How to Configure SAN Boot in a FlexPod Solution CISCO-NETAPP-FLEXPOD-IMPLEMENTATION-ADMINISTRATION-SPECIALIST Practice Questions (Page 2)

Questions 6–10

1. 6foundation · easy

   Which hardware component must be present and properly configured on a UCS server to support SAN boot?

   • AA TPM chip for secure boot
   • BA Fibre Channel adapter (vHBA) with access to the SAN fabric
   • CAn out-of-band management card with a dedicated IP
   • DA USB drive with the OS installer
   Reveal Solution Discussion Select an answer first
2. 7application · medium

   An administrator is configuring SAN boot on a Cisco UCS B-Series server. The server has two vHBAs that will be used for boot. The administrator has created a boot policy that specifies the primary and secondary vHBA. What else must be configured in the boot policy to ensure the server boots from the correct LUN?

   • ASpecify the MAC address of the vNIC and the VLAN ID for the boot network.
   • BSpecify the IP address of the NetApp storage management interface and the iSCSI target name.
   • CSpecify the boot order as 'Local Disk First' and then 'SAN Boot' to ensure fallback.
   • DSpecify the WWPN of the NetApp storage target port and the LUN ID of the boot LUN.
   Reveal Solution Discussion Select an answer first
4. 8application · medium

   A FlexPod environment is being deployed for a customer that requires rapid, consistent provisioning of new UCS B-Series blades. The storage team wants to eliminate the need to pre-stage operating system images on local disks and reduce the time to replace a failed blade. The compute team plans to use Cisco UCS service profiles to manage the blades. Which approach best meets these requirements?

   • AConfigure local boot by installing the OS on each blade's local disk and then clone the disk to other blades using UCS service profile templates.
   • BUse PXE boot from a network server to load the OS on each blade at first boot, and then switch to local disk boot for subsequent boots.
   • CCreate a boot policy that uses iSCSI to boot from a NetApp LUN, and assign it to the service profile, but do not configure any FC zones.
   • DConfigure SAN boot by creating a boot policy in the service profile that references a LUN on the NetApp storage, and assign the boot policy to the service profile.
   Reveal Solution Discussion Select an answer first
5. 9application · medium

   A FlexPod administrator is troubleshooting a SAN boot issue. The server is not seeing the boot LUN. The administrator has confirmed that the LUN is mapped to the correct igroup and that the igroup contains the correct WWPNs. What is the most likely cause of the issue?

   • AThe server's BIOS is set to boot from local disk first, and it is not checking the SAN.
   • BThe NetApp storage is not licensed for Fibre Channel.
   • CThe server's local disk is not formatted with a bootable file system.
   • DThe FC zones are not configured correctly, preventing the server from seeing the storage target.
   Reveal Solution Discussion Select an answer first
6. 10application · medium

   A NetApp administrator is configuring SAN boot for a FlexPod environment. The administrator has created a LUN and an igroup, and has mapped the LUN to the igroup. What is the next step to complete the storage-side configuration?

   • ACreate a new volume and assign it to the igroup.
   • BVerify that the LUN is visible to the server by checking the initiator group and LUN mapping.
   • CAssign the LUN a SCSI ID and configure the server's boot policy to use that SCSI ID.
   • DEnable the LUN for iSCSI and configure the igroup for iSCSI initiators.
   Reveal Solution Discussion Select an answer first