NS0-077 Exam Preparation Material | NetApp StorageGRID Administrator Exam

Explanation:
The failure is caused by the strong-global metadata consistency requirement, not by the Strict ILM placement requirement. StorageGRID stores object metadata in Cassandra, normally maintaining three metadata replicas per site. With three Storage Nodes at Site-2, taking one node down for maintenance and then losing another leaves only one metadata replica available at that site. The required metadata quorum can no longer be achieved for strong-global operations. NetApp documents that strong-global guarantees read-after-write consistency across all sites and requires sufficient metadata replicas to complete the operation.
The distinction from Strict ingest is important. Strict controls object-data placement: all copies specified by the ILM rule must be created before StorageGRID returns success. Here, the ILM rule requires only one copy at each site. Because one Storage Node remains operational at Site-2, StorageGRID can potentially place the Site-2 object copy there .
Therefore, the data-placement requirement itself is not necessarily violated.
However, with two of the three metadata-bearing Storage Nodes unavailable at Site-2, Cassandra cannot satisfy the strong-global metadata consistency requirement, causing client PUT operations to fail.
Reference topics: S3 Consistency # Strong-global # Cassandra Metadata Replicas # Metadata Quorum # Strict ILM Ingest Behavior

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

Explanation:
The appropriate consistency level is strong-global because the requirement explicitly applies to clients and object metadata across multiple StorageGRID sites. NetApp defines strong-global as providing read-after-write consistency for all client requests across all sites.
Therefore, after an object is created or its metadata is changed, subsequent requests from any site receive a consistent view of that change.
strong-site is insufficient because its consistency guarantee applies only to client requests within a single site. A client accessing the bucket from another StorageGRID site could therefore fall outside the required site-wide consistency guarantee. read-after-new-write, which is the default and generally recommended setting, guarantees consistency for newly created objects but provides eventual consistency for object updates. Because the scenario requires immediate consistency following both new writes and changes, it does not meet the stated requirement. available provides eventual consistency for both new objects and updates and prioritizes availability rather than cross-site consistency.
Thus, among the available options, strong-global is specifically designed for workloads requiring globally consistent object and metadata visibility across a multisite StorageGRID deployment.
Reference topics: S3 Buckets # Bucket Consistency # Strong-global # Strong-site # Read-after-new-write # Metadata Distribution Across Sites

Explanation:
StorageGRID evaluates ILM rules sequentially from the top of the active policy. As soon as an object matches a rule, that rule's placement instructions are applied and the object is not evaluated against subsequent rules .
Therefore, the rule containing the specific status=archive filter must appear before the catch-all rule.
In option A, objects tagged status=archive match Rule 1 and receive 4+2 erasure coding at the designated single-site storage pool. StorageGRID supports 4+2 erasure coding in a one-site storage pool provided that at least six data-capable Storage Nodes are available; seven are recommended.
Objects without the archive tag do not match Rule 1 and proceed to Rule 2. Rule 2 serves as the default rule, providing two replicated copies across the required sites. NetApp requires the default rule to be last and to have no filters, ensuring that it catches every object not matched earlier.
Option C is incorrect because its unrestricted first rule would match every object, preventing the archive-specific rule from ever being evaluated. B applies the protection methods to the wrong object classes, while D provides no rule for non-archive objects.
Reference topics: ILM Policies # Rule Evaluation Order # Advanced Filters/Object Tags # Default Rule # Replication # Single-Site Erasure Coding

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