Netapp Updated NS0-077 Exam Questions and Answers by veronica

To delete a specific version of an S3 object, the user must have the appropriate S3 permission, specifically s3:DeleteObjectVersion. In StorageGRID, permissions granted to tenant users are commonly defined through group policies, which control which S3 actions members of the group are authorized to perform against specified bucket and object resources. NetApp explicitly maps s3:DeleteObjectVersion to the S3 operation that deletes a specific object version.

Therefore, the user should verify the group policy associated with their tenant account and confirm that it allows s3:DeleteObjectVersion for the required bucket or object ARN. An explicit Deny for this action would override an Allow. NetApp even provides policy examples that specifically restrict users from deleting versioned objects by denying s3:DeleteObjectVersion.

Option B is incorrect because an S3 lifecycle policy automates object expiration and version-management behavior; it does not grant interactive user permissions. Option C governs where and how StorageGRID stores and protects object data, not S3 authorization. Option D refers to administrative privileges and is not the standard mechanism controlling a tenant user's object-level S3 operations.

Therefore, A. group policy is correct.

Reference topics: Tenant Manager → Groups → S3 Group Policies → s3:DeleteObjectVersion → Versioned Object Permissions → Explicit Deny/Allow Evaluation

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

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

FabricPool normally connects ONTAP to StorageGRID through an HTTPS load balancer endpoint. That endpoint uses a server certificate so that ONTAP can authenticate the StorageGRID service. NetApp specifically warns that if the certificate securing the ONTAP-to-StorageGRID connection expires, FabricPool temporarily stops working and ONTAP loses access to data tiered to StorageGRID.

The same problem can occur when the endpoint certificate is renewed or replaced in StorageGRID but the corresponding trusted certificate on ONTAP is not updated. NetApp requires the StorageGRID and ONTAP certificate configurations to remain synchronized; after certificate replacement or renewal, ONTAP must trust the new certificate chain.

The scenario also eliminates the node-failure answers. The two Gateway Nodes are configured in an HA group, so failure of one Gateway Node should not independently cause the FabricPool endpoint to become unavailable. Likewise, losing one Storage Node does not normally prevent access to the StorageGRID S3 service. A Client Network trust-state change would have broader networking implications and does not fit the isolated, time-related FabricPool failure described.

Therefore, C is the correct answer.

Reference topics: FabricPool Integration → StorageGRID Load Balancer Endpoints → HTTPS/TLS Certificates → Certificate Expiration and Rotation