NS0-077 Exam Dumps - NetApp StorageGRID Administrator Exam

The correct answer is metadata updates. StorageGRID maintains object metadata independently from object data, using the distributed Cassandra database. NetApp specifies that StorageGRID stores three copies of the metadata for every object at each site, meaning every site maintains metadata for all objects in the grid, regardless of where the object data itself is physically stored.

This distinction is critical in the scenario. Even though the new fourth site uses an ILM policy that keeps its object data local with a 2+1 protection scheme, metadata activity is still grid-wide. NetApp explicitly states that administrators must consider network bandwidth and latency between sites because metadata updates are continually replicated between sites even when all object copies remain at the site where they were ingested. Therefore, the WAN links connecting all four sites must be sized to support continuous metadata synchronization.

Load balancer endpoints handle S3 client connectivity and do not create this universal intersite requirement. NTP requires reliable time synchronization but is not the workload driving the stated bandwidth-sizing requirement. Storage pools are logical ILM constructs and do not themselves replicate metadata.

Therefore, B. metadata updates is the required component.

Reference topics: StorageGRID Expansion → Adding a Site → Cassandra Metadata Replication → Intersite Network Bandwidth and Latency → ILM Data Placement

For the SG5860, which uses the SG5800 controller, StorageGRID supports both Fixed and Aggregate port-bond configurations. In Fixed mode, ports 2 and 4 are paired for the Grid Network and ports 1 and 3 for the Client Network. Active-Backup is the default network bond mode, and VLAN tagging is optional; therefore, the two-port Active-Backup configuration in A is supported.

In Aggregate port bond mode, all four 10/25-GbE ports form a single LACP (802.3ad) bond carrying both Grid and Client Network traffic. Because both networks share the aggregate, StorageGRID requires a unique VLAN tag for each network, making C the supported aggregate configuration. A four-port Active-Backup aggregate is not supported, eliminating B.

Verification note: the current NetApp SG5800 appliance documentation also permits two-port LACP bonds in Fixed mode, with VLAN tagging optional. Consequently, option D is technically supported as written, making this question ambiguous against current documentation. If restricted to the intended two-answer certification key representing the standard Fixed Active-Backup and Aggregate LACP configurations, A and C are the expected selections.

Reference topics: SG5800/SG5860 Appliance Networking → Fixed Port Bond Mode → Aggregate Port Bond Mode → Active-Backup → LACP → VLAN Tagging

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

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

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

The correct action is to create a custom alert rule that evaluates the storagegrid_platform_services_failed_kafka_notifications Prometheus metric. StorageGRID collects operational metrics through Prometheus, and NetApp explicitly supports using those metrics as expressions in custom alert rules. When the configured expression crosses the defined threshold, StorageGRID generates an alert at the selected severity level.

For example, the administrator can create a rule under Alerts > Rules > Create custom rule and define an expression based on an increase or nonzero value for the failed Kafka notification metric. The alert can be configured with an appropriate duration and severity. Once triggered, StorageGRID can display the alert in Grid Manager and, when notification services are configured, send email or SNMP notifications to administrators.

Option B is incorrect because Grafana provides visualization of time-series metrics but does not itself establish StorageGRID alert notification logic. Option D allows an administrator to inspect or test the Prometheus metric, but merely querying it does not generate administrative notifications. Option A concerns HTTP/audit information and has no role in metric-based failure alerting.

Therefore, C is the required method for converting the Kafka failure metric into an actionable StorageGRID notification.

Reference topics: Grid Manager → Alerts → Custom Alert Rules → Prometheus Metrics → Platform Services → Kafka Notification Monitoring

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

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