NS0-077 Practice Tests - NetApp StorageGRID Administrator Exam

Prévia do material em texto

1 / 10
Exam : NS0-077
Title :
https://www.passcert.com/NS0-077.html
NetApp StorageGRID
Administrator Exam
2 / 10
1.You are setting up a StorageGRID environment that must maintain data for regulatory compliance.
Which two items are required? (Choose two.)
A. default SnapLock policy
B. Compliance Clock
C. S3 Object Lock
D. compliant default ILM rule
Answer: C D
Explanation:
For regulatory retention in StorageGRID, the required mechanisms are S3 Object Lock and a compliant
default ILM rule. StorageGRID implements write-once-read-many protection through S3 Object Lock.
NetApp states that the global S3 Object Lock setting must be enabled before tenants can create buckets
with S3 Object Lock enabled. Once enabled globally, the setting cannot be disabled.
There is also a mandatory ILM dependency. NetApp explicitly requires the default rule in every active
ILM policy to be compliant before global S3 Object Lock can be enabled. A compliant default rule must
maintain at least two replicated copies or one erasure-coded copy on Storage Nodes, must begin
protection at day 0 using Ingest time, cannot place the protected copies in a Cloud Storage Pool, and
must include a placement extending forever.
Option A is incorrect because SnapLock is an ONTAP WORM technology and is not the StorageGRID
compliance mechanism.
Option B is also incorrect: StorageGRID regulatory retention does not require an administrator-
configured “Compliance Clock.” Object retention is enforced through S3 Object Lock retain-until dates,
retention modes, legal holds, and compliant ILM placement.
Reference topics: S3 Object Lock # Regulatory Compliance # Compliant ILM Rules # Default ILM Rule #
Retention and Legal Hold
2.Which encryption method is available for all deployment methods?
A. Node Encryption
B. Drive Security
C. Stored Object Encryption
D. Drive Encryption
Answer: C
Explanation:
Stored Object Encryption is the StorageGRID encryption method that is available regardless of how the
grid nodes are deployed. It is configured centrally in Grid Manager rather than depending on appliance-
specific hardware capabilities. When enabled, StorageGRID encrypts newly ingested S3 object data that
has not already been encrypted at the bucket or object level. StorageGRID supports AES-128 or AES-
256 for this function.
The other options are deployment-specific. Node Encryption is associated with StorageGRID appliance
nodes and a configured external Key Management Server (KMS); it must be enabled for an eligible
appliance during installation. Drive Security depends on storage appliances equipped with Full Disk
Encryption or self-encrypting drives and is managed through SANtricity System Manager. Drive
Encryption likewise requires StorageGRID appliances containing supported self-encrypting drives and is
configured through the StorageGRID Appliance Installer. These hardware dependencies mean none of
those three methods is universally available across virtual, containerized, cloud, and appliance
3 / 10
deployment models.
Therefore, C. Stored Object Encryption is the correct answer because it operates at the StorageGRID
object-ingest layer rather than relying on a particular node or disk hardware implementation.
Reference topics: Grid Manager # Security Settings # Network and Objects # Stored Object Encryption;
StorageGRID Encryption Methods
3.Which StorageGRID feature enables you to have multiple active information lifecycle management
(ILM) policies?
A. bucket tags
B. ILM policy tags
C. multitenancy
D. Identity and Access Management (IAM) policy
Answer: B
Explanation:
The feature that enables multiple active ILM policies is ILM policy tags. NetApp StorageGRID allows
administrators to create multiple ILM policies and associate each policy with a specific policy tag.
Tenants can then assign one of those ILM policy tags to an S3 bucket, causing objects in that bucket to
be managed by the ILM policy associated with the selected tag. This enables different buckets to receive
different data-protection, placement, retention, or performance treatments while those policies remain
active simultaneously.
StorageGRID also maintains a Default ILM policy tag. Every grid must have an active policy associated
with the Default tag, and that policy governs objects in buckets that do not have another ILM policy tag
assigned. NetApp supports up to 10 policy tags per grid.
Option A is too general. Although StorageGRID implements the assignment on an S3 bucket, the
enabling construct is specifically the ILM policy tag.
Option C, multitenancy, separates tenant resources but does not itself permit multiple active ILM policies.
Option D, IAM policy, controls S3 access permissions and authorization rather than ILM placement or
retention behavior.
Therefore, B is the correct answer.
Reference topics: ILM # Policy Tags # Multiple Active Policies # Default Policy Tag # Per-Bucket ILM
Assignment
4.To comply with an industry regulation, a bank is establishing a disaster recovery solution across two
grids. The tenant federation was successfully configured. You are required to unidirectionally replicate a
critical bucket from Grid-1 to Grid-2 and ensure that all of the content is identical on each grid, to
reestablish operations in the event that Grid-1 fails.
After creating a bucket with versioning enabled on each grid, what are the required steps to complete the
task?
A. Enable cross-grid replication (CGR) on each grid, select the grid federation connection, and select
Yes for Replicate delete markers.
B. Enable cross-grid replication (CGR) on Grid-2, select the grid federation connection, and select Yes
for Replicate delete markers.
C. Enable cross-grid replication (CGR) on Grid-1, select the grid federation connection, and select Yes
for Replicate delete markers.
4 / 10
D. Enable cross-grid replication (CGR) on Grid-1, select the grid federation connection, and select Yes
for Replicate metadata.
Answer: C
Explanation:
For unidirectional cross-grid replication, CGR must be enabled on the bucket in the grid that acts as the
source. NetApp states that when CGR is enabled on only one grid, objects added to that source bucket
are replicated automatically to the corresponding destination bucket on the other grid; objects written to
the destination are not replicated back. Because the required direction is Grid-1 # Grid-2, CGR must
therefore be enabled on Grid-1.
The administrator then selects the appropriate grid federation connection and sets Replicate delete
markers = Yes. When an S3 client deletes an object without specifying a version ID, StorageGRID
creates a delete marker. With this option enabled, that marker is replicated to Grid-2 so the object
appears deleted on both grids, helping maintain matching bucket state. NetApp documents this as the
default behavior.
Option A would configure bidirectional replication, which violates the unidirectional requirement.
Option B reverses the required replication direction.
Option D is incorrect because the relevant CGR configuration control is Replicate delete markers, not
“Replicate metadata.”
Reference topics: Tenant Manager # Grid Federation # Cross-Grid Replication # Source and Destination
Buckets # Versioning # Replicate Delete Markers
5.A StorageGRID ILM policy has moved objects belonging to a specific bucket to a Cloud Storage Pool.
The objects have transitioned automatically to S3 Glacier Deep Archive storage class to minimize costs.
A user now requires immediate access to one of these archived objects.
How can the user achieve this goal?
A. The user must issue an S3 GetObject request, and StorageGRID will automatically retrieve the object.
B. Since the object is no longer on StorageGRID, the user must go directly to the Amazon S3 console to
restore and retrieve the object.
C. Retrieval is not possible, because StorageGRID does not support retrieval from S3 Glacier Deep
Archive.
D. The user must issue an S3 RestoreObject request from Glacier Deep Archive, followed by a
GetObject request.
Answer: D
Explanation:When an object stored in a Cloud Storage Pool has transitioned to Amazon S3 Glacier Deep Archive, it
is in a non-retrievable state. StorageGRID therefore cannot satisfy a normal GetObject request until a
retrievable copy has first been restored. NetApp specifies that the client application must issue an S3
RestoreObject request to restore the object temporarily within the Cloud Storage Pool. After the
restoration completes, the client can issue GetObject through StorageGRID to retrieve the data.
For a restored object, RestoreObject specifies how long the retrievable copy remains available.
StorageGRID supports restoration from Glacier Deep Archive, but Deep Archive does not support the
Expedited retrieval tier; only Standard or Bulk retrieval can be used. Thus, “immediate” access means
initiating the restore process immediately, not instantaneous retrieval from the Deep Archive tier.
Option A is incorrect because GetObject does not automatically restore a non-retrievable Glacier object.
5 / 10
Option B is incorrect because restoration is performed through StorageGRID's S3 API; direct Amazon-
console intervention is unnecessary.
Option C is incorrect because StorageGRID explicitly supports RestoreObject for Cloud Storage Pool
objects transitioned to Glacier Deep Archive.
Reference topics: ILM # Cloud Storage Pools # S3 Glacier Deep Archive # RestoreObject # GetObject #
Retrieval Tiers
6.A customer has an AI/ML training workload that accesses the same objects multiple times. They have
a requirement to enable caching to increase performance.
What StorageGRID node type supports this feature?
A. Archive
B. Storage
C. Admin
D. Gateway
Answer: D
Explanation:
The correct answer is Gateway Node. StorageGRID 12.0 provides load balancer caching, which is
specifically designed to improve performance when workloads repeatedly access the same subset of
objects. NetApp identifies AI/ML training as a strong candidate for this feature because training jobs often
reread the same datasets across multiple epochs. By serving frequently requested objects from cache,
StorageGRID can reduce backend object retrieval activity and lower response latency.
NetApp explicitly states that load balancer caching is available only on Gateway Nodes. Administrators
enable caching on a load balancer endpoint associated with Gateway Nodes and should use dedicated
cache-enabled endpoints for workloads that benefit from repeated reads. NetApp also lists data lakes,
high-performance computing, AI/ML training, content distribution, media asset management, and video
production as examples of workloads that can benefit from caching.
Option B is incorrect because Storage Nodes hold object data and metadata but do not provide the
integrated load-balancer caching capability.
Option C is incorrect even though Admin Nodes run the Load Balancer service; the caching feature itself
is restricted to Gateway Nodes. Archive Nodes are unrelated to this functionality.
Therefore, D. Gateway is the verified answer.
Reference topics: StorageGRID 12.0 # Gateway Nodes # Load Balancer Caching # Cache-Enabled
Endpoints # AI/ML Training Workloads
7.You have a StorageGRID environment consisting of two sites deployed as virtual machines. Site A
contains the primary Admin Node, one Gateway Node, and four Storage Nodes. Site B contains a
nonprimary Admin Node, one Gateway Node, and four Storage Nodes. All client operations use load
balancer endpoints through the Gateway Node. A host in Site A running both the primary Admin Node
and Gateway Node has crashed.
What recovery process should you use to resume client operations the quickest?
A. Deploy a new primary Admin Node, and expand as a new primary Admin Node.
B. Deploy a new Gateway Node, and recover the failed Gateway Node from the nonprimary Admin
Node.
C. Deploy a new primary Admin Node, and recover the failed primary Admin Node.
6 / 10
D. Deploy a new Gateway Node, and expand as a new Gateway Node.
Answer: C
Explanation:
When a physical or virtual host containing multiple StorageGRID nodes fails, NetApp defines a specific
recovery-order requirement when one of those nodes is the primary Admin Node. StorageGRID 12.0
documentation states that if the failed server hosts the primary Admin Node, the primary Admin Node
must be recovered first. This prevents subsequent node-recovery operations from stopping while
attempting to communicate with services associated with the primary Admin Node.
Therefore, the administrator should deploy a replacement VM for the primary Admin Node and perform
the documented primary Admin Node recovery. After the primary Admin Node is operational, recovery of
the failed Gateway Node can proceed, restoring the intended client load-balancing path.
Option A is invalid because StorageGRID does not permit adding a primary Admin Node through an
expansion; the primary Admin Node is established during initial installation and a failed one must be
recovered.
Options B and D incorrectly prioritize the Gateway Node while the failed host also contains the primary
Admin Node. The StorageGRID 12.0 recovery guidance explicitly requires the primary Admin Node to be
handled first in this situation.
Reference topics: Maintenance # Node Recovery # Primary Admin Node Recovery # Multiple Nodes on
Failed Host # Gateway Node Recovery # Load Balancer Service
8.When managing a StorageGRID system, you observe that an object has been successfully ingested,
but its storage location does not match expectations based on the active information lifecycle
management (ILM) policy. You need to confirm which ILM rule was applied to the object during ingest.
Which method helps you infer the ILM rule that was applied to the object?
A. Perform a metadata lookup on the object to view its storage location.
B. Review the audit log for an ORLM (Object Rules Met) message related to the object.
C. Use the ILM policy simulation tool to test object placement based on metadata.
D. Review the audit log for an SPUT (S3 PUT) message related to the object.
Answer: B
Explanation:
The ORLM (Object Rules Met) audit message is the appropriate source for determining which ILM rule
StorageGRID applied to an object. NetApp documents that ORLM is generated when object data has
been successfully stored according to an ILM rule. Critically, the ORLM record contains a RULE field,
which identifies the human-readable label of the ILM rule applied to that object. It also includes the
object's CBID, ILM status, result, and storage-location information.
A metadata lookup in option A is valuable for verifying the current physical placement of replicated copies
or erasure-coded fragments, but it does not directly identify the ILM rule responsible for that placement.
NetApp specifically recommends ORLM when additional information about the ILM evaluation is
required.
Option C simulates how an active ILM policy would evaluate representative metadata; it does not prove
which rule was actually applied to an already-ingested object.
Option D is also insufficient because an SPUT audit record confirms completion of an S3 PUT
transaction and supplies identifiers such as the CBID, bucket, and key, but does not contain the applied
ILM rule name.
7 / 10
Reference topics: Audit Logs # ILM Audit Messages # ORLM/Object Rules Met # RULE Field # Object
Metadata Lookup # ILM Troubleshooting
9.A customer owns a StorageGRID system that contains NetApp SG6160 and SG1100 appliances. The
grid shows low utilization in terms of used space and performance.
Which two additional workloads are valid? (Choose two.)
A. databases
B. file tiering
C. backup solutions
D. virtualization
Answer: B C
Explanation:
The two valid additional workloads are file/data tiering and backup solutions. StorageGRID is an S3-
compatible object-storage platform, and NetApp explicitly positions it for workloads such as data tiering,
backup and disaster recovery, archive, analytics, and application object storage. NetApp FabricPool can
automatically tier inactive data from ONTAP performance tiersto StorageGRID, which directly supports
the file/data-tiering use case.
StorageGRID is also a well-established target for enterprise backup applications. NetApp documents
integrations in which backup products use StorageGRID either as a primary object-storage backup
destination or as a secondary/long-term retention tier. Its scalability, S3 interface, ILM capabilities, and
high-throughput architecture make unused capacity and performance resources suitable for additional
backup workloads.
Options A and D are not appropriate as stated. Production databases generally require transactional
block or file storage characteristics, while virtualization datastores normally depend on block or NAS
protocols such as SAN, NFS, or VMFS. StorageGRID instead exposes object storage through the S3
API and is not intended to act as a conventional database volume or hypervisor datastore.
Therefore, the correct choices are B and C.
Reference topics: StorageGRID Use Cases # FabricPool/Data Tiering # Backup and Recovery # S3
Object Storage # NetApp Solutions Integration
10.During a troubleshooting session with a NetApp Support Engineer, you are asked to upload log files
for further analysis.
Which two methods do you use to generate and upload the required logs to NetApp Support using
upload. netapp.com/sg? (Choose two.)
A. Use the NetApp Active IQ OneCollect tool.
B. Trigger an on-demand AutoSupport message on the admin interface.
C. Use Lumberjack on involved nodes.
D. Use Grid Manager SUPPORT > Tools > Logs.
Answer: A D
Explanation:
StorageGRID diagnostic information requested by NetApp Support can be collected through the Grid
Manager log-collection interface. NetApp documents SUPPORT > Tools > Log collection as the standard
StorageGRID mechanism for gathering logs, configuration data, system information, and other
diagnostic content from selected grid nodes. The resulting .tar.gz archive can be downloaded or sent to
8 / 10
NetApp Technical Support.
NetApp Active IQ OneCollect is also a NetApp diagnostic collection framework that supports
StorageGRID environments and can collect consolidated support information for troubleshooting.
NetApp documentation identifies OneCollect as a mechanism for gathering diagnostic data from
supported NetApp systems, including StorageGRID, and making that information available for support
analysis.
Lumberjack is a StorageGRID node-level troubleshooting utility and remains useful for specialized log
collection, but for this question's wording—specifically generating and uploading support data through
the NetApp support workflow—the intended choices are OneCollect and Grid Manager log collection.
11.You have a StorageGRID system that spans multiple sites. You are asked to create an S3 bucket for
extremely important objects that require all sites to receive metadata immediately after any new write or
change.
When creating this S3 bucket, which consistency level meets the requirement?
A. strong-global
B. available
C. strong-site
D. read-after-new-write
Answer: A
Explanation:
The appropriate consistency level is strong-global because the requirement explicitly applies to clients
and object metadata across multiple StorageGRID sites. NetApp defines strong-global as providing read-
after-write consistency for all client requests across all sites.
Therefore, after an object is created or its metadata is changed, subsequent requests from any site
receive a consistent view of that change.
strong-site is insufficient because its consistency guarantee applies only to client requests within a single
site. A client accessing the bucket from another StorageGRID site could therefore fall outside the
required site-wide consistency guarantee. read-after-new-write, which is the default and generally
recommended setting, guarantees consistency for newly created objects but provides eventual
consistency for object updates. Because the scenario requires immediate consistency following both
new writes and changes, it does not meet the stated requirement. available provides eventual
consistency for both new objects and updates and prioritizes availability rather than cross-site
consistency.
Thus, among the available options, strong-global is specifically designed for workloads requiring globally
consistent object and metadata visibility across a multisite StorageGRID deployment.
Reference topics: S3 Buckets # Bucket Consistency # Strong-global # Strong-site # Read-after-new-
write # Metadata Distribution Across Sites
12.You intend to perform maintenance on a customer's VMware ESXi, which hosts a StorageGRID
Storage Node as a virtual machine (VM).
Which procedure maintains the integrity of the grid?
A. Use live vMotion to another ESXi host.
B. Use Grid Manager to boot the VM into maintenance mode.
C. Use Storage vMotion to another datastore, except disk 1.
9 / 10
D. Shut down the VM and cold migrate it on another ESXi host.
Answer: D
Explanation:
For a StorageGRID node running as a VMware virtual machine, NetApp requires the node to be
gracefully shut down before hypervisor migration or maintenance. The supported migration approach is
therefore a cold migration, in which the StorageGRID node is stopped before it is moved to another ESXi
host. NetApp documentation explicitly states that cold migration is supported.
Option A is specifically unsupported. NetApp warns that VMware live vMotion can cause the virtual
machine clock to jump. StorageGRID depends heavily on synchronized time for distributed database
operations, object metadata, configuration updates, and inter-node coordination. A time discontinuity can
therefore lead to data or configuration integrity problems, which is why live vMotion must not be used for
StorageGRID grid nodes.
Option B is incorrect because StorageGRID appliance maintenance mode is intended for specific
appliance maintenance procedures; it is not the prescribed migration workflow for a VMware-hosted
software Storage Node.
Option C is also not the required host-maintenance procedure and unnecessarily introduces datastore-
level movement considerations.
Thus, the correct sequence is to gracefully shut down the StorageGRID VM and perform a cold migration
to another ESXi host, preserving grid integrity while host maintenance is performed.
Reference topics: VMware Deployment # Hypervisor Maintenance # StorageGRID Node Shutdown #
VMware Migration Restrictions # Cold Migration
13.Your customer is running a multisite grid and is ingesting log data from a variety of sources. The logs
are processed by a Security Information and Event Management (SIEM) solution and stored in the grid
for reading purposes only. A log file must be readable from all available nodes in the grid. Ingest into the
grid must be possible even when a site is down. Due to the size and importance, the log files are stored
in an EC7+5 format across three sites.
Which bucket consistency level and ingest policy must be selected?
A. read-after-new-write and strict
B. strong-global and strict
C. all and balanced
D. read-after-new-write and balanced
Answer: D
Explanation:
The correct combination is read-after-new-write consistency with Balanced ingest. The workload
contains log objects that are written once and subsequently read, so read-after-new-write provides the
required behavior: StorageGRID guarantees read-after-write consistency for new objects, while
maintaining high availability. NetApp recommends this consistency setting for most workloads. Because
these SIEM log objects are not expected to be updated after creation, the eventual-consistency behavior
for updates is not material to this use case.
The ingest requirement is decisive. The EC7+5 placement spans three sites, but clients must remain
able to ingest when one site is unavailable. With Strict ingest, StorageGRID must satisfy the ILM
placement instructions synchronously before acknowledging the write. If the required EC placement
cannot be created because a site is down, the request fails. In contrast, Balanced attempts the specified
10 / 10
ILMplacement immediately but, when an outage prevents that placement, StorageGRID falls back to
dual-commit protection and acknowledges the object. ILM subsequently creates the required EC7+5
placement when resources become available again.
all is inappropriate because it requires every metadata node to receive metadata immediately, reducing
availability during failures.
Therefore, D satisfies both immediate visibility of newly written logs and continued ingest during a site
outage.
Reference topics: S3 Bucket Consistency # Read-after-new-write # ILM Ingest Behavior # Balanced vs
Strict # Erasure Coding # Multisite Availability
14.A customer is deploying a new grid across three data centers. Ingested data must always be
consistent and available for all read and write operations in the event that one site and an additional
node fails.
Which consistency level is required?
A. all
B. strong-global
C. strong-site
D. read-after-new-write
Answer: B
Explanation:
The required consistency level is strong-global, specifically using the Quorum strong-global semantics
available in StorageGRID 12.0. NetApp defines strong-global as guaranteeing read-after-write
consistency for client requests across all sites. With Quorum semantics enabled, a grid containing three
or more sites can tolerate a site failure while continuing client operations, provided the required metadata
replica quorum remains available.
This directly matches the scenario. NetApp's multisite resiliency guidance states that, for a three-or-
more-site deployment using Quorum strong-global, a single site plus a single node failure can occur
without interruption to operations or metadata consistency, assuming sufficient object-data protection
remains under the ILM configuration.
Option A, all, is unsuitable because every metadata node must acknowledge the update; if a node or site
is unavailable, the request fails.
Option C, strong-site, only guarantees immediate consistency within one site and does not provide the
required global consistency.
Option D provides read-after-write consistency for new objects but only eventual consistency for
updates, so it does not satisfy the requirement that data remain consistently available for all read and
write activity.
Reference topics: StorageGRID 12.0 # S3 Consistency # Strong-global # Quorum Semantics # Multisite
Failure Tolerance # Metadata Replication