vserver security trace filter create is the appropriate command to troubleshoot why a user can read and write some files on an NFS volume but cannot read all files. The symptom points to file-level access evaluation rather than a simple export-policy failure. Export-policy check-access is useful to test whether a client can access an export path based on export rules, but it does not fully explain per-file permission differences inside the volume. security login create is for administrator login configuration and is unrelated to client file access.
security audit show does not perform targeted access-decision tracing. ONTAP security trace can be used to trace NAS access decisions and identify whether permissions, user mapping, security style, ACLs, or UNIX mode bits are causing the denial. A support engineer should use it when access is inconsistent across files in the same volume. References/topics: ONTAP security trace, NFS file access troubleshooting, UNIX permissions, mixed security styles, and NAS authorization diagnostics.

Disk 6b.39 should be replaced because the exhibit indicates one disk is the abnormal contributor to disk utilization rather than a balanced aggregate-wide load problem. When Active IQ reports 100 percent disk utilization despite low protocol operations, the support engineer must determine whether the metric reflects true client workload, background operations, or a single device causing path or service time issues. Replacing multiple disks without evidence would be excessive, and adding disks to the aggregate would not correct a failing or pathological disk that is already producing abnormal utilization. Reseating shelf module B would be appropriate if the pattern showed a path, shelf, or module-wide issue, but the scenario points to a specific disk. In disk-level troubleshooting, the correct response is to isolate the outlier device, confirm the disk ID, and replace the failing component through standard NetApp support procedures. References/topics: Active IQ disk utilization analysis, disk outlier diagnosis, ONTAP storage performance triage, drive replacement workflow, and hardware fault isolation.

The supported NetApp HCI compute-node cabling methods are the 2-cable and 6-cable configurations. The 2- cable design is a simplified topology that reduces cabling while still supporting required network connectivity. The 6-cable configuration provides greater physical separation and bandwidth for management, storage, vMotion, and VM traffic depending on the validated design. A 1-cable configuration does not provide the required redundancy and traffic separation for supported HCI compute-node deployment. A 4-cable configuration is not one of the supported compute-node cabling methods in this exam context. NetApp HCI cabling must follow validated architecture because incorrect port use or switch design can prevent the NetApp Deployment Engine from validating the environment and can create performance or availability issues. The engineer should always compare the physical cabling with the deployment guide before running or rerunning the NetApp Deployment Engine. References/topics: NetApp HCI compute-node cabling, deployment prerequisites, 2-cable topology, 6-cable topology, and validated HCI network design.
Reference: https://library.netapp.com/ecm/ecm_download_file/ECMLP2856899 (11)

Kerberos configuration should be reviewed when CIFS access issues occur only when clients access a data LIF on a specific node. Kerberos authentication relies on proper service principal names, DNS records, time synchronization, and node/LIF identity behavior. If the same share path works through other nodes or LIF locations, the issue is less likely to be the share path itself. Export policies apply primarily to NFS access and are not the correct focus for CIFS share troubleshooting. General cluster health may be checked, but it does not directly explain a node-specific CIFS authentication failure. The support engineer should investigate Kerberos and CIFS server dependencies such as DNS aliases, SPNs, domain controller communication, and the data LIF's node context. The key clue is node specificity with CIFS, which commonly points to Kerberos name or authentication path problems. References/topics: ONTAP SMB Kerberos authentication, CIFS data LIF behavior, SPN/DNS validation, node-specific CIFS access troubleshooting, and Active Directory integration.
Reference: https://library.netapp.com/ecm/ecm_download_file/ECMLP2426787

The special boot menu is used to implement Advanced Drive Partitioning when ADP is not already applied before cluster setup. ADP is a low-level disk partitioning and root/data layout choice that must be established early in the system initialization process. It is not enabled from the SP prompt, and the nodeshell is not the proper place to repartition a new system for ADP layout. The LOADER prompt alone does not perform the ADP initialization workflow; the special boot menu provides the maintenance options used for initialization and disk reconfiguration tasks. The scenario is specifically before cluster setup, which is the correct time to correct the disk layout. A support engineer must avoid building root aggregates on large whole drives when ADP is required, because doing so wastes capacity. References/topics: Advanced Drive Partitioning, root-data partitioning, special boot menu maintenance options, FAS2720 initialization, and pre-cluster-setup disk layout.