Free Practice Questions for Netapp NS0-162 Exam

FC switch zoning is the process of assigning a set of WWPNs to a zone, which is a group of ports that can communicate with each other. Zoning is required for FC SAN hosts to access LUNs on the SVM. If the zoning is not done correctly, the host might not be able to discover the LUNs or might see LUNs that belong to other hosts. Therefore, FC switch zoning is a possible cause of the issue with SVM eplc_fcp when mapping a namespace to a host. References :- Configure an SVM for FC, Configure FC protocol and FCoE protocol on SVMs with System Manager

 The problem is that the host IP address does not match the export policy rule. The export policy rule shown in the exhibit specifies that any client with an IP address within the 10.0.1.0/24 subnet can access the volume using NFSv3, as indicated by “Access Protocol” set to “any” and “Client Match” set to “10.0.1.0/24”. However, the Linux host has an IP address of 10.0.1.24, which falls outside this range, leading to a mismatch between the host IP and export policy rule. To fix this problem, the export policy rule should be modified to include the host IP address or a broader subnet that covers it. References :- Add a rule to an export policy, vserver export-policy rule create, Create an export policy for the volume

 The route is a network configuration that defines how the traffic from a LIF is routed to a destination. The route consists of a destination, a gateway, and a metric. The destination is the IP address or subnet that the LIF wants to reach. The gateway is the IP address of the next-hop router that forwards the traffic to the destination. The metric is a numerical value that indicates the preference of the route. In this scenario, the route for the SVM vs0 has a destination of 0.0.0.0/0, which means any IP address or subnet. The gateway is 10.61.208.1, which is the IP address of the router that connects the LIF to the rest of the network. The metric is 20, which is a relatively low value that indicates a high preference. However, the gateway is incorrect, as it does not match the subnet of the LIF. The LIF has an IP address of 192.0.2.130 and a netmask of 255.255.255.0, which means its subnet is 192.0.2.0/24. The gateway should be an IP address within the same subnet, such as 192.0.2.1. This would allow the LIF to communicate with the router and reach other destinations. The incorrect gateway causes connectivity issues, as the LIF cannot find a valid route to send or receive traffic. To resolve this issue, the route needs to be modified to reflect the correct gateway using the network route create or network route modify commands or the System Manager GUI12. References :- Create a route, Modify a route

To enable Active Directory (AD) domain users and groups to access the cluster or SVMs for administration purposes, you need to set up an authentication tunnel through an SVM that has a CIFS server created and joined to the domain. This can be either an existing CIFS SVM or a dedicated admin SVM. You also need to use the vserver active-directory create command to create a computer account on the domain for the SVM that you want to access. This command works for both CIFS and non-CIFS SVMs. Configuring an authentication tunnel through anadmin SVM or an existing CIFS SVM are both valid actions to accomplish this task. However, using the vserver active-directory create command to create a computer account on the domain for a CIFS SVM is not necessary, as this is done automatically when the CIFS server is created and joined to the domain. References :- Configure Active Directory domain controller access overview, How to configure AD authentication for cluster when CIFS is not licensed, Create a CIFS server

 The broadcast-domain split command allows you to create a new broadcast domain by moving one or more ports from an existing broadcast domain to the new one. In this scenario, you can use this command to move the e0e and e0c ports from the Default broadcast domain to a new broadcast domain in the same IPspace. This would satisfy the requirement of creating a new broadcast domain with the specified ports. The other options are not valid for this scenario, as they either create a new broadcast domain without moving any ports (A), merge two existing broadcast domains into one (D), or require a graphical user interface ©. References :- network port broadcast-domain split, Create a broadcast domain

 The number of ISCSI LIFs that will be created from the SVM setup wizard, as shown in the exhibit, is 16. This is because the LIFs per node field is set to 2, and there are 4 nodes in the cluster. Therefore, the total number of LIFs is 2 x 4 8 for each SVM, and since there are two SVMs, the total number of LIFs is 8 x 2 16. The other options are incorrect because they do not match the calculation based on the exhibit. References :- Configure an SVM for iSCSI, Configure iSCSI on an existing SVM

The security method that would be used to authenticate targets and initiators in an ISCSI environment is CHAP. CHAP stands for Challenge Handshake Authentication Protocol, and it is a method that validates the identity of targets and initiators during the initial link. CHAP uses a shared secret (a password) that is exchanged between the target and the initiator in a challenge-response manner. CHAP can be used in both one-way and mutual modes, depending on whether both parties need to authenticate each other or not. The other options are not valid for this scenario because:

NIS is a network information service that provides centralized management of user accounts and host names, but it does not provide authentication for ISCSI devices.

LDAP is a protocol for accessing and managing directory services, such as user and group information, but it does not provide authentication for ISCSI devices.

/etc/hosts is a file that maps host names to IP addresses, but it does not provide authentication for ISCSI devices. References :- How iSCSI authentication works, Securing iSCSI Devices, Configure iSCSI authentication

 NetApp’s All SAN Array (ASA) is a dedicated SAN-only solution that provides high performance and availability for mission-critical applications. ASA supports up to 2-node clusters, which can be either HA pairs or MetroCluster configurations. ASA does not support single node, 12-node, or 24-node clusters, as these are reserved for ONTAP systems that support both SAN and NAS protocols. References :- All-Flash SAN Array (ASA) A-Series Systems, All-Flash SAN Array software configuration overview, ASA system does not report as SAN optimized

 To configure data-at-rest encryption for your NetApp ONTAP 9.8 cluster without KMIP services, you need to enable onboard key management and cluster-wide FIPS-compliant mode. Onboard key management allows you to use a passphrase to generate and protect the cluster-wide encryption key, which is used to encrypt the disk encryption keys. Cluster-wide FIPS-compliant mode ensures that the encryption algorithms and modules used by ONTAP are compliant with the Federal Information Processing Standard (FIPS) 140-2. These two actions will satisfy the requirements of data security and passphrase protection for your cluster. References :- NetApp Encryption overview, Configure onboard key management, Enable cluster-wide FIPS-compliant mode