The ORLM (Object Rules Met) audit message is the appropriate source for determining which ILM rule StorageGRID applied to an object. NetApp documents that ORLM is generated when object data has been successfully stored according to an ILM rule. Critically, the ORLM record contains a RULE field, which identifies the human-readable label of the ILM rule applied to that object. It also includes the object's CBID, ILM status, result, and storage-location information.

A metadata lookup in option A is valuable for verifying the current physical placement of replicated copies or erasure-coded fragments, but it does not directly identify the ILM rule responsible for that placement. NetApp specifically recommends ORLM when additional information about the ILM evaluation is required.

Option C simulates how an active ILM policy would evaluate representative metadata; it does not prove which rule was actually applied to an already-ingested object. Option D is also insufficient because an SPUT audit record confirms completion of an S3 PUT transaction and supplies identifiers such as the CBID, bucket, and key, but does not contain the applied ILM rule name.

Reference topics: Audit Logs → ILM Audit Messages → ORLM/Object Rules Met → RULE Field → Object Metadata Lookup → ILM Troubleshooting

Before adding an SG6160 appliance to an existing StorageGRID 12.0 grid, the StorageGRID Appliance Installer firmware must be compatible with the StorageGRID software version currently running on the grid. NetApp's StorageGRID 12.0 expansion requirements explicitly state that if the Appliance Installer firmware is not compatible, it must be upgraded before the appliance is deployed as a new grid node.

Because this SG6160 still contains an older 11.8-era Appliance Installer, the administrator should obtain the appropriate StorageGRID Appliances support/firmware package from NetApp Downloads and manually upgrade the appliance through the Appliance Installer's firmware-upgrade workflow. NetApp's documented procedure uses Advanced > Upgrade Firmware, followed by uploading the appropriate support file and completing the firmware update before installation.

Option A is incorrect because a newly added appliance should not be introduced with incompatible installer firmware merely to operate temporarily at a mixed version. Option D has the same problem: compatibility must be established before joining the node. Option B is incorrect because Active IQ is not the mechanism used to upgrade StorageGRID Appliance Installer firmware.

Therefore, C is the correct procedure.

Reference topics: StorageGRID Expansion → Appliance Nodes → StorageGRID Appliance Installer → Firmware Compatibility → Upgrade Firmware → SG6160 Deployment

The correct solution is the CloudMirror service. CloudMirror is a StorageGRID Platform Service that automatically replicates selected objects from a StorageGRID S3 bucket to an external S3-compatible destination, including Amazon S3. NetApp specifically identifies the use case of mirroring newly ingested customer data into Amazon S3 so that AWS services can perform analytics or other processing on that data.

CloudMirror operates independently of the grid's active ILM policies. After object ingest succeeds, StorageGRID attempts to deliver the replicated object to the configured destination as soon as possible. The tenant configures a Platform Services endpoint containing the destination Amazon S3 bucket information and credentials, then applies a CloudMirror replication configuration to the source bucket.

Option B is incorrect because cross-grid replication is designed for replication between StorageGRID systems connected through grid federation, rather than for using Amazon S3 as an external analytics destination. NetApp XCP and Robocopy are file migration/copy utilities and are not StorageGRID's native event-driven S3 replication mechanism.

Therefore, D. CloudMirror service directly satisfies the requirement to replicate newly ingested StorageGRID objects into Amazon S3 for downstream AWS processing.

Reference topics: Tenant Manager → Platform Services → CloudMirror Replication → Amazon S3 Endpoint → Hybrid Cloud Data Pipelines

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

To provide highly available access specifically to Grid Manager and Tenant Manager, the HA group must contain Admin Node interfaces. StorageGRID 12.0 documentation states that Admin Nodes provide access to these management services, whereas Gateway Nodes provide the Load Balancer service for S3 client traffic. For Grid Manager access, the HA group should contain the primary Admin Node and one or more non-primary Admin Nodes; the primary Admin Node must be configured as the primary interface in the group.

Tenant Manager also runs on Admin Nodes. Tenant users connect to an Admin Node when accessing Tenant Manager, so using multiple Admin Node interfaces behind an HA virtual IP provides the required management-interface availability.

