Netapp NS0-077 NetApp StorageGRID Administrator Exam Exam Practice Test

NetApp defines a specific workflow for migrating a Linux-based StorageGRID node between hosts. The source node must first be shut down cleanly using storagegrid node stop. After the node has stopped, the administrator runs storagegrid node export on the source host. The export output identifies the /var/local storage volume and provides the corresponding import command to use on the target host.

On Host-B, the administrator runs storagegrid node import against the exported node storage. NetApp then requires the imported configuration to be checked with storagegrid node validate. After successful validation, the migrated node is started with storagegrid node start, and Grid Manager is used to confirm that the node returns to a green operational state with no alerts.

Therefore, C represents the required migration sequence. Although the option summarizes the final validation/start phase, its stop → export → import → verify ordering matches NetApp's prescribed procedure.

Option A is incorrect because Grid Manager does not automatically migrate Linux containers. Option B reverses the export/import sequence. Option D incorrectly treats migration as a new StorageGRID installation and node reconfiguration.

Reference topics: StorageGRID Maintenance → Linux Host Migration → Node Stop → Node Export → Node Import → Validate → Start → Grid Manager Verification

Under the legacy strong-global consistency behavior represented by these answer choices, writes use a quorum of metadata replicas at every site, while reads require a quorum of metadata replicas at the local site. Consequently, B and D are the intended answers. This architecture provides read-after-write consistency across all sites while allowing a client to perform reads using the metadata replicas available locally rather than waiting for responses from every remote site. NetApp defines strong-global as guaranteeing read-after-write consistency for client requests across all sites.

There is an important StorageGRID 12.0 qualification. New StorageGRID 12.0 installations use Quorum strong-global semantics by default. In a three-site grid containing three metadata replicas per site, the write requirement becomes a grid-wide quorum of five of the nine metadata replicas, with no more than three replicas contributed by one site. This improves site-failure tolerance. Systems upgraded from StorageGRID 11.9 or earlier retain the legacy strong-global behavior unless explicitly changed.

Therefore, B and D are the certification-key answer for the semantics assumed by this question, but B should not be generalized to a newly installed StorageGRID 12.0 grid using Quorum strong-global.

Reference topics: S3 Consistency → Strong-global → Metadata Replicas → Local Read Quorum → Legacy vs Quorum Strong-global

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

The bank-records bucket requires indefinite immutable retention, so its ILM rule must comply with StorageGRID S3 Object Lock requirements. NetApp specifies that a compliant ILM rule must create at least two replicated copies or one erasure-coded copy, those copies must reside on Storage Nodes, at least one placement must begin at day 0 using Ingest time, and at least one placement must continue forever. Critically, copies governed by a compliant S3 Object Lock rule cannot be stored in a Cloud Storage Pool.

This requirement directly eliminates A, B, and C because every one of those choices introduces a Cloud Storage Pool. The organization's general preference to use cloud storage for long-term data does not override StorageGRID compliance restrictions for Object Lock-protected content.

NetApp's own bank-records example uses precisely this design: the bucket-specific compliant rule retains an erasure-coded copy on Storage Nodes from day 0 to forever.

Therefore, D is correct. Other noncompliant buckets can still use separate ILM rules that transition data to Cloud Storage Pools after six months, but immutable bank-records objects must remain on compliant StorageGRID Storage Node placements indefinitely.

Reference topics: ILM → S3 Object Lock → Compliant ILM Rules → Storage Nodes → Forever Retention → Cloud Storage Pool Restrictions

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

In StorageGRID, group policies are attached to a specific tenant group and define which S3 resources members of that group are permitted or denied access to. NetApp explicitly states that a group policy applies to only one group and can apply to multiple buckets. This makes B the correct answer.

Group policies are configured through Tenant Manager or the Tenant Management API and use AWS-compatible JSON policy syntax. A single group policy can therefore contain multiple Resource entries referencing different buckets and objects. In contrast, a bucket policy is attached to one specific bucket and can grant or deny access to multiple users or groups.

