NS0-194 practice question 10 of 15
While troubleshooting client access issues to a CIFS share, you notice that the issue only occurs when the data LIF that the clients are accessing is on a specific node in the cluster. In this scenario, which configuration should you review to determine why this issue is happening?
Full set: 60 questionsThe problem is isolated to a specific node when it hosts the CIFS data LIF. This indicates a node-specific configuration or state issue rather than a cluster-wide or SVM-wide problem. CIFS authentication, particularly Kerberos, is a primary candidate. Kerberos is time-sensitive and requires that the clock on the storage node be synchronized with the Key Distribution Center (KDC), which is typically a domain controller. If a single node has a significant clock skew or a broken secure channel to the domain controller, Kerberos authentication will fail for any client connections landing on a LIF hosted by that node.
A. cluster health: A general cluster health problem would likely manifest as a more widespread or intermittent issue, not one consistently tied to a specific node hosting a LIF.
C. share path: The share path is a storage virtual machine (SVM) level configuration. An incorrect share path would cause access to fail regardless of which node's LIF the client connects through.
D. export policies: Export policies are used to control access for the NFS protocol. CIFS access is controlled by share-level permissions and NTFS file-level permissions.
1. NetApp ONTAP 9 Documentation, SMB/CIFS management, "Troubleshoot SMB server and domain issues": This guide details common SMB issues, including "Authentication failures due to time skew." It states, "Kerberos authentication can fail if the time difference between the cluster and the Windows domain controller that is acting as the Kerberos Key Distribution Center (KDC) is greater than the configured maximum clock skew (the default is five minutes)." This highlights that a time issue, which can be node-specific if NTP is misconfigured on one node, will cause Kerberos failures.
2. NetApp Technical Report 4835, "SMB Protocol Best Practices with NetApp ONTAP," Section 3.1, "Time Services": This document emphasizes the importance of time synchronization for Kerberos. It states, "Kerberos authentication is time sensitive and requires that the clocks on the client, the storage system, and the KDC are all synchronized. NetApp recommends configuring NTP on the ONTAP cluster and on the domain controllers." A failure of NTP on a single node would lead to the described scenario.
3. NetApp ONTAP 9 Documentation, SMB/CIFS management, "How Kerberos authentication works": This section explains that for Kerberos to succeed, a secure communication channel must exist between the ONTAP system and the Active Directory domain. This secure channel is established and maintained by each node that could potentially serve CIFS data, making its health a node-specific concern.
Keep practicing
Take the free NS0-194 practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other NS0-194 practice questions
- Question 1Which three techniques are used in ONTAP to improve storage efficiencies? (Choose three.)
- Question 2For security reasons, you must track the access of files of a specific folder. In this sc…
- Question 3You observe cyclic redundancy check (CRC) errors on a network port from a node in the clu…
- Question 4Your Windows clients were able to access your CIFS SVM yesterday. Today they are no longe…
- Question 7A customer receives the message shown below in their EMS logs. Tue Jun 27 18:34:18 CEST […
- Question 8Several clients are accessing an ONTAP SnapMirror DP destination volume. Some clients fre…
