Netapp NS0-077 NetApp StorageGRID Administrator Exam Exam Practice Test

The SG6160 is the best match for environments designed for very large-scale StorageGRID deployments. StorageGRID 12.0 substantially increases overall platform scalability, supporting up to one trillion objects, more than twice the previous platform limit. This increase is enabled in part by a newer Cassandra version that stores object metadata more efficiently, allowing considerably larger object populations to be maintained.

The SG6160 is NetApp's higher-scale disk-based StorageGRID appliance. Its SG6100-CN compute controller provides 48 CPU cores and 256 GB of RAM, providing substantially more compute and memory resources for StorageGRID services than capacity-oriented SG5800 models. It also supports a 60-drive base shelf plus as many as two 60-drive expansion shelves, for a maximum of 180 drives per appliance. NetApp specifically positions the SG6160 and its expansion configuration for large-scale deployments, transactional small-object workloads, and data lakes.

The SG5812 and SG5860 are positioned primarily as cost-optimized secondary-storage platforms. The SG1100 is a services appliance used for Admin Node and Gateway Node functions and does not provide object-storage capacity.

Therefore, D. SG6160 is the appropriate selection for this scale-oriented requirement.

Reference topics: StorageGRID 12.0 Scalability → One-Trillion-Object Limit → Cassandra Metadata Scaling → SG6100 Series → SG6160 Large-Scale Deployments

StorageGRID High Availability (HA) groups provide resilient S3 client connectivity by grouping network interfaces from multiple Admin Nodes and Gateway Nodes. NetApp states that HA groups containing Gateway Nodes, Admin Nodes, or a combination of both can provide highly available data connections for S3 clients.

An HA group uses one or more virtual IP (VIP) addresses. One interface is designated as the primary active interface, while the remaining interfaces act as backups according to their configured priority. S3 applications connect to the VIP rather than directly to an individual node. If the active interface or its node becomes unavailable, StorageGRID transfers the VIP to another eligible interface in the HA group, allowing client workloads to continue with minimal interruption. Both Admin Nodes and Gateway Nodes run the Load Balancer service, which distributes S3 requests to Storage Nodes.

Options A and B are incorrect because Storage Node interfaces cannot be members of StorageGRID HA groups. Option C is also invalid; Archive Nodes are not supported HA-group members and are unrelated to client load-balancer HA.

Therefore, the supported node combination for highly available S3 client connections is Admin Nodes and Gateway Nodes.

Reference topics: Grid Manager → High Availability Groups → Admin Nodes → Gateway Nodes → Virtual IP Addresses → Load Balancer Service → S3 Client Connectivity

StorageGRID maintenance should be performed using a rolling, node-by-node approach so that the grid continues providing S3 services while individual nodes are temporarily unavailable. NetApp states that StorageGRID upgrades are designed to be non-disruptive: nodes of the same type are taken down and upgraded one at a time, preventing all nodes of a particular role from becoming unavailable simultaneously.

NetApp also permits administrators to approve individual nodes or groups of nodes and, when upgrade order is important, explicitly recommends waiting for one node or group to complete before approving the next. During this process, administrators should monitor Grid Manager for node status, alerts, and service health.

High availability also depends on appropriate architecture: ILM policies should maintain redundant object copies, and S3 clients should connect through HA-group VIPs, highly available third-party load balancers, or multiple Gateway Nodes.

Option A increases operational risk by scheduling maintenance during peak load. Option C could remove too much grid capacity simultaneously and defeat redundancy. Option D is not a prescribed StorageGRID maintenance procedure and could unnecessarily disrupt grid and client communication.

Reference topics: Software Update → Rolling Upgrade → Hotfix Installation → Node Availability → HA Client Connectivity → ILM Redundancy

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

FabricPool normally connects ONTAP to StorageGRID through an HTTPS load balancer endpoint. That endpoint uses a server certificate so that ONTAP can authenticate the StorageGRID service. NetApp specifically warns that if the certificate securing the ONTAP-to-StorageGRID connection expires, FabricPool temporarily stops working and ONTAP loses access to data tiered to StorageGRID.

The same problem can occur when the endpoint certificate is renewed or replaced in StorageGRID but the corresponding trusted certificate on ONTAP is not updated. NetApp requires the StorageGRID and ONTAP certificate configurations to remain synchronized; after certificate replacement or renewal, ONTAP must trust the new certificate chain.

The scenario also eliminates the node-failure answers. The two Gateway Nodes are configured in an HA group, so failure of one Gateway Node should not independently cause the FabricPool endpoint to become unavailable. Likewise, losing one Storage Node does not normally prevent access to the StorageGRID S3 service. A Client Network trust-state change would have broader networking implications and does not fit the isolated, time-related FabricPool failure described.

Therefore, C is the correct answer.

