Free Netapp NS0-077 Practice Exam with Questions & Answers

StorageGRID custom alert rules define their trigger conditions using Prometheus expressions. NetApp StorageGRID 12.0 documentation states that when creating a custom alert rule, the administrator enters a Prometheus expression for one or more alert severity levels. These expressions evaluate metrics collected from StorageGRID nodes and services and determine when an alert condition becomes true.

For this requirement, the administrator would construct an expression that evaluates both CPU and memory utilization metrics and combines the conditions logically so that the rule triggers only when CPU usage exceeds 90% and memory utilization exceeds 80% for the same applicable node. StorageGRID's Prometheus service collects time-series metrics from services throughout the grid, and those metrics are used by both the Grid Manager monitoring views and the alerting framework.

Option A is incorrect because the Grid Management REST API can expose metrics and can be used to test Prometheus queries, but it is not the syntax used to define the alert condition itself. Option B is an S3 object-query capability and is unrelated to system monitoring. Option C is not the alert-expression language.

Therefore, D. Prometheus expression is the correct answer.

Reference topics: Grid Manager → Alerts → Alert Rules → Create Custom Rule → Prometheus Metrics and Expressions → CPU/Memory Monitoring

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

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

A Global Server Load Balancer (GSLB) is the appropriate solution when StorageGRID client traffic must be intelligently directed among multiple geographically distributed sites. NetApp states that global load balancing integrates with DNS to provide intelligent routing across StorageGRID sites and can direct clients to the closest destination site, while also detecting site outages and redirecting requests to another available site. This global routing functionality is provided through a supported third-party load-balancing or DNS traffic-management solution.

A typical architecture combines GSLB at the global layer with site-local load balancers or StorageGRID Gateway Node HA groups. When an S3 client resolves the StorageGRID endpoint FQDN, the GSLB selects the appropriate site's virtual IP based on factors such as availability and network latency, thereby providing proximity-based client access.

Option B provides effective local site load balancing, but by itself does not choose the geographically closest site. Option A provides HA for interfaces within an HA group and is not a geographic traffic-management mechanism. Option C provides link-level redundancy and bandwidth aggregation rather than application-level site selection.

Therefore, D is the correct answer.

Reference topics: StorageGRID Load Balancing → Third-Party Load Balancers → Global Server Load Balancing (GSLB) → DNS-Based Site Selection → Geo-Distributed Client Access

A StorageGRID branch bucket provides access to objects from a versioned base bucket as those objects existed at a selected point or range in time. NetApp describes a branch bucket as presenting a distinct view of protected data while allowing operations on the branch to be separated from the base bucket. This makes branch buckets appropriate for use cases such as application testing, investigation, recovery workflows, development, and other activities where production data should remain undisturbed.

When creating the branch, an administrator can select a Before, After, Between, or Exclude time filter. A branch can also be configured as read-only or read-write. Importantly, object settings and objects written directly to a branch do not modify the corresponding object versions in the base bucket.

Option A is incorrect because StorageGRID is fundamentally S3 object storage; branch buckets do not provide simultaneous SMB/NFS access. Option B describes cloud tiering rather than branching. Option C describes ILM rule filtering and placement behavior, which is handled through StorageGRID ILM policies and rules, not branch buckets.

Therefore, D best represents the intended operational purpose of branch buckets: creating an isolated point-in-time data view for nondisruptive work without changing the production base bucket.

Reference topics: Tenant Manager → S3 Buckets → Branch Buckets → Base Bucket → Versioning → Time Filters → Read-only/Read-write Branches

The correct combination is read-after-new-write consistency with Balanced ingest. The workload contains log objects that are written once and subsequently read, so read-after-new-write provides the required behavior: StorageGRID guarantees read-after-write consistency for new objects, while maintaining high availability. NetApp recommends this consistency setting for most workloads. Because these SIEM log objects are not expected to be updated after creation, the eventual-consistency behavior for updates is not material to this use case.

The ingest requirement is decisive. The EC7+5 placement spans three sites, but clients must remain able to ingest when one site is unavailable. With Strict ingest, StorageGRID must satisfy the ILM placement instructions synchronously before acknowledging the write. If the required EC placement cannot be created because a site is down, the request fails. In contrast, Balanced attempts the specified ILM placement immediately but, when an outage prevents that placement, StorageGRID falls back to dual-commit protection and acknowledges the object. ILM subsequently creates the required EC7+5 placement when resources become available again.

all is inappropriate because it requires every metadata node to receive metadata immediately, reducing availability during failures. Therefore, D satisfies both immediate visibility of newly written logs and continued ingest during a site outage.

Reference topics: S3 Bucket Consistency → Read-after-new-write → ILM Ingest Behavior → Balanced vs Strict → Erasure Coding → Multisite Availability

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

NetApp StorageGRID is a distributed object-storage platform with native Amazon S3 API support, making option D the appropriate use case. NetApp positions StorageGRID for storing large quantities of unstructured data securely and durably across geographically distributed sites, with integrated Information Lifecycle Management controlling object placement, protection, retention, and storage tier throughout the object's lifecycle. These characteristics make StorageGRID particularly suitable for enterprise backup, archive, disaster-recovery, and long-term retention repositories.

S3 clients communicate with StorageGRID using object operations such as PUT Object, GET Object, and DELETE Object. StorageGRID can protect the resulting objects through replicated copies or erasure coding according to ILM policy, enabling highly durable and scalable repositories that can be accessed by authorized applications from multiple locations.

Option A describes persistent block/file-style storage normally provided to Kubernetes through CSI-backed storage services. Option B requires traditional NAS file protocols and directory-service integration rather than S3 object access. Option C describes a transactional database workload requiring low-latency SAN/block storage; StorageGRID is not a replacement for an FC SAN hosting Oracle database volumes.

Therefore, D directly aligns with StorageGRID's S3 architecture and documented use cases.

Reference topics: StorageGRID → S3 REST API → Object Storage → Backup and Archive → ILM → Replication and Erasure Coding

For regulatory retention in StorageGRID, the required mechanisms are S3 Object Lock and a compliant default ILM rule. StorageGRID implements write-once-read-many protection through S3 Object Lock. NetApp states that the global S3 Object Lock setting must be enabled before tenants can create buckets with S3 Object Lock enabled. Once enabled globally, the setting cannot be disabled.

There is also a mandatory ILM dependency. NetApp explicitly requires the default rule in every active ILM policy to be compliant before global S3 Object Lock can be enabled. A compliant default rule must maintain at least two replicated copies or one erasure-coded copy on Storage Nodes, must begin protection at day 0 using Ingest time, cannot place the protected copies in a Cloud Storage Pool, and must include a placement extending forever.

Option A is incorrect because SnapLock is an ONTAP WORM technology and is not the StorageGRID compliance mechanism. Option B is also incorrect: StorageGRID regulatory retention does not require an administrator-configured “Compliance Clock.” Object retention is enforced through S3 Object Lock retain-until dates, retention modes, legal holds, and compliant ILM placement.

Reference topics: S3 Object Lock → Regulatory Compliance → Compliant ILM Rules → Default ILM Rule → Retention and Legal Hold