NS0-604 Hybrid Cloud - Architect Practice Questions

For Cloud Volumes Service (and Azure NetApp Files), performance is directly tied to the allocated volume quota. The throughput is calculated as a fixed amount per terabyte of provisioned capacity, determined by the selected service level (e.g., Standard, Premium, Extreme for CVS). A larger volume in the same service level will have higher performance.

NetApp provides a pre-defined IAM policy in JSON format that contains the exact, least-privilege permissions required by the Connector to function. The recommended and most secure method is to use this policy document to create the IAM role. This ensures the Connector has all necessary permissions without being overly permissive, adhering to the principle of least privilege.

The volume show-footprint command is a powerful tool for analyzing space usage within a volume. Crucially for FabricPool, it provides a temperature breakdown, showing how much data is considered 'hot' versus 'cold' based on recent activity. This allows an administrator to verify if the system recognizes data as inactive and therefore ready to be tiered.

This is true. BlueXP is designed for multi-account and multi-cloud management. To manage resources in another AWS account, you would add a new set of credentials for that account into BlueXP. The Connector would then be authorized to deploy and manage resources in the second account using cross-account IAM roles, without requiring any VPC peering or direct network connectivity between the accounts.

The key to non-disruptive DR testing is using FlexClone. A FlexClone is an instantaneous, space-efficient, writable copy of a volume. By creating a FlexClone of the read-only SnapMirror destination volume, the application can be fully tested against a writable dataset. Meanwhile, the underlying SnapMirror relationship remains active and continues to replicate data, ensuring the DR copy is up-to-date. Once testing is complete, the clone is simply deleted.

The correct architecture for Azure NetApp Files is to create a delegated subnet within the VNet where clients need access. This places the ANF service endpoint directly on the VNet, providing the lowest latency and secure, private access without traversing a gateway or peering link. Service endpoints and peering are valid networking concepts but are not the specific, required method for integrating ANF.

For a Cloud Volumes ONTAP HA pair in AWS, a floating IP address is required for data LIFs to ensure seamless failover. This IP address is automatically moved to the active node during a failover event by updating the VPC route tables. Without it, clients connected to the failed node's IP will lose connection, as the IP is not automatically re-associated with the surviving node.

BlueXP uses a combination of Roles and Workspaces to enforce RBAC. 'Roles' define what actions a user can perform (e.g., create volumes, manage backups), while 'Workspaces' define which resources (e.g., specific ONTAP clusters or cloud environments) those actions can be performed on. Together, they allow for granular, least-privilege access control.

Cloud Volumes ONTAP supports integrating with external key managers. The correct procedure is to configure the SVM to connect to an external KMIP-compliant server, such as AWS KMS, Azure Key Vault, or a third-party KMIP server. This allows for customer-managed keys without requiring data migration. Re-keying volumes can then be done online.

FabricPool is the NetApp ONTAP technology designed for automatic, block-level data tiering from a performance tier (SSD aggregate) to a capacity tier (cloud object storage like Google Cloud Storage). It operates transparently to applications, as the file metadata remains on the performance tier, making it the ideal solution for this use case.