Options A and C are incorrect because StorageGRID does not assign precedence among group, bucket, and session policies. NetApp states that there is no difference in priority among these policy types. Authorization is determined by evaluating the applicable policy statements, with an explicit Deny overriding an Allow; it is not based on one policy class automatically taking precedence over another.

Option D reverses the relationship: it describes the scope of a bucket policy rather than a group policy.

Reference topics: Tenant Manager → S3 Access Management → Group Policies → Bucket Policies → Session Policies → AWS Policy Language

A StorageGRID High Availability (HA) group provides active-backup access by assigning one or more virtual IP (VIP) addresses to the currently active interface. For site-level failover, the HA group includes suitable Admin Node or Gateway Node interfaces from both sites, and those interfaces must participate in a network design that allows the same VIP to move between sites. NetApp's StorageGRID site-failover guidance specifically describes including interfaces from Site 1 and Site 2 and assigning a VIP within the same subnet. If the preferred site's interface becomes unavailable, StorageGRID transfers the VIP to the next available interface at the other site.

Accordingly, the VIP subnet must be available across the participating sites; the same client-facing VIP remains usable after failover. StorageGRID requires the VIP and optional gateway to belong to the configured VIP subnet.

Option B is incorrect because multiple VIPs are not assigned as independent site-specific addresses for HA failover; all configured VIPs reside simultaneously on the active HA interface. Option C is invalid because the HA configuration requires IP addresses, not an FQDN. Option D confuses the optional gateway with the actual VIP.

Reference topics: Grid Manager → High Availability Groups → Multi-site HA → VIP Subnet → Primary and Backup Interfaces → Site Failover

For the SG5860, which uses the SG5800 controller, StorageGRID supports both Fixed and Aggregate port-bond configurations. In Fixed mode, ports 2 and 4 are paired for the Grid Network and ports 1 and 3 for the Client Network. Active-Backup is the default network bond mode, and VLAN tagging is optional; therefore, the two-port Active-Backup configuration in A is supported.

In Aggregate port bond mode, all four 10/25-GbE ports form a single LACP (802.3ad) bond carrying both Grid and Client Network traffic. Because both networks share the aggregate, StorageGRID requires a unique VLAN tag for each network, making C the supported aggregate configuration. A four-port Active-Backup aggregate is not supported, eliminating B.

Verification note: the current NetApp SG5800 appliance documentation also permits two-port LACP bonds in Fixed mode, with VLAN tagging optional. Consequently, option D is technically supported as written, making this question ambiguous against current documentation. If restricted to the intended two-answer certification key representing the standard Fixed Active-Backup and Aggregate LACP configurations, A and C are the expected selections.

Reference topics: SG5800/SG5860 Appliance Networking → Fixed Port Bond Mode → Aggregate Port Bond Mode → Active-Backup → LACP → VLAN Tagging

StorageGRID requires an ADC service quorum at each site at all times. The ADC service maintains grid topology information and provides configuration services used throughout the grid. StorageGRID therefore prevents the decommissioning of a Storage Node if removing that node would violate the site's ADC quorum requirements.

StorageGRID 12.0 provides a supported Move ADC procedure specifically for situations where an administrator needs to decommission a Storage Node hosting ADC. The ADC service can be moved to another eligible Storage Node within the same site. The target must not already host ADC and must be either a combined Storage Node or metadata-only Storage Node. NetApp performs the operation through the Grid Management private API, using POST /private/move-adc/start; progress can be monitored with GET /private/move-adc. The dependent IDNT, ACCT, and RSM services move automatically with ADC.

Option B is invalid because ADC runs on eligible Storage Nodes, not Admin Nodes. Option C is incorrect because StorageGRID 12.0 documents the migration through the Grid Management API rather than a CLI relocation command. Option D is unsupported; administrators do not manually reinstall ADC.

Therefore, A is correct.

Reference topics: StorageGRID Maintenance → Move ADC → ADC Quorum → Storage Node Decommission → Grid Management API

