NS0-077 NetApp StorageGRID Administrator Exam Questions and Answers

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

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

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

StorageGRID Traffic Classification Policies provide the correct quality-of-service mechanism for controlling a workload that is consuming excessive network or request resources. A traffic classification policy can match traffic by bucket, tenant, subnet, or load balancer endpoint and can impose limits such as aggregate bandwidth, per-request bandwidth, concurrent requests, or request rate. Therefore, the appropriate remediation is to identify the backup bucket and restrict the bandwidth available to that workload.

This approach prevents the backup application from monopolizing StorageGRID resources during its backup window, leaving sufficient capacity for other clients to perform object uploads. StorageGRID 12.0 documentation specifically states that bandwidth limits control the rate at which matching requests are allowed to flow and that traffic-classification policies are designed for traffic limiting and SLA-related performance management.

Option D is incorrect because StorageGRID traffic classification does not provide a mechanism to reserve or guarantee minimum bandwidth to other buckets; it limits maximum resource consumption by matching workloads. Options A and C involve ILM ingest behavior. Strict or Balanced ingest controls how object placement satisfies ILM requirements at ingest and is not a QoS mechanism for protecting competing workloads.

Therefore, throttling the backup bucket through a traffic classification policy is the correct solution.

Reference topics: Grid Manager → Configuration → Network → Traffic Classification → Bucket Matching Rules → Bandwidth Limits → QoS and Workload Management

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

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

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 ILM placement 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

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

For a capacity-focused FabricPool repository containing predominantly cold object data, the most efficient expansion method is to add a data-only Storage Node. StorageGRID 12.0 supports combined, metadata-only, and data-only Storage Nodes. A data-only node is dedicated to object-data storage and does not participate in Cassandra metadata storage, making it particularly appropriate when the primary objective is to maximize usable object capacity rather than increase metadata capacity. NetApp specifically describes data-only, high-capacity Storage Nodes as appropriate when dedicated capacity is required.

After the node is added, erasure-coded data can be rebalanced so that existing EC fragments are redistributed across the original and newly added Storage Nodes. NetApp states that EC rebalancing redistributes erasure-coded fragments among Storage Nodes at the site, allowing newly added capacity to be utilized by an existing EC protection scheme.

Option D adds usable capacity, but a combined node also provides metadata/Cassandra functionality that is unnecessary when the goal is specifically to maximize object-data capacity for a cold FabricPool workload. Options B and C are not supported StorageGRID capacity-expansion strategies; appliance RAID/DDP configuration and SANtricity LUN sizing must not be arbitrarily changed to enlarge StorageGRID object storage.

Reference topics: StorageGRID Expansion → Data-only Storage Nodes → Object Capacity → Erasure Coding → EC Rebalancing → FabricPool Capacity Planning

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

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

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

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

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