Cisco 400-051 - CCIE Collaboration Written Exam

Answer : D

Explanation:
Using the AFG will allow you to get this license mac before even touching the server. It is provided after filling in the main form of the AFG but it can also be found by looking at the last few lines of your platformconfig.xml file.
Once you have the xml files, you will need to map those to the floppy drive of the VM (no usb support on the VM OVA). There are many ways to do this. I simply use a freeware virtual floppy app that I drop the platformconfig.xml file on and then copy the*.flp image out to the datastore. I"™ll end up with a directory on my datastore called AFG that has the host named *.flp images that I will use during install. It also serves as archival of these files in the event the server needs to be re-imaged. This is important because the license mac will change if every parameter is not entered exactly as it was prior. If the license mac changes, you will have to go through the process of requesting new license files to be generated.
References: http://angryciscoguy.com/jello/cisco-answer-file-generator-to-the-rescue/

Answer : E

Explanation:
is

VMware vCenter -
when deploying on
UC on UCS Tested Reference Configuration hardware
-> optional
when deploying on
UC on UCS Specs-based and Third-party Server Specs-based hardware
.
-> mandatory
-> vCenter Statistics Level 4 logging is mandatory so that Cisco TAC is able to provide effective support.

Click here -
-> for how to configure VMware vCenter to capture these logs. If not configured by default, Cisco TAC may request enabling these settings in order to provide effective support.
-> Also note that enablement of specific VMware vSphere management features may require vCenter and/or a higher feature Edition of vSphere ESXi.
-> Cisco Collaboration does not require its own dedicated vCenter.
-> Note that when VMware vCenter is not required and is not used, then VMware vSphere ESXi's default management interface is its free/included VMware vSphere Client (formerly branded VI Client).
Reference: http://docwiki.cisco.com/wiki/Unified_Communications_VMware_Requirements

Answer : D

Explanation:
What does a TRC definition include?
-> Definition of server model and local components (CPU, RAM, adapters, local storage) at the orderable part number level.
-> Required RAID configuration (e.g. RAID5, RAID10, etc.) - including battery backup cache or SuperCap - when the TRC uses DAS storage
-> Guidance on hardware installation and basic setup (e.g. click here).
-
Click here for detailed Cisco UCS server documentation
regarding hardware configuration procedures.
- Configuration of Virtual-to-physical network interface mapping is design-dependent and not included in TRC definition.
- Configuration of adapters (such as Cisco VIC, 3rd-party CNA / NIC / HBA) is design-dependent and not included in TRC definition.
- Configuration settings or step by step procedures for hardware BIOS, firmware, drivers, RAID setup are not included.
Click here for detailed Cisco UCS
server documentation
.
-> Design, installation and configuration of external hardware is not included in TRC definition, such as:
- Network routing and switching (e.g. routers, gateways, MCUs, ethernet/FC/FCoE switches, Cisco Catalyst/Nexus/MDS, etc.)
- QoS configuration of route/switch network devices
- Cisco UCS B-Series chassis and switching components (e.g. Cisco UCS 6100/6200, Cisco UCS 2100/2200, Cisco UCS 5100)
- Storage arrays (such as those from EMC, NetApp or other vendors)
-> Configuration settings, patch recommendations or step by step procedures for VMware software are not included in TRC definition.
-> Infrastructure solutions such as Vblock from Virtual Computing Environment may also be leveraged for configuration details not included in the TRC definition.
Reference: http://docwiki.cisco.com/wiki/UC_Virtualization_Supported_Hardware#UC_on_UCS_Tested_Reference_Configurations

Answer : A

Explanation:
Definition of server model and local components (CPU, RAM, adapters, local storage) at the orderable part number level.
-> Required RAID configuration (e.g. RAID5, RAID10, etc.) - including battery backup cache or SuperCap - when the TRC uses DAS storage
-> Guidance on hardware installation and basic setup.
- Configuration of Virtual-to-physical network interface mapping is design-dependent and not included in TRC definition.
- Configuration of adapters (such as Cisco VIC, 3rd-party CNA / NIC / HBA) is design-dependent and not included in TRC definition.
-> Design, installation and configuration of external hardware is not included in TRC definition, such as:
- Network routing and switching (e.g. routers, gateways, MCUs, ethernet/FC/FCoE switches, Cisco Catalyst/Nexus/MDS, etc.)
- QoS configuration of route/switch network devices
- Cisco UCS B-Series chassis and switching components (e.g. Cisco UCS 6100/6200, Cisco UCS 2100/2200, Cisco UCS 5100)
- Storage arrays (such as those from EMC, NetApp or other vendors)
-> Configuration settings, patch recommendations or step by step procedures for VMware software are not included in TRC definition.
-> Infrastructure solutions such as Vblock from Virtual Computing Environment may also be leveraged for configuration details not included in the TRC definition.
References:

Answer : E

Explanation:
Cisco Discovery Protocol provides an additional capability not found in LLDP-MED that allows the switch to extend trust to the phone. In this case, the phone is now trusted to mark the packets received on the PC port accordingly. This feature can be used to off-load the switch because now it does not need to police the information being received from the phone.