Reference topics: FabricPool Integration → StorageGRID Load Balancer Endpoints → HTTPS/TLS Certificates → Certificate Expiration and Rotation

Adding another SG1100 services appliance increases aggregate client throughput because each SG1100 can operate as a Gateway Node running the StorageGRID Load Balancer service. With DNS Round Robin, client connections are distributed across the available services appliances, allowing the aggregate load-balancing capacity to scale horizontally. NetApp explicitly identifies increased aggregate throughput and no idle hosts as advantages of the DNS Round Robin load-balancing model.

The SG1100 is specifically designed to provide high-performance Gateway Node and Admin Node services and supports high-speed network connectivity up to 100 GbE. Adding another equivalent SG1100 therefore provides additional processing and network capacity while preserving consistent performance characteristics across the load-balancer pool. NetApp cautions against mixing services appliances with substantially different performance levels when balancing client traffic.

Option B is incorrect because the SGF6112 is a Storage Node appliance, while StorageGRID load-balancer caching is available only on Gateway Nodes. Option C does not provide the same intended horizontal client-throughput expansion. Option D would substitute an SG110, a lower-performance services appliance, and could create inconsistent load-balancing performance.

Therefore, A is the correct answer.

Reference topics: StorageGRID Load Balancing → DNS Round Robin → SG1100 Services Appliances → Gateway Nodes → Aggregate Client Throughput

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 backup workload requires time-based immutability, so the tenant must be permitted to use S3 Object Lock. StorageGRID S3 Object Lock protects individual object versions from deletion or overwrite until their configured retain-until date. When an Object Lock-enabled bucket is created, StorageGRID automatically enables bucket versioning. A backup application can then assign its seven-year retention period to each object as it is written.

For the new tenant, the grid administrator should also configure the maximum retention period as seven years. StorageGRID allows administrators to define a tenant-level maximum retention period, and any bucket default retention or object-level retain-until date must remain within that limit. The current StorageGRID tenant-creation workflow specifically provides S3 Object Lock advanced permissions for configuring this maximum retention period.

After an object's retain-until date expires, S3 Object Lock no longer prevents its deletion, allowing the backup software to perform normal expiration or cleanup operations. Platform Services are unrelated; they provide functions such as CloudMirror and event notifications. A 7-TB quota controls capacity, not retention duration or immutability.

Reference topics: Tenant Accounts → S3 Object Lock → Maximum Retention Period → Object-Level Retention → Immutable Backup Data

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 tool for modifying network addressing on an existing StorageGRID deployment is the change-ip tool. NetApp documents that the Change IP tool can modify the network configuration of one or more grid nodes, including the IP address, subnet mask/prefix, gateway, and MTU. It can also update Grid Network configuration and add, modify, or remove Admin and Client Network addressing.

This is the appropriate mechanism when moving an operational StorageGRID site to a new data center where the network subnet changes. The tool provides a controlled workflow to select affected nodes, edit addressing, review the proposed configuration, validate the changes, and then apply them to the grid. StorageGRID 12.0 documentation shows the workflow explicitly through the change-ip command and its menu options for editing IP/mask, gateway, MTU, and Grid Network subnet information.

Option A is primarily used during appliance installation and certain appliance maintenance operations, not as the general grid-wide IP migration tool. Option C bypasses StorageGRID configuration management and must not be used as the normal method for persistent grid-network changes. Option D manages tenant-level S3 resources and cannot modify node networking.

Reference topics: StorageGRID Maintenance → Network Procedures → Configure IP Addresses → Change Node Network Configuration → Change IP Tool

A Global Server Load Balancer (GSLB) is the appropriate solution when StorageGRID client traffic must be intelligently directed among multiple geographically distributed sites. NetApp states that global load balancing integrates with DNS to provide intelligent routing across StorageGRID sites and can direct clients to the closest destination site, while also detecting site outages and redirecting requests to another available site. This global routing functionality is provided through a supported third-party load-balancing or DNS traffic-management solution.

A typical architecture combines GSLB at the global layer with site-local load balancers or StorageGRID Gateway Node HA groups. When an S3 client resolves the StorageGRID endpoint FQDN, the GSLB selects the appropriate site's virtual IP based on factors such as availability and network latency, thereby providing proximity-based client access.

Option B provides effective local site load balancing, but by itself does not choose the geographically closest site. Option A provides HA for interfaces within an HA group and is not a geographic traffic-management mechanism. Option C provides link-level redundancy and bandwidth aggregation rather than application-level site selection.

Therefore, D is the correct answer.

Reference topics: StorageGRID Load Balancing → Third-Party Load Balancers → Global Server Load Balancing (GSLB) → DNS-Based Site Selection → Geo-Distributed Client Access

