NS0-077 Questions and Answers

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

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

A healthy StorageGRID deployment requires one primary Admin Node and at least three Storage Nodes at each site. NetApp StorageGRID 12.0 documentation states that every grid requires a primary Admin Node to provide core management and configuration services, while every site requires a minimum of three Storage Nodes. Therefore, the smallest healthy single-site virtual test environment contains four nodes: one Admin Node plus three Storage Nodes.

The three-Storage-Node minimum is important because Storage Nodes host core distributed services such as Cassandra, DDS, and ADC. In particular, the ADC service is hosted on at least three Storage Nodes at a site, supporting grid topology information, authentication, and service discovery.

Option A lacks the required primary Admin Node and therefore cannot constitute a complete manageable StorageGRID grid. Option D contains an Admin Node but only one Storage Node, which does not satisfy the three-node minimum. Option C would work, but the Gateway Node is optional because Admin Nodes can also provide S3 load-balancing functionality for a small compatibility-test deployment.

Therefore, B is the minimum healthy virtual configuration.

Reference topics: StorageGRID Architecture → Grid Node Types → Primary Admin Node → Minimum Storage Nodes per Site → Virtual Deployment Requirements

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

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

To provide highly available access specifically to Grid Manager and Tenant Manager, the HA group must contain Admin Node interfaces. StorageGRID 12.0 documentation states that Admin Nodes provide access to these management services, whereas Gateway Nodes provide the Load Balancer service for S3 client traffic. For Grid Manager access, the HA group should contain the primary Admin Node and one or more non-primary Admin Nodes; the primary Admin Node must be configured as the primary interface in the group.

Tenant Manager also runs on Admin Nodes. Tenant users connect to an Admin Node when accessing Tenant Manager, so using multiple Admin Node interfaces behind an HA virtual IP provides the required management-interface availability.

Option B is incorrect because Gateway Nodes do not provide Grid Manager or Tenant Manager. Option D is valid for S3 client access, because both Admin and Gateway Nodes run the Load Balancer service, but it is not the correct configuration for management-interface HA. Option C corresponds to a specialized HA configuration used for S3 Select and does not satisfy the management-service requirement.

Therefore, the correct answer is A.

Reference topics: Grid Manager → High Availability Groups → Administrative Connections → Admin Nodes → Grid Manager/Tenant Manager → VIP Failover

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

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

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.

Reference topics: Audit Logs → ILM Audit Messages → ORLM/Object Rules Met → RULE Field → Object Metadata Lookup → ILM Troubleshooting

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

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

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

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