A customer has lost access to shares being used by an application. What are three troubleshooting steps the administrator should take? (Choose three.)

The admin SVM handles cluster management traffic and has no role in serving data shares to application clients, so its running state does not affect user or application SMB access.

A LIF can continue to serve client traffic from a non-home port after a failover event, so not residing on its home port is not a direct cause of lost share access.

All LIFs in the SVM must be operationally up to serve SMB traffic; a downed LIF prevents clients from establishing or maintaining sessions to the SVM. Verifying LIF status is a foundational step because even one failed LIF can disrupt connectivity for clients that depend on it.

The CIFS server must be running on the SVM, and the specific share must exist and be in an online state for clients to map drives or access files. This rules out service-level outages or accidental share deletion or offline status as the root cause.

Basic network connectivity between the SMB client and the SVM LIF IP must exist before any higher-layer protocol troubleshooting is meaningful. Verifying reachability via ping or traceroute isolates whether the issue is network-layer or storage-layer.