NS0-403 practice question 9 of 15

A customer was running a traditional application with the data being provided by an NetApp ONTAP NFSv3 export. The customer is now migrating that same application to run with a container in a Kubernetes environment using NetApp Trident. In this scenario, how would the customer ensure that the new container-based application has access to the same data?

Full set: 60 questions
Answer options
A: Use the rsync command to copy the data to a worker node in the Kubernetes cluster and allow the kubelet to auto-discover the storage for the container.
B: Import the volume using the tridentcti command and provide the corresponding persistent volume claim YAML. Correct answer
C: Define a backend YAML in Trident and use the kubectl command to create the backend in the Trident namespace.
D: Define the connection information for the NFSv3 export in the storage class object and then reference the storage class in the persistent volume claim.
Correct Answer:
B. Import the volume using the tridentcti command and provide the corresponding persistent volume claim YAML.
Explanation

The most direct and supported method for making a pre-existing NetApp ONTAP volume, which already contains data, available to a Kubernetes pod is by using Trident's volume import feature. The tridentctl import volume command is specifically designed for this "brownfield" scenario. It inspects the existing volume on the ONTAP backend and creates a corresponding Kubernetes PersistentVolume (PV) object. Once the PV is created, a user can create a PersistentVolumeClaim (PVC) that binds to this PV, allowing the new containerized application to mount and access the original data without migration.

Why Incorrect

A. Using rsync copies the data, which does not meet the requirement of accessing the same data. This approach also breaks the persistent storage model of Kubernetes.
C. Defining a backend is a necessary prerequisite for Trident to communicate with the ONTAP system, but it does not, by itself, grant access to a specific, existing volume.
D. A StorageClass is a template used for dynamically provisioning new, empty volumes. It does not contain parameters to connect to a specific, pre-existing volume with data.

References

1. NetApp Trident Documentation, "Importing a volume": This document explicitly details the procedure for bringing an existing volume under Trident's management. It states, "If you have a volume that was created outside of Trident and you want to bring it under Trident’s management, you can use the tridentctl import volume command. This command...will then create a PV for that volume, which you can then use with a PVC." This directly supports option B.

Source: NetApp Trident Documentation, trident-use/vol-import.html

2. NetApp Trident Documentation, "StorageClass objects": This page explains that StorageClasses serve as templates for dynamic provisioning. The parameters listed for StorageClasses (e.g., provisioningType, fsType, snapshotPolicy) are for creating new volumes, not for referencing existing ones. This refutes the methodology described in option D.

Source: NetApp Trident Documentation, trident-use/k8s-storage-class.html

3. NetApp Trident Documentation, "Backend configuration": This section describes how to configure backends, which is the process mentioned in option C. The documentation clarifies that this step only enables Trident to communicate with the storage system, it is not the step that makes a specific volume available to a pod.

Source: NetApp Trident Documentation, trident-config/backend-ontap.html

Scroll to Top