Practice Free NS0-077 NetApp StorageGRID Administrator Exam Exam Questions Answers With Explanation

StorageGRID supports webhook endpoints as destinations for S3 bucket event notifications. The purpose is to allow external applications, automation systems, or data-processing workflows to react when configured S3 events occur, such as object creation or deletion. NetApp documents that a tenant can configure an external or locally hosted webhook endpoint that accepts HTTP POST notification requests. Platform-service messages are generated from StorageGRID and delivered to the configured endpoint, enabling event-driven application integration.

This makes B the correct answer. For example, after an object is uploaded to a bucket, StorageGRID can generate a notification that is delivered to a webhook. The receiving application can then start processing, indexing, transformation, compliance validation, or another automated workflow without continuously polling the bucket.

Option A describes Cloud Storage Pools/ILM-based external storage placement, not webhook integration. Option C describes ONTAP SnapMirror orchestration, which is not the function of StorageGRID webhook notifications. Option D is also incorrect: webhook-based S3 event notifications are a tenant platform service, not a replacement for Grid-level alerting technologies such as SNMP, email notifications, and StorageGRID monitoring.

NetApp identifies platform services as including CloudMirror replication, bucket event notifications, and search integration, with webhook endpoints supported specifically for event-notification delivery.

Reference topics: Tenant Manager ? Platform Services ? S3 Event Notifications ? Webhook Endpoints ? HTTP/HTTPS POST ? Event-Driven Integration

The correct configuration is to route StorageGRID AutoSupport traffic through an Admin proxy server. NetApp states that when AutoSupport packages are transmitted using HTTPS, the primary Admin Node requires outbound access to NetApp Technical Support either directly or through a proxy server. This is specifically intended for secure environments where StorageGRID nodes cannot establish unrestricted direct internet connections.

The administrator configures this under Configuration > Security > Proxy settings > Admin, enables the Admin proxy, and specifies the proxy server hostname or IP address and port. Authentication credentials can also be supplied when required. Once configured, AutoSupport traffic from Admin Nodes to NetApp Technical Support is routed through this controlled proxy path.

This preserves normal AutoSupport functionality, including periodic and event-triggered AutoSupport packages, which support proactive monitoring and automatic support-case workflows. Manually uploading bundles, as in A, would not provide the desired automated behavior. Option B does not solve the connectivity restriction. Option C is also incorrect because AutoSupport On Demand is intended primarily for active troubleshooting and itself requires HTTPS connectivity; it does not replace normal automated AutoSupport delivery.

Therefore, D provides the required secure outbound connectivity while retaining automated NetApp support capabilities.

Reference topics: Grid Manager ? AutoSupport ? Admin Proxy ? HTTPS AutoSupport ? Event-Triggered AutoSupport ? NetApp Technical Support Connectivity

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

StorageGRID Traffic Classification Policies provide the correct quality-of-service mechanism for controlling a workload that is consuming excessive network or request resources. A traffic classification policy can match traffic by bucket, tenant, subnet, or load balancer endpoint and can impose limits such as aggregate bandwidth, per-request bandwidth, concurrent requests, or request rate. Therefore, the appropriate remediation is to identify the backup bucket and restrict the bandwidth available to that workload.

This approach prevents the backup application from monopolizing StorageGRID resources during its backup window, leaving sufficient capacity for other clients to perform object uploads. StorageGRID 12.0 documentation specifically states that bandwidth limits control the rate at which matching requests are allowed to flow and that traffic-classification policies are designed for traffic limiting and SLA-related performance management.

Option D is incorrect because StorageGRID traffic classification does not provide a mechanism to reserve or guarantee minimum bandwidth to other buckets; it limits maximum resource consumption by matching workloads. Options A and C involve ILM ingest behavior. Strict or Balanced ingest controls how object placement satisfies ILM requirements at ingest and is not a QoS mechanism for protecting competing workloads.

Therefore, throttling the backup bucket through a traffic classification policy is the correct solution.

Reference topics: Grid Manager ? Configuration ? Network ? Traffic Classification ? Bucket Matching Rules ? Bandwidth Limits ? QoS and Workload Management

