Important NetApp NS0-077 Exam Questions

Answer: A

Explanation:

StorageGRID evaluates ILM rules sequentially from the top of the active policy. As soon as an object matches a rule, that rule's placement instructions are applied and the object is not evaluated against subsequent rules. Therefore, the rule containing the specific status=archive filter must appear before the catch-all rule.

In option A, objects tagged status=archive match Rule 1 and receive 4+2 erasure coding at the designated single-site storage pool. StorageGRID supports 4+2 erasure coding in a one-site storage pool provided that at least six data-capable Storage Nodes are available; seven are recommended.

Objects without the archive tag do not match Rule 1 and proceed to Rule 2. Rule 2 serves as the default rule, providing two replicated copies across the required sites. NetApp requires the default rule to be last and to have no filters, ensuring that it catches every object not matched earlier.

Option C is incorrect because its unrestricted first rule would match every object, preventing the archive-specific rule from ever being evaluated. B applies the protection methods to the wrong object classes, while D provides no rule for non-archive objects.

Reference topics: ILM Policies Rule Evaluation Order Advanced Filters/Object Tags Default Rule Replication Single-Site Erasure Coding

Answer: B

Explanation:

The feature that enables multiple active ILM policies is ILM policy tags. NetApp StorageGRID allows administrators to create multiple ILM policies and associate each policy with a specific policy tag. Tenants can then assign one of those ILM policy tags to an S3 bucket, causing objects in that bucket to be managed by the ILM policy associated with the selected tag. This enables different buckets to receive different data-protection, placement, retention, or performance treatments while those policies remain active simultaneously.

StorageGRID also maintains a Default ILM policy tag. Every grid must have an active policy associated with the Default tag, and that policy governs objects in buckets that do not have another ILM policy tag assigned. NetApp supports up to 10 policy tags per grid.

Option A is too general. Although StorageGRID implements the assignment on an S3 bucket, the enabling construct is specifically the ILM policy tag. Option C, multitenancy, separates tenant resources but does not itself permit multiple active ILM policies. Option D, IAM policy, controls S3 access permissions and authorization rather than ILM placement or retention behavior.

Therefore, B is the correct answer.

Reference topics: ILM Policy Tags Multiple Active Policies Default Policy Tag Per-Bucket ILM Assignment

Answer: D

Explanation:

StorageGRID 12.0 introduces an integrated mechanism for long-term log archival to an S3 system bucket. NetApp specifically identifies this as a StorageGRID 12.0 manageability enhancement: the former Audit and syslog server page was renamed Log management, with functionality added for storing logs in a system bucket for backup purposes.

From Grid Manager, the administrator uses Log management Log location Use a bucket and enables archive logs. A tenant and S3 bucket can then be created or selected. StorageGRID automatically stores rotated log files in that bucket, using object keys beginning with system-logs/. This eliminates the need for node-level scripts or periodic manual copying.

Option A is incorrect because StorageGRID already performs native log rotation; custom rotation scripts do not provide the StorageGRID 12.0 archival mechanism. Option B refers to legacy audit-export behavior rather than the new long-term backup capability. Option C is technically possible as a manual administrative operation but does not satisfy the requirement for automatic backup.

For compliance retention, administrators can additionally control archived-log lifetime through an ILM rule or S3 bucket lifecycle policy.

Reference topics: Grid Manager Log Management Log Location System/S3 Bucket Archive Logs Log Retention

Answer: D

Explanation:

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

Answer: B

Explanation:

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