NetApp NS0-165 問題集 練習問題・模擬試験｜日本語版＆英語版対応

サンプル問題 1： A SAN Administrator is hardening the security of an iSCSI deployment. The security mandate requires Bidirectional (Mutual) CHAP authentication between the Windows Server hosts and the ONTAP storage array. The administrator configures the ONTAP cluster: cluster1::> vserver iscsi security create -vserver svm_san -initiator iqn.1991-05.com.microsoft:win-host1 -auth-type CHAP -user-name target_user -outbound-user-name initiator_user When the Windows Server attempts to discover the target and log in, the connection is instantly rejected with an "Authentication Failure" error. Based on the mechanics of Bidirectional iSCSI CHAP, which TWO of the following password/secret constraints and configuration rules must the administrator verify to resolve the login failure? (Choose 2.)

• A: Bidirectional CHAP mathematically disables Asymmetric Logical Unit Access (ALUA), forcing the administrator to manually pin the LUN to a specific physical port.
• B: In the Windows iSCSI Initiator configuration, the "Target secret" field must exactly match the password associated with the outbound-user-name (initiator_user) configured on the ONTAP array.
• C: The inbound password (used by the host to authenticate to ONTAP) and the outbound password (used by ONTAP to authenticate back to the host) MUST be mathematically identical to satisfy the IPSec mutual trust requirement.
• D: In the Windows iSCSI Initiator configuration, the "Target secret" field must exactly match the password associated with target_user on the ONTAP array.
• E: ONTAP strictly enforces that the inbound CHAP secret and the outbound CHAP secret MUST be different; using the same password for both directions poses a replay-attack vulnerability and is actively rejected by the WAFL security kernel.

サンプル問題 2： An IT Manager receives an alert that a scheduled SnapMirror transfer failed during the night. The manager logs into ONTAP System Manager and navigates to the Protection dashboard. The GUI displays a generic "Transfer Failed" status indicator on the relationship, but the network team requires the exact error code and timestamp of the network timeout to correlate with a firewall change. The manager opens an SSH session to the cluster to investigate further. ``` cluster1::> snapmirror show -destination-path svm_dest:vol_dest Progress Source Destination Mirror Relationship Total Last Path Type Path State Status Progress Healthy Updated ----------- ---- ------------ ------- -------------- --------- ------- -------- svm_src:vol DP svm_dest:vol Snapmirrored Idle - false - ``` Which TWO ONTAP CLI commands provide the granular, low-level diagnostic output required to identify the specific network timeout failure that is abstracted in the standard System Manager GUI? (Choose 2.)

• A: volume show -vserver svm_dest -volume vol_dest -fields state,status
• B: system node run -node cluster1-01 -command sysstat -c 1
• C: event log show -message-name snapmirror* -severity Error
• D: network interface show -role cluster-management -status-admin up
• E: snapmirror show -destination-path svm_dest:vol_dest -instance

サンプル問題 3： A NAS Administrator configures a new tree quota to restrict an existing qtree (qt_projectX) to 500GB. However, a developer reports they are still able to write data well beyond this specified limit. The administrator checks the active quota status via the CLI: ``` cluster1::> volume quota show -vserver svm_nas -volume vol_data Vserver: svm_nas Volume: vol_data State: on cluster1::> volume quota report -vserver svm_nas -volume vol_data Vserver: svm_nas ----Disk---- ----Files----- Quota Volume Tree Type ID Used Limit Used Limit Specifier ------- -------- ------ ------- ----- ----- ------ ------ --------- vol_data qt_home tree 1 400GB 1TB 12000 - qt_home (Note: qt_projectX is missing from the active report output) ``` Which TWO valid administrative actions will force ONTAP to compile and apply the newly created qt_projectX quota rule to the active filesystem? (Choose 2.)

• A: Re-mount the NFS export on the client workstations to clear stale capacity caches from the Linux kernel.
• B: Reboot the physical storage controller hosting the volume to flush and rebuild the quota rule tables.
• C: Execute the volume quota resize -vserver svm_nas -volume vol_data command to hot-load the new rule into memory.
• D: Execute the volume quota off followed immediately by the volume quota on command for the specific volume.
• E: Temporarily migrate the volume to a different aggregate using volume move to trigger a backend quota recalculation.