The ILM placement unachievable alert means that StorageGRID is unable to satisfy one or more placement instructions defined by an active ILM rule for certain objects. NetApp defines this alert as indicating that an ILM placement instruction cannot be achieved for certain objects, commonly because a required Storage Node or storage location is temporarily unavailable or because the ILM rule specifies a placement that the current topology cannot satisfy.

Therefore, D is the most accurate answer. The alert does not inherently mean that every S3 PUT operation failed. Whether a client PUT fails depends on the ILM rule's ingest behavior. With Strict ingest, StorageGRID must create all placements specified by the ILM rule immediately, so a placement failure can cause the client PUT to fail. With Balanced ingest, StorageGRID can temporarily use alternate protection and complete the required ILM placement later.

This distinction makes option C too absolute. Options A and B are unrelated to the meaning of the alert. NetApp also notes that ILM placement unachievable can occur while Storage Nodes are stopped during an upgrade and can persist for up to one day afterward, which is directly relevant to this post-update scenario.

Reference topics: Grid Manager → Alerts → ILM Placement Unachievable → ILM Placement Instructions → Balanced and Strict Ingest Behavior → Upgrade/Hotfix Monitoring

The correct configuration is Cross-Origin Resource Sharing (CORS). StorageGRID supports CORS specifically so that objects stored in an S3 bucket can be accessed by web applications originating from different domains. NetApp's documentation uses essentially this exact use case: an S3 bucket containing images can be configured with CORS so that those images can be displayed by a website hosted in another domain.

For a service provider hosting image objects centrally while multiple customer websites access those objects from separate domains, the browser treats the requests as cross-origin. A CORS configuration on the S3 bucket defines the permitted origins, HTTP methods such as GET, and allowed headers. The administrator can either authorize specific customer domains or, where appropriate, permit GET requests from multiple origins. HTTPS remains handled independently by the StorageGRID load balancer endpoint and its TLS certificate.

Option C is incorrect because the HTTPS certificate must match the StorageGRID endpoint domain names clients connect to, not every external website that merely references the images. Option A is unnecessary because one endpoint can service multiple domains, and Swift is unrelated.

Reference topics: Tenant Manager → S3 Buckets → Cross-Origin Resource Sharing (CORS) → Allowed Origins → Static Web Content → HTTPS S3 Access

NetApp StorageGRID is a distributed object-storage platform with native Amazon S3 API support, making option D the appropriate use case. NetApp positions StorageGRID for storing large quantities of unstructured data securely and durably across geographically distributed sites, with integrated Information Lifecycle Management controlling object placement, protection, retention, and storage tier throughout the object's lifecycle. These characteristics make StorageGRID particularly suitable for enterprise backup, archive, disaster-recovery, and long-term retention repositories.

S3 clients communicate with StorageGRID using object operations such as PUT Object, GET Object, and DELETE Object. StorageGRID can protect the resulting objects through replicated copies or erasure coding according to ILM policy, enabling highly durable and scalable repositories that can be accessed by authorized applications from multiple locations.

Option A describes persistent block/file-style storage normally provided to Kubernetes through CSI-backed storage services. Option B requires traditional NAS file protocols and directory-service integration rather than S3 object access. Option C describes a transactional database workload requiring low-latency SAN/block storage; StorageGRID is not a replacement for an FC SAN hosting Oracle database volumes.

Therefore, D directly aligns with StorageGRID's S3 architecture and documented use cases.

Reference topics: StorageGRID → S3 REST API → Object Storage → Backup and Archive → ILM → Replication and Erasure Coding

StorageGRID HA groups use an explicit interface priority order. The first interface in that order is the Primary interface and normally hosts all virtual IP addresses assigned to the HA group. If the Primary interface becomes unavailable, StorageGRID automatically moves the VIP addresses to the highest-priority backup interface that remains operational.

Importantly, this behavior includes automatic failback. NetApp states that when the failure is resolved and a higher-priority interface becomes available again, the VIP addresses are automatically moved to the highest-priority available interface. Therefore, once the original Primary interface is restored and considered healthy, StorageGRID automatically transfers the VIP back to it. No administrator intervention or Load Balancer service restart is required.

