NetApp NS0-077 Practice Exam Questions & Answers

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

For unidirectional cross-grid replication, CGR must be enabled on the bucket in the grid that acts as the source. NetApp states that when CGR is enabled on only one grid, objects added to that source bucket are replicated automatically to the corresponding destination bucket on the other grid; objects written to the destination are not replicated back. Because the required direction is Grid-1 Grid-2, CGR must therefore be enabled on Grid-1.

The administrator then selects the appropriate grid federation connection and sets Replicate delete markers = Yes. When an S3 client deletes an object without specifying a version ID, StorageGRID creates a delete marker. With this option enabled, that marker is replicated to Grid-2 so the object appears deleted on both grids, helping maintain matching bucket state. NetApp documents this as the default behavior.

Option A would configure bidirectional replication, which violates the unidirectional requirement. Option B reverses the required replication direction. Option D is incorrect because the relevant CGR configuration control is Replicate delete markers, not ''Replicate metadata.''

Reference topics: Tenant Manager Grid Federation Cross-Grid Replication Source and Destination Buckets Versioning Replicate Delete Markers

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

A Global Server Load Balancer (GSLB) is the appropriate solution when StorageGRID client traffic must be intelligently directed among multiple geographically distributed sites. NetApp states that global load balancing integrates with DNS to provide intelligent routing across StorageGRID sites and can direct clients to the closest destination site, while also detecting site outages and redirecting requests to another available site. This global routing functionality is provided through a supported third-party load-balancing or DNS traffic-management solution.

A typical architecture combines GSLB at the global layer with site-local load balancers or StorageGRID Gateway Node HA groups. When an S3 client resolves the StorageGRID endpoint FQDN, the GSLB selects the appropriate site's virtual IP based on factors such as availability and network latency, thereby providing proximity-based client access.

Option B provides effective local site load balancing, but by itself does not choose the geographically closest site. Option A provides HA for interfaces within an HA group and is not a geographic traffic-management mechanism. Option C provides link-level redundancy and bandwidth aggregation rather than application-level site selection.

Therefore, D is the correct answer.

Reference topics: StorageGRID Load Balancing Third-Party Load Balancers Global Server Load Balancing (GSLB) DNS-Based Site Selection Geo-Distributed Client Access

StorageGRID diagnostic information requested by NetApp Support can be collected through the Grid Manager log-collection interface. NetApp documents SUPPORT > Tools > Log collection as the standard StorageGRID mechanism for gathering logs, configuration data, system information, and other diagnostic content from selected grid nodes. The resulting .tar.gz archive can be downloaded or sent to NetApp Technical Support.

NetApp Active IQ OneCollect is also a NetApp diagnostic collection framework that supports StorageGRID environments and can collect consolidated support information for troubleshooting. NetApp documentation identifies OneCollect as a mechanism for gathering diagnostic data from supported NetApp systems, including StorageGRID, and making that information available for support analysis.

Lumberjack is a StorageGRID node-level troubleshooting utility and remains useful for specialized log collection, but for this question's wording---specifically generating and uploading support data through the NetApp support workflow---the intended choices are OneCollect and Grid Manager log collection.

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