Option B is incorrect because Gateway Nodes do not provide Grid Manager or Tenant Manager. Option D is valid for S3 client access, because both Admin and Gateway Nodes run the Load Balancer service, but it is not the correct configuration for management-interface HA. Option C corresponds to a specialized HA configuration used for S3 Select and does not satisfy the management-service requirement.

Therefore, the correct answer is A.

Reference topics: Grid Manager → High Availability Groups → Administrative Connections → Admin Nodes → Grid Manager/Tenant Manager → VIP Failover

The correct answer is Gateway Node. StorageGRID 12.0 provides load balancer caching, which is specifically designed to improve performance when workloads repeatedly access the same subset of objects. NetApp identifies AI/ML training as a strong candidate for this feature because training jobs often reread the same datasets across multiple epochs. By serving frequently requested objects from cache, StorageGRID can reduce backend object retrieval activity and lower response latency.

NetApp explicitly states that load balancer caching is available only on Gateway Nodes. Administrators enable caching on a load balancer endpoint associated with Gateway Nodes and should use dedicated cache-enabled endpoints for workloads that benefit from repeated reads. NetApp also lists data lakes, high-performance computing, AI/ML training, content distribution, media asset management, and video production as examples of workloads that can benefit from caching.

Option B is incorrect because Storage Nodes hold object data and metadata but do not provide the integrated load-balancer caching capability. Option C is incorrect even though Admin Nodes run the Load Balancer service; the caching feature itself is restricted to Gateway Nodes. Archive Nodes are unrelated to this functionality.

Therefore, D. Gateway is the verified answer.

Reference topics: StorageGRID 12.0 → Gateway Nodes → Load Balancer Caching → Cache-Enabled Endpoints → AI/ML Training Workloads

In StorageGRID, group policies are attached to a specific tenant group and define which S3 resources members of that group are permitted or denied access to. NetApp explicitly states that a group policy applies to only one group and can apply to multiple buckets. This makes B the correct answer.

Group policies are configured through Tenant Manager or the Tenant Management API and use AWS-compatible JSON policy syntax. A single group policy can therefore contain multiple Resource entries referencing different buckets and objects. In contrast, a bucket policy is attached to one specific bucket and can grant or deny access to multiple users or groups.

Options A and C are incorrect because StorageGRID does not assign precedence among group, bucket, and session policies. NetApp states that there is no difference in priority among these policy types. Authorization is determined by evaluating the applicable policy statements, with an explicit Deny overriding an Allow; it is not based on one policy class automatically taking precedence over another.

Option D reverses the relationship: it describes the scope of a bucket policy rather than a group policy.

Reference topics: Tenant Manager → S3 Access Management → Group Policies → Bucket Policies → Session Policies → AWS Policy Language

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.

Reference topics: Grid Manager → Alerts → Custom Alert Rules → Prometheus Metrics → Platform Services → Kafka Notification Monitoring

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

The increased I/O on sdc is expected when that device corresponds to storage volume 0 (/var/local/rangedb/0), because StorageGRID uses volume 0 for the Cassandra database that stores object metadata. NetApp documents that StorageGRID maintains object metadata independently from object data in Cassandra and reserves space specifically on volume 0 of every Storage Node for metadata storage and essential database operations.

Cassandra performs continuous metadata-related activity, including database reads and writes, compaction, indexing, consistency operations, and repair. Consequently, the disk containing volume 0 can exhibit noticeably higher I/O than the remaining object-storage volumes even when object data itself is reasonably balanced. NetApp diagnostic examples also show sdc associated with /var/local/rangedb/0, illustrating the relationship between this device and the StorageGRID metadata volume.

Option A does not explain persistent device-specific activity because object ingest is handled through StorageGRID services and ILM placement. Option B would indicate an object-placement issue rather than systematically higher I/O on volume 0. Option D is also incorrect because higher utilization is not necessarily caused by a larger number of stored object payloads.

Reference topics: Storage Nodes → Storage Volumes → Volume 0 → Cassandra Object Metadata → Disk I/O and Performance Monitoring