NS0-077 Exam Dumps : NetApp StorageGRID Administrator Exam

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

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 distributes object metadata evenly across the Storage Nodes participating in metadata storage at a site. Consequently, when Storage Nodes have different metadata capacities, the smallest Storage Node becomes the limiting factor for the site's usable metadata capacity. NetApp explicitly states that when a site contains Storage Nodes of different sizes, the smallest node at that site determines the site's metadata capacity.

The underlying consideration is particularly tied to volume 0, because StorageGRID stores Cassandra object metadata on volume 0. NetApp recommends configuring comparable volume 0 sizes across Storage Nodes whenever possible. If different sizes are used, the node with the smallest volume 0 establishes the effective per-node metadata ceiling. Because metadata is evenly distributed, excess metadata space available on larger nodes cannot compensate for insufficient capacity on the smallest participating node.

Therefore, the largest, newest, or oldest Storage Node has no special role in determining metadata sizing. Hardware generation or installation age is irrelevant to this calculation; usable metadata capacity is constrained by the node with the least available metadata capacity.

Reference topics: Grid Manager → Storage Settings → Metadata Reserved Space; Storage Nodes → Volume 0; Object Metadata Capacity and Cassandra Distribution