Free Practice Questions for Netapp NS0-077 Exam

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 correct approach is to create three separate S3 tenant accounts, one for each business unit. StorageGRID tenant accounts are designed as administrative and data-isolation boundaries. NetApp states that each tenant account has its own federated or local groups, users, S3 buckets, and objects, allowing different organizational entities to manage their own resources independently. NetApp specifically cites an enterprise use case in which separate tenant accounts are created for different departments such as Marketing, Human Resources, and Customer Support.

This design also provides delegated administration. After the grid administrator creates each tenant, authorized users for that tenant can use Tenant Manager to manage their own groups, users, S3 access keys, and buckets without gaining administrative control over resources belonging to another tenant.

Option A can segregate S3 resources with bucket policies, and NetApp documents that as a valid alternative where separate tenants are unnecessary. However, it does not provide the same strict administrative separation required here. Options B and C similarly place all business units within one tenant and therefore share the same tenant-level administrative boundary.

Therefore, D best satisfies both strict isolation and independent management.

Reference topics: Tenant Accounts → Enterprise Multitenancy → Tenant Manager → Groups and Users → S3 Buckets → Administrative Isolation

StorageGRID Platform Services traffic, including Apache Kafka event notifications, originates from Storage Nodes that run the Administrative Domain Controller (ADC) service. NetApp explicitly requires these ADC Storage Nodes to have network connectivity to external Platform Services endpoints. For Kafka, StorageGRID normally establishes outbound TCP connectivity from ADC Storage Nodes to the Kafka cluster, using port 9092 by default unless another port is configured.

In this topology, the Storage Nodes do not have Client Network interfaces, so they cannot use a Client Network default route to reach the Kafka endpoint. NetApp's supported alternative is to configure the Storage Nodes with Admin Networks containing appropriate Admin External Subnet List (AESL) entries that provide routes to the external endpoint network. Without the required AESL route on the ADC nodes, StorageGRID cannot validate connectivity to the Kafka endpoint.

Option B incorrectly identifies LDR as the service responsible for sending Platform Services messages. Option D is irrelevant because Gateway Nodes do not originate these Kafka Platform Services notifications. Although Platform Services must be enabled for the tenant, the networking details in the scenario specifically identify missing ADC-node endpoint routing as the intended failure.

Reference topics: Platform Services → Kafka Event Notifications → ADC Service → Admin Network → AESL → External Endpoint Connectivity

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

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

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 answer is Gateway Node. StorageGRID 12.0 provides load balancer caching, which is specifically designed to improve performance when workloads repeatedly access the same subset of objects. NetApp identifies AI/ML training as a strong candidate for this feature because training jobs often reread the same datasets across multiple epochs. By serving frequently requested objects from cache, StorageGRID can reduce backend object retrieval activity and lower response latency.

NetApp explicitly states that load balancer caching is available only on Gateway Nodes. Administrators enable caching on a load balancer endpoint associated with Gateway Nodes and should use dedicated cache-enabled endpoints for workloads that benefit from repeated reads. NetApp also lists data lakes, high-performance computing, AI/ML training, content distribution, media asset management, and video production as examples of workloads that can benefit from caching.

Option B is incorrect because Storage Nodes hold object data and metadata but do not provide the integrated load-balancer caching capability. Option C is incorrect even though Admin Nodes run the Load Balancer service; the caching feature itself is restricted to Gateway Nodes. Archive Nodes are unrelated to this functionality.

Therefore, D. Gateway is the verified answer.

Reference topics: StorageGRID 12.0 → Gateway Nodes → Load Balancer Caching → Cache-Enabled Endpoints → AI/ML Training Workloads

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