You have a StorageGRID environment consisting of two sites deployed as virtual machines. Site A contains the primary Admin Node, one Gateway Node, and four Storage Nodes. Site B contains a nonprimary Admin Node, one Gateway Node, and four Storage Nodes. All client operations use load balancer endpoints through the Gateway Node. A host in Site A running both the primary Admin Node and Gateway Node has crashed.
What recovery process should you use to resume client operations the quickest?
When a physical or virtual host containing multiple StorageGRID nodes fails, NetApp defines a specific recovery-order requirement when one of those nodes is the primary Admin Node. StorageGRID 12.0 documentation states that if the failed server hosts the primary Admin Node, the primary Admin Node must be recovered first. This prevents subsequent node-recovery operations from stopping while attempting to communicate with services associated with the primary Admin Node.
Therefore, the administrator should deploy a replacement VM for the primary Admin Node and perform the documented primary Admin Node recovery. After the primary Admin Node is operational, recovery of the failed Gateway Node can proceed, restoring the intended client load-balancing path.
Option A is invalid because StorageGRID does not permit adding a primary Admin Node through an expansion; the primary Admin Node is established during initial installation and a failed one must be recovered. Options B and D incorrectly prioritize the Gateway Node while the failed host also contains the primary Admin Node. The StorageGRID 12.0 recovery guidance explicitly requires the primary Admin Node to be handled first in this situation.
Reference topics: Maintenance Node Recovery Primary Admin Node Recovery Multiple Nodes on Failed Host Gateway Node Recovery Load Balancer Service
A customer requires highly available data connections for S3 clients.
Which two types of nodes can be grouped together to provide high availability?
StorageGRID High Availability (HA) groups provide resilient S3 client connectivity by grouping network interfaces from multiple Admin Nodes and Gateway Nodes. NetApp states that HA groups containing Gateway Nodes, Admin Nodes, or a combination of both can provide highly available data connections for S3 clients.
An HA group uses one or more virtual IP (VIP) addresses. One interface is designated as the primary active interface, while the remaining interfaces act as backups according to their configured priority. S3 applications connect to the VIP rather than directly to an individual node. If the active interface or its node becomes unavailable, StorageGRID transfers the VIP to another eligible interface in the HA group, allowing client workloads to continue with minimal interruption. Both Admin Nodes and Gateway Nodes run the Load Balancer service, which distributes S3 requests to Storage Nodes.
Options A and B are incorrect because Storage Node interfaces cannot be members of StorageGRID HA groups. Option C is also invalid; Archive Nodes are not supported HA-group members and are unrelated to client load-balancer HA.
Therefore, the supported node combination for highly available S3 client connections is Admin Nodes and Gateway Nodes.
Reference topics: Grid Manager High Availability Groups Admin Nodes Gateway Nodes Virtual IP Addresses Load Balancer Service S3 Client Connectivity
Which encryption method is available for all deployment methods?
Stored Object Encryption is the StorageGRID encryption method that is available regardless of how the grid nodes are deployed. It is configured centrally in Grid Manager rather than depending on appliance-specific hardware capabilities. When enabled, StorageGRID encrypts newly ingested S3 object data that has not already been encrypted at the bucket or object level. StorageGRID supports AES-128 or AES-256 for this function.
The other options are deployment-specific. Node Encryption is associated with StorageGRID appliance nodes and a configured external Key Management Server (KMS); it must be enabled for an eligible appliance during installation. Drive Security depends on storage appliances equipped with Full Disk Encryption or self-encrypting drives and is managed through SANtricity System Manager. Drive Encryption likewise requires StorageGRID appliances containing supported self-encrypting drives and is configured through the StorageGRID Appliance Installer. These hardware dependencies mean none of those three methods is universally available across virtual, containerized, cloud, and appliance deployment models.
Therefore, C. Stored Object Encryption is the correct answer because it operates at the StorageGRID object-ingest layer rather than relying on a particular node or disk hardware implementation.
Reference topics: Grid Manager Security Settings Network and Objects Stored Object Encryption; StorageGRID Encryption Methods
A customer wants to test their application against a StorageGRID system to verify its compatibility.
What is the minimum number and type of nodes required to deploy a healthy virtual StorageGRID environment for this test?
A healthy StorageGRID deployment requires one primary Admin Node and at least three Storage Nodes at each site. NetApp StorageGRID 12.0 documentation states that every grid requires a primary Admin Node to provide core management and configuration services, while every site requires a minimum of three Storage Nodes. Therefore, the smallest healthy single-site virtual test environment contains four nodes: one Admin Node plus three Storage Nodes.
The three-Storage-Node minimum is important because Storage Nodes host core distributed services such as Cassandra, DDS, and ADC. In particular, the ADC service is hosted on at least three Storage Nodes at a site, supporting grid topology information, authentication, and service discovery.
Option A lacks the required primary Admin Node and therefore cannot constitute a complete manageable StorageGRID grid. Option D contains an Admin Node but only one Storage Node, which does not satisfy the three-node minimum. Option C would work, but the Gateway Node is optional because Admin Nodes can also provide S3 load-balancing functionality for a small compatibility-test deployment.
Therefore, B is the minimum healthy virtual configuration.
Reference topics: StorageGRID Architecture Grid Node Types Primary Admin Node Minimum Storage Nodes per Site Virtual Deployment Requirements
You are configuring a two-site StorageGRID solution to be the destination for mission-critical application data. You want the HA group to fail over from one site to the other in the event of a site failure.
How is the HA group configured?
A StorageGRID High Availability (HA) group provides active-backup access by assigning one or more virtual IP (VIP) addresses to the currently active interface. For site-level failover, the HA group includes suitable Admin Node or Gateway Node interfaces from both sites, and those interfaces must participate in a network design that allows the same VIP to move between sites. NetApp's StorageGRID site-failover guidance specifically describes including interfaces from Site 1 and Site 2 and assigning a VIP within the same subnet. If the preferred site's interface becomes unavailable, StorageGRID transfers the VIP to the next available interface at the other site.
Accordingly, the VIP subnet must be available across the participating sites; the same client-facing VIP remains usable after failover. StorageGRID requires the VIP and optional gateway to belong to the configured VIP subnet.
Option B is incorrect because multiple VIPs are not assigned as independent site-specific addresses for HA failover; all configured VIPs reside simultaneously on the active HA interface. Option C is invalid because the HA configuration requires IP addresses, not an FQDN. Option D confuses the optional gateway with the actual VIP.
Reference topics: Grid Manager High Availability Groups Multi-site HA VIP Subnet Primary and Backup Interfaces Site Failover
Currently there are no comments in this discussion, be the first to comment!