Network Appliance NS0-901 - NetApp Certified AI Expert Exam

A data science team reports that their Jupyter notebook pod, which was previously working, is now failing to start. The pod's status is 'CrashLoopBackOff'. An MLOps engineer investigates and finds that the pod's PersistentVolumeClaim (PVC) is bound, but the pod logs show a "Permission denied" error when trying to write to its '/data' mount point.
The engineer checks the Trident backend configuration associated with the pod's StorageClass:
apiVersion: trident.netapp.io/v1
kind: TridentBackendConfig
metadata:
name: ontap-nas-eco
spec:
version: 1
storageDriverName: ontap-nas
managementLIF: 10.10.20.5
dataLIF: 10.10.20.10
svm: svm-prod-ds
exportPolicy: read-only-policy
What is the most likely cause of the "Permission denied" error?

• A. The Kubernetes pod has an invalid 'securityContext' that prevents it from writing to any volume.
• B. The 'dataLIF' is configured incorrectly and is unreachable from the Kubernetes nodes.
• C. The 'storageDriverName' should be 'ontap-san' for all AI workloads.
• D. The Trident backend is configured to use an export policy ('read-only-policy') that does not grant write permissions to the Kubernetes nodes.

A data scientist needs to launch a Jupyter notebook as a pod in a Kubernetes cluster. The pod requires a 50 Gi persistent volume for storing datasets and notebooks. The cluster administrator has configured a default Trident StorageClass for general-purpose use. The data scientist has the following PersistentVolumeClaim (PVC) manifest:
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: jupyter-pvc
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 50Gi
When this PVC is applied to the cluster, what will be the result?

• A. Trident will create a 1 Gi volume, as this is the default size for all PVCs.
• B. The PVC will remain in a "Pending" state until a PersistentVolume is manually created.
• C. Trident will automatically provision a 50 Gi volume on its default backend and bind it to the PVC.
• D. The PVC will fail because a 'storageClassName' is not explicitly defined.

A healthcare organization plans to use a large dataset of patient records to train a predictive model. Before training, they must identify and segregate all records containing Personally Identifiable Information (PII) to comply with privacy regulations. The data resides on an on- premises NetApp ONTAP cluster. The organization needs an automated tool to scan the data in- place and tag files containing PII without moving the data.
The project requirements are as follows:
Task: Identify PII in a large dataset.
Data_Location: On-premises ONTAP cluster.
Constraint: Data must not be moved from its source location for scanning.
Output: Tagged files containing PII.
Which NetApp tool is designed for this specific task?

• A. NetApp BlueXP classification
• B. NetApp SnapMirror
• C. NetApp FlexCache
• D. NetApp XCP

The Chief Information Security Officer (CISO) is concerned about the risk of a ransomware attack encrypting the critical vector database hosted on the NetApp AFF A-Series. The CISO wants a solution that can proactively detect and block a live attack in real-time, not just recover from a backup after the fact.
Which NetApp security feature should the architect enable on the vector database volume to meet this requirement?

• A. NetApp SnapLock (Compliance Mode)
• B. NetApp Volume Encryption (NVE)
• C. Autonomous Ransomware Protection (ARP)
• D. Multi-Admin Verification (MAV)

A network administrator, attempting to harden the security of the data center, modifies a firewall access control list (ACL). Immediately afterward, the "Advisor Assistant" application pods can no longer mount their required NFS volumes from the AFF A-Series. The MLOps team confirms the pods are stuck in a 'ContainerCreating' state with a 'MountVolume.SetUp failed... connection timed out' error. The administrator provides the new, active firewall rule:
RULE | ACTION | PROTOCOL | SOURCE_IP_RANGE | DEST_IP_RANGE | DEST_PORT --|--|-
|--||--51 | ALLOW | TCP | 10.20.5.0/24 | 10.20.10.0/24 | 2049
What is the most likely reason for the mount failures?

• A. The firewall rule is blocking the NFSv4 protocol, which requires TCP port 2050.
• B. The firewall rule is blocking the NFS lock manager (NLM) protocol, which is required for file locking.
• C. The 'SOURCE_IP_RANGE' is incorrect and does not include the Kubernetes pod IP addresses.
• D. The firewall rule is blocking the Portmapper/RPCbind service (TCP/UDP port 111), which is necessary for the initial NFS mount negotiation.