Pass the Netapp Hybrid Cloud Administrator NS0-077 Questions and answers with ExamsMirror

The correct approach is to create three separate S3 tenant accounts, one for each business unit. StorageGRID tenant accounts are designed as administrative and data-isolation boundaries. NetApp states that each tenant account has its own federated or local groups, users, S3 buckets, and objects, allowing different organizational entities to manage their own resources independently. NetApp specifically cites an enterprise use case in which separate tenant accounts are created for different departments such as Marketing, Human Resources, and Customer Support.

This design also provides delegated administration. After the grid administrator creates each tenant, authorized users for that tenant can use Tenant Manager to manage their own groups, users, S3 access keys, and buckets without gaining administrative control over resources belonging to another tenant.

Option A can segregate S3 resources with bucket policies, and NetApp documents that as a valid alternative where separate tenants are unnecessary. However, it does not provide the same strict administrative separation required here. Options B and C similarly place all business units within one tenant and therefore share the same tenant-level administrative boundary.

Therefore, D best satisfies both strict isolation and independent management.

Reference topics: Tenant Accounts → Enterprise Multitenancy → Tenant Manager → Groups and Users → S3 Buckets → Administrative Isolation

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

The correct configuration is Cross-Origin Resource Sharing (CORS). StorageGRID supports CORS specifically so that objects stored in an S3 bucket can be accessed by web applications originating from different domains. NetApp's documentation uses essentially this exact use case: an S3 bucket containing images can be configured with CORS so that those images can be displayed by a website hosted in another domain.

For a service provider hosting image objects centrally while multiple customer websites access those objects from separate domains, the browser treats the requests as cross-origin. A CORS configuration on the S3 bucket defines the permitted origins, HTTP methods such as GET, and allowed headers. The administrator can either authorize specific customer domains or, where appropriate, permit GET requests from multiple origins. HTTPS remains handled independently by the StorageGRID load balancer endpoint and its TLS certificate.

Option C is incorrect because the HTTPS certificate must match the StorageGRID endpoint domain names clients connect to, not every external website that merely references the images. Option A is unnecessary because one endpoint can service multiple domains, and Swift is unrelated.

Reference topics: Tenant Manager → S3 Buckets → Cross-Origin Resource Sharing (CORS) → Allowed Origins → Static Web Content → HTTPS S3 Access

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

The SGF6112 is specifically suited to this requirement because StorageGRID supports configuring this appliance to operate as a Gateway Node with caching. NetApp documents the SGF6112 as a compact 1U all-flash appliance containing 12 NVMe SSDs, and explicitly lists its ability to operate as a Gateway Node with caching. This enables frequently accessed S3 objects to be cached close to the application without deploying a complete StorageGRID site containing multiple Storage Nodes.

This architecture is particularly appropriate for a small office with restricted rack space and power. The caching Gateway serves repeatedly accessed objects locally, reducing retrieval latency and WAN traffic while the authoritative object data continues to reside on the existing StorageGRID Storage Nodes.

Options A and C create entirely new StorageGRID sites. A production site requires at least three Storage Nodes, which significantly increases equipment, power, cooling, and rack requirements. C additionally deploys multiple high-performance appliances when only local read acceleration is required.

Option B is invalid because the SG5812 is a Storage Node appliance and does not provide the SGF6112's supported caching-Gateway operating mode.

Therefore, D provides the required local-read performance with the smallest practical physical footprint.

Reference topics: StorageGRID 12.0 → Load Balancer Caching → SGF6112 → Gateway Node with Caching → Edge/Remote-Site Read Acceleration

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 provides S3 bucket event notifications as a platform service that can inform external applications when specified object-level events occur. NetApp documentation confirms that event-notification destinations can be an Amazon SNS topic, Kafka topic, or webhook endpoint. Therefore, both the webhook endpoint in option B and the Apache Kafka endpoint in option C can notify the application when an s3:ObjectCreated event occurs.

A webhook endpoint receives notification messages through HTTP POST requests and is appropriate when the application exposes an HTTP/HTTPS listener. A Kafka endpoint publishes the event to a configured Kafka topic, allowing an application or processing service to consume the event and immediately initiate object conversion. StorageGRID explicitly identifies sns, kafka, and webhook as supported notification endpoint types.

Option A is incorrect because a StorageGRID load balancer endpoint provides S3 client connectivity rather than bucket-event notification. Option D is also incorrect because CloudMirror replication copies objects to another S3 bucket; it is a replication service, not an application-notification mechanism.

Reference topics: Tenant Manager → Platform Services → Event Notifications → Kafka/Webhook Endpoints; S3 Bucket Notification Configuration

The correct feature is health checks. When a third-party load balancer is placed in front of StorageGRID nodes, it must continuously determine which backend nodes are healthy enough to accept S3 client traffic. NetApp specifically recommends configuring a health-check mechanism so the load balancer can test each node and remove an unhealthy or unresponsive node from the active pool.

For StorageGRID, NetApp recommends using an HTTP OPTIONS request as a health probe. The load balancer sends the request directly to each Storage Node and expects an HTTP 200 response. If a node repeatedly fails to return the expected response, the third-party load balancer marks that node offline and stops directing new client connections to it. NetApp's guidance gives an example polling interval of once per second and marking a node offline after three failed checks.

Option A, GSLB, distributes traffic between geographically separate sites or data centers rather than determining the health of an individual backend node. Option C, SSL offloading, handles TLS processing. Option D, session persistence, keeps a client's requests associated with a selected backend and does not detect failed nodes.

Therefore, B. health checks directly satisfies the requirement.

Reference topics: Third-Party Load Balancers → Backend Node Health Checks → HTTP OPTIONS Probe → Node Pool Availability → S3 Client Connectivity