NS0-077 Sample Questions Answers

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

When an existing StorageGRID deployment is expanded with nodes whose Grid Network IP addresses are on a subnet that has not previously been used, that subnet must be added to the Grid Network subnet list before the expansion is started. StorageGRID maintains this list so that every grid node can correctly route internal Grid Network traffic to the other participating subnets. NetApp StorageGRID 12.0 documentation explicitly states that if any new node uses a new Grid Network subnet, the administrator must add that subnet first; otherwise, the expansion must be cancelled, the subnet added, and the expansion restarted.

The configuration is performed in Grid Manager → Maintenance → Network → Grid Network, where the administrator selects Add another subnet and enters the network in CIDR notation. StorageGRID then distributes the routing configuration throughout the grid.

Option A is incorrect because routes do not need to be configured manually on every node. Option B is incorrect because a StorageGRID Gateway Node provides client load-balancing functions and is not an IP router between Grid Network subnets. Option D is also incorrect; StorageGRID explicitly supports multiple Grid Network subnets, provided they are routable through the configured Grid Network gateway.

Reference topics: StorageGRID Expansion → Grid Network → Grid Network Subnet List → Adding Nodes on New Subnets → Grid Network Routing

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

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

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

The feature that enables multiple active ILM policies is ILM policy tags. NetApp StorageGRID allows administrators to create multiple ILM policies and associate each policy with a specific policy tag. Tenants can then assign one of those ILM policy tags to an S3 bucket, causing objects in that bucket to be managed by the ILM policy associated with the selected tag. This enables different buckets to receive different data-protection, placement, retention, or performance treatments while those policies remain active simultaneously.

StorageGRID also maintains a Default ILM policy tag. Every grid must have an active policy associated with the Default tag, and that policy governs objects in buckets that do not have another ILM policy tag assigned. NetApp supports up to 10 policy tags per grid.

Option A is too general. Although StorageGRID implements the assignment on an S3 bucket, the enabling construct is specifically the ILM policy tag. Option C, multitenancy, separates tenant resources but does not itself permit multiple active ILM policies. Option D, IAM policy, controls S3 access permissions and authorization rather than ILM placement or retention behavior.

Therefore, B is the correct answer.

Reference topics: ILM → Policy Tags → Multiple Active Policies → Default Policy Tag → Per-Bucket ILM Assignment

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