The correct configuration is to route StorageGRID AutoSupport traffic through an Admin proxy server. NetApp states that when AutoSupport packages are transmitted using HTTPS, the primary Admin Node requires outbound access to NetApp Technical Support either directly or through a proxy server. This is specifically intended for secure environments where StorageGRID nodes cannot establish unrestricted direct internet connections.

The administrator configures this under Configuration > Security > Proxy settings > Admin, enables the Admin proxy, and specifies the proxy server hostname or IP address and port. Authentication credentials can also be supplied when required. Once configured, AutoSupport traffic from Admin Nodes to NetApp Technical Support is routed through this controlled proxy path.

This preserves normal AutoSupport functionality, including periodic and event-triggered AutoSupport packages, which support proactive monitoring and automatic support-case workflows. Manually uploading bundles, as in A, would not provide the desired automated behavior. Option B does not solve the connectivity restriction. Option C is also incorrect because AutoSupport On Demand is intended primarily for active troubleshooting and itself requires HTTPS connectivity; it does not replace normal automated AutoSupport delivery.

Therefore, D provides the required secure outbound connectivity while retaining automated NetApp support capabilities.

Reference topics: Grid Manager → AutoSupport → Admin Proxy → HTTPS AutoSupport → Event-Triggered AutoSupport → NetApp Technical Support Connectivity

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

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

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

The correct answer is metadata updates. StorageGRID maintains object metadata independently from object data, using the distributed Cassandra database. NetApp specifies that StorageGRID stores three copies of the metadata for every object at each site, meaning every site maintains metadata for all objects in the grid, regardless of where the object data itself is physically stored.

This distinction is critical in the scenario. Even though the new fourth site uses an ILM policy that keeps its object data local with a 2+1 protection scheme, metadata activity is still grid-wide. NetApp explicitly states that administrators must consider network bandwidth and latency between sites because metadata updates are continually replicated between sites even when all object copies remain at the site where they were ingested. Therefore, the WAN links connecting all four sites must be sized to support continuous metadata synchronization.

Load balancer endpoints handle S3 client connectivity and do not create this universal intersite requirement. NTP requires reliable time synchronization but is not the workload driving the stated bandwidth-sizing requirement. Storage pools are logical ILM constructs and do not themselves replicate metadata.

Therefore, B. metadata updates is the required component.

Reference topics: StorageGRID Expansion → Adding a Site → Cassandra Metadata Replication → Intersite Network Bandwidth and Latency → ILM Data Placement

A StorageGRID branch bucket provides access to objects from a versioned base bucket as those objects existed at a selected point or range in time. NetApp describes a branch bucket as presenting a distinct view of protected data while allowing operations on the branch to be separated from the base bucket. This makes branch buckets appropriate for use cases such as application testing, investigation, recovery workflows, development, and other activities where production data should remain undisturbed.

When creating the branch, an administrator can select a Before, After, Between, or Exclude time filter. A branch can also be configured as read-only or read-write. Importantly, object settings and objects written directly to a branch do not modify the corresponding object versions in the base bucket.

Option A is incorrect because StorageGRID is fundamentally S3 object storage; branch buckets do not provide simultaneous SMB/NFS access. Option B describes cloud tiering rather than branching. Option C describes ILM rule filtering and placement behavior, which is handled through StorageGRID ILM policies and rules, not branch buckets.

Therefore, D best represents the intended operational purpose of branch buckets: creating an isolated point-in-time data view for nondisruptive work without changing the production base bucket.

Reference topics: Tenant Manager → S3 Buckets → Branch Buckets → Base Bucket → Versioning → Time Filters → Read-only/Read-write Branches

To delete a specific version of an S3 object, the user must have the appropriate S3 permission, specifically s3:DeleteObjectVersion. In StorageGRID, permissions granted to tenant users are commonly defined through group policies, which control which S3 actions members of the group are authorized to perform against specified bucket and object resources. NetApp explicitly maps s3:DeleteObjectVersion to the S3 operation that deletes a specific object version.

Therefore, the user should verify the group policy associated with their tenant account and confirm that it allows s3:DeleteObjectVersion for the required bucket or object ARN. An explicit Deny for this action would override an Allow. NetApp even provides policy examples that specifically restrict users from deleting versioned objects by denying s3:DeleteObjectVersion.

Option B is incorrect because an S3 lifecycle policy automates object expiration and version-management behavior; it does not grant interactive user permissions. Option C governs where and how StorageGRID stores and protects object data, not S3 authorization. Option D refers to administrative privileges and is not the standard mechanism controlling a tenant user's object-level S3 operations.

Therefore, A. group policy is correct.

Reference topics: Tenant Manager → Groups → S3 Group Policies → s3:DeleteObjectVersion → Versioned Object Permissions → Explicit Deny/Allow Evaluation