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 .

The correct tool for modifying network addressing on an existing StorageGRID deployment is the change-ip tool. NetApp documents that the Change IP tool can modify the network configuration of one or more grid nodes, including the IP address, subnet mask/prefix, gateway, and MTU. It can also update Grid Network configuration and add, modify, or remove Admin and Client Network addressing.
This is the appropriate mechanism when moving an operational StorageGRID site to a new data center where the network subnet changes. The tool provides a controlled workflow to select affected nodes, edit addressing, review the proposed configuration, validate the changes, and then apply them to the grid. StorageGRID 12.0 documentation shows the workflow explicitly through the change-ip command and its menu options for editing IP/mask, gateway, MTU, and Grid Network subnet information.
Option A is primarily used during appliance installation and certain appliance maintenance operations, not as the general grid-wide IP migration tool. Option C bypasses StorageGRID configuration management and must not be used as the normal method for persistent grid-network changes. Option D manages tenant-level S3 resources and cannot modify node networking.
Reference topics: StorageGRID Maintenance # Network Procedures # Configure IP Addresses # Change Node Network Configuration # Change IP Tool

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

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