NetApp NS0-604 Hybrid Cloud - Architect Exam Practice Test

Answer : B

To add personal data identifiers from an Oracle database to NetApp BlueXP classification scans, the customer should use custom categories. Custom categories allow the user to define specific types of data (such as personal identifiers) for classification, helping BlueXP to scan and detect those specific data types within the environment.

RegEx (A) can be used for pattern matching but would require the user to manually define regular expressions, while custom keywords (D) and Data Fusion (C) are not the appropriate mechanisms for this specific use case of adding personal data identifiers to the scans. Custom categories are specifically designed for managing such identifiers.

Answer : D

If a customer needs to run some of their NetApp Cloud Volumes ONTAP instances on-premises, the best solution would be Azure Stack. Azure Stack extends Azure cloud capabilities to on-premises environments and supports hybrid workloads, including those based on Cloud Volumes ONTAP.

Other options like VMware Cloud (A), AWS Outpost (B), and Google Anthos (C) are cloud extensions but are not directly integrated with Cloud Volumes ONTAP in the same way as Azure Stack, which provides a native extension of Azure services to on-premises infrastructure.

Answer : A

The issue where the Linux client shows that the NFS volume is full, despite the AWS dashboard showing available capacity in the Amazon FSx for NetApp ONTAP file system, suggests that the allocated volume size within ONTAP is smaller than the total capacity available. To resolve this, the customer should enable volume autosizing. Autosizing allows the volume to automatically increase in size as needed, preventing issues where the volume becomes full while the underlying file system still has available storage.

Increasing the capacity of the file system (B) is not necessary since the file system already has free space. Deleting snapshots (C) can free up some space, but autosizing is a more efficient solution. Tiering cold data (D) addresses long-term storage management but won't resolve the immediate issue of the volume being full.

Answer : D

For setting up disaster recovery in the Central US region for an existing Azure NetApp Files workload in the East US2 region, the customer should use cross-region replication. This feature allows data replication across different Azure regions, providing a robust disaster recovery solution by keeping a secondary copy of the data in a geographically separate location.

Cross-zone replication (A) deals with replication within the same region across availability zones. SnapMirror (B) and SyncMirror (C) are ONTAP-specific replication technologies but are not directly applicable to Azure NetApp Files in this scenario.

Answer : B, D

For companies that have negotiated a Microsoft Azure Consumption Commitment (MACC) and want to use NetApp BlueXP data services without additional budget for the rest of the year, two licensing models can be used:

PayGo (B): This is the Pay-As-You-Go licensing model, which allows the customer to use Azure credits from their MACC for NetApp services. It aligns with the company's desire to leverage their Azure budget without incurring additional costs.

Private Offer (D): Through Azure's Private Offer model, customers can negotiate custom pricing and leverage their Azure commitment to pay for NetApp services, aligning with their existing MACC.

Keystone (A) is a subscription-based model for on-premises or hybrid environments, and BYOL (C) (Bring Your Own License) requires an upfront purchase of licenses, which would not align with the company's scenario of having no additional budget.

Answer : A, C

NetApp Keystone Storage as a Service (STaaS) offers various service levels depending on performance and latency requirements. For workloads that require less than 2ms latency, the two relevant service levels are:

Extreme (A): This service level is designed for the most latency-sensitive and high-performance workloads. It provides ultra-low latency (<2ms) and is ideal for applications that demand top-tier performance.

Premium (C): The Premium service level also supports low latency, typically less than 2ms, making it suitable for workloads with moderate to high performance requirements.

Standard (B) and Performance (D) service levels provide higher latency and are not suitable for workloads requiring less than 2ms latency.

Answer : A

NetApp AutoSupport requires outbound access to specific endpoints for delivering support data, and this communication occurs over HTTPS (port 443). The two provided NetApp AutoSupport URLs are accessed via secure HTTP (HTTPS), so the company must configure routing and firewall policies to allow outbound HTTPS traffic.

Blocking HTTPS traffic by default would prevent the AutoSupport service from functioning, which is critical for sending diagnostic information to NetApp support for monitoring and troubleshooting.

Options like NFS/SMB traffic (B), SSH/RDP traffic (C), and DNS traffic (D) are irrelevant in this context, as AutoSupport only requires secure web traffic via HTTPS.