When an existing StorageGRID deployment is expanded with nodes whose Grid Network IP addresses are on a subnet that has not previously been used, that subnet must be added to the Grid Network subnet list before the expansion is started. StorageGRID maintains this list so that every grid node can correctly route internal Grid Network traffic to the other participating subnets. NetApp StorageGRID 12.0 documentation explicitly states that if any new node uses a new Grid Network subnet, the administrator must add that subnet first; otherwise, the expansion must be cancelled, the subnet added, and the expansion restarted.

The configuration is performed in Grid Manager ? Maintenance ? Network ? Grid Network, where the administrator selects Add another subnet and enters the network in CIDR notation. StorageGRID then distributes the routing configuration throughout the grid.

Option A is incorrect because routes do not need to be configured manually on every node. Option B is incorrect because a StorageGRID Gateway Node provides client load-balancing functions and is not an IP router between Grid Network subnets. Option D is also incorrect; StorageGRID explicitly supports multiple Grid Network subnets, provided they are routable through the configured Grid Network gateway.

Reference topics: StorageGRID Expansion ? Grid Network ? Grid Network Subnet List ? Adding Nodes on New Subnets ? Grid Network Routing

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

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

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

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

When an object stored in a Cloud Storage Pool has transitioned to Amazon S3 Glacier Deep Archive, it is in a non-retrievable state. StorageGRID therefore cannot satisfy a normal GetObject request until a retrievable copy has first been restored. NetApp specifies that the client application must issue an S3 RestoreObject request to restore the object temporarily within the Cloud Storage Pool. After the restoration completes, the client can issue GetObject through StorageGRID to retrieve the data.

For a restored object, RestoreObject specifies how long the retrievable copy remains available. StorageGRID supports restoration from Glacier Deep Archive, but Deep Archive does not support the Expedited retrieval tier; only Standard or Bulk retrieval can be used. Thus, “immediate” access means initiating the restore process immediately, not instantaneous retrieval from the Deep Archive tier.

Option A is incorrect because GetObject does not automatically restore a non-retrievable Glacier object. Option B is incorrect because restoration is performed through StorageGRID's S3 API; direct Amazon-console intervention is unnecessary. Option C is incorrect because StorageGRID explicitly supports RestoreObject for Cloud Storage Pool objects transitioned to Glacier Deep Archive.

Reference topics: ILM ? Cloud Storage Pools ? S3 Glacier Deep Archive ? RestoreObject ? GetObject ? Retrieval Tiers

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

For a capacity-focused FabricPool repository containing predominantly cold object data, the most efficient expansion method is to add a data-only Storage Node. StorageGRID 12.0 supports combined, metadata-only, and data-only Storage Nodes. A data-only node is dedicated to object-data storage and does not participate in Cassandra metadata storage, making it particularly appropriate when the primary objective is to maximize usable object capacity rather than increase metadata capacity. NetApp specifically describes data-only, high-capacity Storage Nodes as appropriate when dedicated capacity is required.

After the node is added, erasure-coded data can be rebalanced so that existing EC fragments are redistributed across the original and newly added Storage Nodes. NetApp states that EC rebalancing redistributes erasure-coded fragments among Storage Nodes at the site, allowing newly added capacity to be utilized by an existing EC protection scheme.

Option D adds usable capacity, but a combined node also provides metadata/Cassandra functionality that is unnecessary when the goal is specifically to maximize object-data capacity for a cold FabricPool workload. Options B and C are not supported StorageGRID capacity-expansion strategies; appliance RAID/DDP configuration and SANtricity LUN sizing must not be arbitrarily changed to enlarge StorageGRID object storage.

Reference topics: StorageGRID Expansion ? Data-only Storage Nodes ? Object Capacity ? Erasure Coding ? EC Rebalancing ? FabricPool Capacity Planning

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.

Reference topics: Grid Manager ? Load Balancer Endpoints ? Tenant Access ? Allow Selected Tenants ? S3 Client Access Control ? Endpoint Binding