NetApp Certified Storage Installation Engineer, ONTAP Free Sample Questions

The correct action is to halt the installation until the site's power infrastructure meets the specifications outlined in the NetApp Hardware Universe. Using underrated power equipment like splitters creates a significant risk of power failure and system instability, which violates installation best practices. The engineer has a responsibility to ensure the environment is suitable to support the hardware reliably.

On FAS8300 and FAS8700 controllers, a two-node switchless cluster interconnect uses the 100 GbE ports: e0c is cabled to e0c and e0d to e0d between the two controllers. The 25 GbE ports e0a and e0b are cabled e0a-to-e0a and e0b-to-e0b as the HA interconnect only, so they are not cluster interconnect connections. e0M is the management (wrench) port, and cluster ports are never connected to a management switch.

The ANDU process is designed to be nondisruptive, and it will pause if it detects operations that could be impacted. The correct procedure is to identify the source of the lock using ONTAP commands ('vserver cifs session file show' or similar) and resolve the issue at the source (by having the user close the file) rather than forcing a disruptive action or aborting the entire process.

RAID-TEC (triple erasure coding) uses three parity disks per RAID group and protects against up to three simultaneous disk failures in a RAID group, the highest protection ONTAP RAID offers. RAID-TEC is supported on all disk types and platforms, including AFF, even though RAID-DP is the default for all-flash local tiers. RAID-DP protects against two simultaneous failures and RAID4 against one; RAID 0+1 is not an ONTAP aggregate RAID type.

ONTAP clusters can mix platforms. Nodes in an HA pair must be like controller models, but otherwise you can use any supported combination of controllers, and NetApp confirms that AFF and FAS models can be mixed in the same cluster. A 6-node cluster is well within the limits (up to 24 nodes for NAS, 12 for SAN). The cluster base license is a deprecated input and is not required. Confirm the specific platform mix and cluster-switch connectivity in the Hardware Universe, add the new nodes one at a time, and then enable storage failover for the new HA pair.

A broadcast domain groups network ports (physical ports, VLAN ports, or interface groups), usually from several nodes, that belong to the same layer 2 network; the ports in the group can then be used by an SVM for data or management traffic, and a port must be in a broadcast domain before it can host a LIF. When VLANs segregate departments such as Sales (VLAN 100) and Engineering (VLAN 200), each VLAN defines a separate broadcast domain (for example, the e0c-100 ports of all nodes in one and the e0c-200 ports in another). ONTAP also creates a failover group with the same name for each broadcast domain. An IPspace is a separate IP address space that contains broadcast domains, a failover group only lists failover targets, and an interface group aggregates physical ports.

True. Nodes communicate over a private, dedicated cluster interconnect, and NetApp's cabling best practice is to keep cluster traffic on a separate network from all other traffic. In a two-node switchless cluster the dedicated cluster ports are cabled directly between the controllers; in a switched cluster they connect to a pair of NetApp-supported cluster switches ('Only NetApp-validated back-end switches (ordered from NetApp) are supported'), which do not carry client data, management, or intercluster replication traffic. VLANs cannot be created on cluster ports, and a cluster LIF cannot be on the same subnet as a management or data LIF.

NetApp best practices for Cisco Nexus cluster switches mandate a minimum of two ISLs for redundancy. These ISLs should be configured using the last two ports on each switch (e.g., ports 31 and 32 on a 32-port switch) and cabled to the corresponding ports on the peer switch. This specific port usage is expected by the Reference Configuration File (RCF).

NetApp supplies a Reference Configuration File (RCF) for each supported cluster switch; the RCF defines the port assignments, VLANs, and network settings for cluster operation. For the BES-53248, the RCF is downloaded from the Broadcom Cluster Switches page on the NetApp Support Site (mysupport.netapp.com) and applied after the initial switch configuration, the EFOS installation, and any port licenses (with script apply, followed by write memory). The BES-53248 runs Broadcom EFOS (FASTPATH is the OS of the older NetApp CN1610), and the RCF is not an EFOS image, an ONTAP script, or a file generated by the cluster setup wizard.

The ONTAP node-removal procedure is run at the advanced privilege level. It first identifies the node that holds epsilon with cluster show and, if that node is being removed, moves epsilon before the removal: cluster modify -node -epsilon false, then cluster modify -node -epsilon true on a node that is not being removed. Only after that (and after forcing a new RDB primary if the node is the current primary) is cluster remove-node run from a node that stays in the cluster. The procedure does not rely on the removal command, or on node IDs, to reassign epsilon.