A customer owns a StorageGRID system that contains NetApp SG6160 and SG1100 appliances. The grid shows low utilization in terms of used space and performance.
Which two additional workloads are valid? (Choose two.)
Answer : B, C
The two valid additional workloads are file/data tiering and backup solutions. StorageGRID is an S3-compatible object-storage platform, and NetApp explicitly positions it for workloads such as data tiering, backup and disaster recovery, archive, analytics, and application object storage. NetApp FabricPool can automatically tier inactive data from ONTAP performance tiers to StorageGRID, which directly supports the file/data-tiering use case.
StorageGRID is also a well-established target for enterprise backup applications. NetApp documents integrations in which backup products use StorageGRID either as a primary object-storage backup destination or as a secondary/long-term retention tier. Its scalability, S3 interface, ILM capabilities, and high-throughput architecture make unused capacity and performance resources suitable for additional backup workloads.
Options A and D are not appropriate as stated. Production databases generally require transactional block or file storage characteristics, while virtualization datastores normally depend on block or NAS protocols such as SAN, NFS, or VMFS. StorageGRID instead exposes object storage through the S3 API and is not intended to act as a conventional database volume or hypervisor datastore.
Therefore, the correct choices are B and C.
Reference topics: StorageGRID Use Cases FabricPool/Data Tiering Backup and Recovery S3 Object Storage NetApp Solutions Integration
Question 2
A certain grid is configured in a network topology where only Admin Nodes and Gateway Nodes have the Client Network configured. Storage Nodes on this grid have only Admin Networks and Grid Networks. A tenant administrator is configuring integration with Apache Kafka for notification services. After setting the correct Uniform Resource Identifier (URI) and Unique Resource Name (URN) entries, the endpoint test validation fails.
What could be a possible cause for this error?
Answer : C
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.
Your customer has a requirement to create external backups of some of their buckets, where all backup objects are to be retained for at least 90 days, including all possible versions. Your customer already created a new standalone grid on the new location.
What steps provide a solution for this requirement?
Answer : D
The correct architecture combines S3 versioning, cross-grid replication (CGR), and ILM retention. StorageGRID cross-grid replication operates between two StorageGRID systems connected through grid federation and requires the participating source and destination buckets to have versioning enabled. Critically, CGR creates versioned objects at the destination and replicates the source version ID, preserving the ordering of object versions between the grids. This directly satisfies the requirement to protect all possible versions.
After replication, each grid independently applies its active ILM policy to the objects stored locally. The backup grid can therefore use ILM rules to retain replicated objects for at least 90 days. StorageGRID ILM also supports rules specifically targeting noncurrent versions of versioned S3 objects by using Noncurrent time as the reference time, allowing previous versions to be retained for the required period.
Options A and B are unsuitable because nonversioned buckets cannot preserve every object version. Option C correctly identifies versioning and CGR, but a bucket policy governs access permissions; version retention is instead controlled through ILM or an S3 lifecycle configuration.
Reference topics: Grid Federation Cross-Grid Replication S3 Versioning ILM Rules Noncurrent Object Versions Retention Periods
Question 4
A customer created several S3 load balancer endpoints, one of which should be accessible only to a specific tenant that is used for internal backups.
How can you meet this requirement?
Answer : C
StorageGRID load balancer endpoints can be restricted so that only selected tenant accounts are permitted to use a specific endpoint. During endpoint configuration, the administrator uses the Tenant access setting and selects Allow selected tenants, then chooses the backup tenant account. NetApp states that with this setting, only the selected tenant accounts can use the endpoint to access their buckets. This directly satisfies the requirement to dedicate one S3 load balancer endpoint to the internal-backup tenant.
Option A is incorrect because a global binding mode determines where the endpoint is available across eligible Admin and Gateway Node interfaces; it does not restrict access by tenant identity. Option D similarly limits the endpoint to interfaces associated with particular HA groups, which controls network exposure rather than tenant authorization. Option B is not a valid per-tenant isolation mechanism because HTTPS configuration applies to the endpoint connection itself and cannot be selectively disabled for unrelated tenant accounts.
Therefore, the required control is to configure the load balancer endpoint's tenant-access settings and assign access specifically to the backup tenant.
A customer runs a StorageGRID deployment with six Storage Nodes at a single site. The customer wants to decommission one of the nodes that hosts an Administrative Domain Controller (ADC) service and replace the node with new hardware.
Before proceeding with the decommission, what is done to ensure that grid quorum and metadata operations remain unaffected?
Answer : A
StorageGRID requires an ADC service quorum at each site at all times. The ADC service maintains grid topology information and provides configuration services used throughout the grid. StorageGRID therefore prevents the decommissioning of a Storage Node if removing that node would violate the site's ADC quorum requirements.
StorageGRID 12.0 provides a supported Move ADC procedure specifically for situations where an administrator needs to decommission a Storage Node hosting ADC. The ADC service can be moved to another eligible Storage Node within the same site. The target must not already host ADC and must be either a combined Storage Node or metadata-only Storage Node. NetApp performs the operation through the Grid Management private API, using POST /private/move-adc/start; progress can be monitored with GET /private/move-adc. The dependent IDNT, ACCT, and RSM services move automatically with ADC.
Option B is invalid because ADC runs on eligible Storage Nodes, not Admin Nodes. Option C is incorrect because StorageGRID 12.0 documents the migration through the Grid Management API rather than a CLI relocation command. Option D is unsupported; administrators do not manually reinstall ADC.
Therefore, A is correct.
Reference topics: StorageGRID Maintenance Move ADC ADC Quorum Storage Node Decommission Grid Management API
Question 6
Your customer wants to add a tenant for a new backup workload to an existing grid. The backup software automatically sets a seven-year retention period on the objects, during which time the object must be immutable. After the retention period, the backup software must be able to clean up the objects as required.
Which two steps will ensure this behavior on the new tenant? (Choose two.)
Answer : A, D
The backup workload requires time-based immutability, so the tenant must be permitted to use S3 Object Lock. StorageGRID S3 Object Lock protects individual object versions from deletion or overwrite until their configured retain-until date. When an Object Lock-enabled bucket is created, StorageGRID automatically enables bucket versioning. A backup application can then assign its seven-year retention period to each object as it is written.
For the new tenant, the grid administrator should also configure the maximum retention period as seven years. StorageGRID allows administrators to define a tenant-level maximum retention period, and any bucket default retention or object-level retain-until date must remain within that limit. The current StorageGRID tenant-creation workflow specifically provides S3 Object Lock advanced permissions for configuring this maximum retention period.
After an object's retain-until date expires, S3 Object Lock no longer prevents its deletion, allowing the backup software to perform normal expiration or cleanup operations. Platform Services are unrelated; they provide functions such as CloudMirror and event notifications. A 7-TB quota controls capacity, not retention duration or immutability.
Reference topics: Tenant Accounts S3 Object Lock Maximum Retention Period Object-Level Retention Immutable Backup Data
Question 7
You have implemented an Apache Kafka notification in Platform Services. You want to be notified in the event that Platform Services fails to send the data.
Using the storagegrid_platform_services_failed_kafka_notifications metric, which action enables you to receive notifications?
Answer : C
The correct action is to create a custom alert rule that evaluates the storagegrid_platform_services_failed_kafka_notifications Prometheus metric. StorageGRID collects operational metrics through Prometheus, and NetApp explicitly supports using those metrics as expressions in custom alert rules. When the configured expression crosses the defined threshold, StorageGRID generates an alert at the selected severity level.
For example, the administrator can create a rule under Alerts > Rules > Create custom rule and define an expression based on an increase or nonzero value for the failed Kafka notification metric. The alert can be configured with an appropriate duration and severity. Once triggered, StorageGRID can display the alert in Grid Manager and, when notification services are configured, send email or SNMP notifications to administrators.
Option B is incorrect because Grafana provides visualization of time-series metrics but does not itself establish StorageGRID alert notification logic. Option D allows an administrator to inspect or test the Prometheus metric, but merely querying it does not generate administrative notifications. Option A concerns HTTP/audit information and has no role in metric-based failure alerting.
Therefore, C is the required method for converting the Kafka failure metric into an actionable StorageGRID notification.
All Official Question Types