Authentic Netapp Certification Exam NS0-077 Questions Answers

For a StorageGRID node running as a VMware virtual machine, NetApp requires the node to be gracefully shut down before hypervisor migration or maintenance. The supported migration approach is therefore a cold migration, in which the StorageGRID node is stopped before it is moved to another ESXi host. NetApp documentation explicitly states that cold migration is supported.

Option A is specifically unsupported. NetApp warns that VMware live vMotion can cause the virtual machine clock to jump. StorageGRID depends heavily on synchronized time for distributed database operations, object metadata, configuration updates, and inter-node coordination. A time discontinuity can therefore lead to data or configuration integrity problems, which is why live vMotion must not be used for StorageGRID grid nodes.

Option B is incorrect because StorageGRID appliance maintenance mode is intended for specific appliance maintenance procedures; it is not the prescribed migration workflow for a VMware-hosted software Storage Node. Option C is also not the required host-maintenance procedure and unnecessarily introduces datastore-level movement considerations.

Thus, the correct sequence is to gracefully shut down the StorageGRID VM and perform a cold migration to another ESXi host, preserving grid integrity while host maintenance is performed.

Reference topics: VMware Deployment → Hypervisor Maintenance → StorageGRID Node Shutdown → VMware Migration Restrictions → Cold Migration

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

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