Options A and C are incorrect because restarting the Load Balancer service is not part of the standard HA failback workflow. Option B is also incorrect because StorageGRID does not permanently leave the VIP on a lower-priority backup interface after the preferred interface has recovered. The configured priority order continues to determine which interface should host the HA group's VIPs.

Reference topics: Grid Manager → High Availability Groups → Interface Priority → Primary/Backup Interfaces → VIP Failover and Automatic Failback

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 tiers to 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

StorageGRID's integrated S3 caching capability is designed to improve performance for workloads that repeatedly read a working subset of object data. NetApp states that load balancer caching can significantly improve performance when a workload operates on a subset of data and accesses objects multiple times. The cache is implemented on Gateway Nodes and allows frequently requested S3 objects to be served locally rather than repeatedly retrieving the data from upstream Storage Nodes. This reduces retrieval latency and backend traffic, which is particularly valuable when applications or compute resources are geographically separated from the primary object-storage location.

NetApp identifies data lakes, high-performance computing, AI/ML training, content distribution networks, media asset management, and video production as suitable caching workloads. StorageGRID 12.0 specifically highlights the S3 caching layer as a performance enhancement for AI/ML training.

Option B describes lifecycle-based cloud tiering, not S3 caching. Option C describes conventional durable object storage and, notably, NetApp lists backup applications among workloads that are generally poor candidates for caching. Option D describes ONTAP multiprotocol NAS/object functionality and is unrelated to StorageGRID's S3 cache.

Therefore, A precisely represents the intended caching use case.

Reference topics: StorageGRID 12.0 → Load Balancing → Load Balancer Caching → Gateway Nodes → Cacheable S3 Workloads → AI/ML and HPC Performance

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

The correct architecture combines S3 versioning, cross-grid replication (CGR), and ILM retention. StorageGRID cross-grid replication operates between two StorageGRID systems connected through grid federation and requires the participating source and destination buckets to have versioning enabled. Critically, CGR creates versioned objects at the destination and replicates the source version ID, preserving the ordering of object versions between the grids. This directly satisfies the requirement to protect all possible versions.

After replication, each grid independently applies its active ILM policy to the objects stored locally. The backup grid can therefore use ILM rules to retain replicated objects for at least 90 days. StorageGRID ILM also supports rules specifically targeting noncurrent versions of versioned S3 objects by using Noncurrent time as the reference time, allowing previous versions to be retained for the required period.

Options A and B are unsuitable because nonversioned buckets cannot preserve every object version. Option C correctly identifies versioning and CGR, but a bucket policy governs access permissions; version retention is instead controlled through ILM or an S3 lifecycle configuration.

Reference topics: Grid Federation → Cross-Grid Replication → S3 Versioning → ILM Rules → Noncurrent Object Versions → Retention Periods

StorageGRID supports webhook endpoints as destinations for S3 bucket event notifications. The purpose is to allow external applications, automation systems, or data-processing workflows to react when configured S3 events occur, such as object creation or deletion. NetApp documents that a tenant can configure an external or locally hosted webhook endpoint that accepts HTTP POST notification requests. Platform-service messages are generated from StorageGRID and delivered to the configured endpoint, enabling event-driven application integration.

This makes B the correct answer. For example, after an object is uploaded to a bucket, StorageGRID can generate a notification that is delivered to a webhook. The receiving application can then start processing, indexing, transformation, compliance validation, or another automated workflow without continuously polling the bucket.

Option A describes Cloud Storage Pools/ILM-based external storage placement, not webhook integration. Option C describes ONTAP SnapMirror orchestration, which is not the function of StorageGRID webhook notifications. Option D is also incorrect: webhook-based S3 event notifications are a tenant platform service, not a replacement for Grid-level alerting technologies such as SNMP, email notifications, and StorageGRID monitoring.

NetApp identifies platform services as including CloudMirror replication, bucket event notifications, and search integration, with webhook endpoints supported specifically for event-notification delivery.

Reference topics: Tenant Manager → Platform Services → S3 Event Notifications → Webhook Endpoints → HTTP/HTTPS POST → Event-Driven Integration