NS0-157 · Question #33
A customer has configured SnapDrive for Windows to assist in creating Snapshot copies of a LUN. In SnapDrive, the transport protocol configuration uses the vsadminuser account for authentication…
The correct answer is C. SnapDrive requires a cluster-wide privileged account. SnapDrive for Windows requires cluster-level administrative credentials; the SVM-scoped vsadmin account does not have the cluster-wide privileges needed for the transport protocol connection.
Question
A customer has configured SnapDrive for Windows to assist in creating Snapshot copies of a LUN. In SnapDrive, the transport protocol configuration uses the vsadminuser account for authentication. SnapDrive fails to connect to the SVM. Why did this failure occur?
Options
- ATransport protocol requires a domain Windows account.
- BThe vsadmin account is locked or does not have a password.
- CSnapDrive requires a cluster-wide privileged account.
- DTransport protocol requires a local Windows account.
How the community answered
(18 responses)- A6% (1)
- B6% (1)
- C78% (14)
- D11% (2)
Why each option
SnapDrive for Windows requires cluster-level administrative credentials; the SVM-scoped vsadmin account does not have the cluster-wide privileges needed for the transport protocol connection.
SnapDrive transport protocol authentication uses ONTAP credentials, not Windows domain accounts; Windows directory accounts are unrelated to ONTAP API authentication.
A locked vsadmin account would prevent login, but the root cause here is that vsadmin is SVM-scoped and structurally lacks the cluster-level privileges SnapDrive requires, not a lock or missing password.
SnapDrive for Windows uses ONTAP APIs over its configured transport protocol to perform storage management operations that span cluster-level resources. The vsadmin account is restricted in scope to a single SVM and lacks the cluster-wide administrative access that SnapDrive requires for authentication and LUN management, causing the connection to fail regardless of network reachability.
SnapDrive transport protocol authentication is based on ONTAP user accounts, not local Windows accounts; local Windows accounts have no role in ONTAP API connectivity.
Concept tested: SnapDrive for Windows cluster-level authentication requirements
Source: https://docs.netapp.com/us-en/snapdrive-windows/
Topics
Community Discussion
No community discussion yet for this question.