[Free] 2017(Nov) Dumps4cert Testinsides Cisco 300-165 Dumps with VCE and PDF Download 21-30

Dumps4cert 2017 Nov Cisco Official New Released 300-165
100% Free Download! 100% Pass Guaranteed!
http://www.Dumps4cert.com/300-165.html

Implementing Cisco Data Center Infrastructure

Question No: 21 – (Topic 2)

Which Cisco Nexus feature is best managed with DCNM-SAN?

  1. VSS

  2. domain parameters

  3. virtual switches

  4. AAA

Answer: B Explanation:

The Fibre Channel domain (fcdomain) feature performs principal switch selection, domain ID distribution, FC ID allocation, and fabric reconfiguration functions as described in the FC-SW-2 standards. The domains are configured on a per VSAN basis. If you do not configure a domain ID, the local switch uses a random ID.

This section describes each fcdomain phase:

Dumps4Cert 2017 PDF and VCE

鈥?/p>

Dumps4Cert 2017 PDF and VCE

Principal switch selection – This phase guarantees the selection of a unique principal switch across the fabric.

鈥?/p>

Dumps4Cert 2017 PDF and VCE

Domain ID distribution – This phase guarantees each switch in the fabric obtains a unique domain ID.

鈥?/p>

Dumps4Cert 2017 PDF and VCE

FC ID allocation – This phase guarantees a unique FC ID assignment to each device attached to the corresponding switch in the fabric.

鈥?/p>

Fabric reconfiguration – This phase guarantees a resynchronization of all switches in the fabric to ensure they simultaneously restart a new principal switch selection phase.

Reference: http://www.cisco.com/c/en/us/td/docs/switches/datacenter/mds9000/sw/5_2/configuration/g uides/sysmgnt/DCNM-SAN/sysmgmt_dcnm/sysmgmt_overview.html#wp1051962

Question No: 22 – (Topic 2)

Which of the following Cisco Nexus features is best managed with DCNM-LAN?

  1. VSS

  2. Domain parameters

  3. Virtual switches

  4. AAA

Answer: C Explanation:

DCNM-LAN supports the following platforms:

Dumps4Cert 2017 PDF and VCE

鈥?/p>

Dumps4Cert 2017 PDF and VCE

Cisco Nexus 1000V switches

鈥?/p>

Dumps4Cert 2017 PDF and VCE

Cisco Nexus 2000 Fabric Extenders

Dumps4Cert 2017 PDF and VCE

鈥?/p>

Dumps4Cert 2017 PDF and VCE

Cisco Nexus 3000 Series switches

Dumps4Cert 2017 PDF and VCE

鈥?/p>

Cisco Nexus 4000 Series switches

鈥?/p>

Dumps4Cert 2017 PDF and VCE

Cisco Nexus 5000 Series switches

Dumps4Cert 2017 PDF and VCE

鈥?/p>

Dumps4Cert 2017 PDF and VCE

Catalyst 6500

Dumps4Cert 2017 PDF and VCE

DCNM-LAN provides limited support for the Catalyst 6500 Series switches that runs classic IOS version 12.2(33)SXI or higher.

DCNM-LAN supports the viewing of the current configuration attributes of the device.

DCNM-LAN does not support changing the configuration of the device.

DCNM-LAN supports the Firewall Service Module (FWSM) version 4.0 or higher for the Catalyst 6500 Series switches.

鈥?/p>

Question No: 23 – (Topic 2)

Cisco Nexus 7000 Series switches

Reference: http://www.cisco.com/c/en/us/td/docs/switches/datacenter/mds9000/sw/5_2/configuration/g uides/fund/DCNM-SAN-LAN_5_2/DCNM_Fundamentals/fund_overview.html

  1. They allow reserve vNICs to be allocated out of the spares pool.

  2. They enable hardware-based failover.

  3. They select the primary fabric association for dynamic vNICs.

  4. They allow dynamic vNICs to be reserved for fabric failover.

Answer: C Explanation:

Number of Dynamic vNICs – This is the number of vNICs that will be available for dynamic assignment to VMs. Remember that the VIC has a limit to the number of vNICs that it can support and this is based on the number of uplinks between the IOM and the FI. At least this is the case with the 2104 IOM and the M81KR VIC, which supports ((# IOM Links * 15) – 2)). Also remember that your ESXi server will already have a number of vNICs used for other traffic such as Mgmt, vMotion, storage, etc, and that these count against the limit.

Adapter Policy – This determines the vNIC adapter config (HW queue config, TCP offload, etc) and you must select VMWarePassThru to support VM-FEX in High Performance mode.

Protection – This determines the initial placement of the vNICs, either all of them are placed on fabric A or Fabric B or they are alternated between the two fabrics if you just select the “Protected” option. Failover is always enabled on these vNICs and there is no way to disable the protection.

Reference: http://infrastructureadventures.com/2011/10/09/deploying-cisco-ucs-vm-fex-for- vsphere-–-part-2-ucsm-config-and-vmware-integration/

Question No: 24 – (Topic 2)

Which statement about the implementation of Cisco TrustSec on Cisco Nexus 7000 Series Switches is true?

  1. While SGACL enforcement and SGT propagation are supported on the M and F modules, 802.1AE (MACsec) support is available only on the M module.

  2. SGT Exchange Protocol is required to propagate the SGTs across F modules that lack hardware support for Cisco TrustSec.

  3. AAA authentication and authorization is supported using TACACS or RADIUS to a Cisco Secure Access Control Server.

  4. Both Cisco TrustSec and 802.1X can be configured on an F or M module interface.

Answer: A Explanation:

The M-Series modules on the Nexus 7000 support 802.1AE MACSEC on all ports, including the new M2-series modules. The F2e modules will have this feature enabled in the future.

It is important to note that because 802.1AE MACSEC is a link-level encryption, the two MACSEC-enabled endpoints, Nexus 7000 devices in our case, must be directly L2 adjacent. This means we direct fiber connection or one facilitated with optical gear is required. MACSEC has integrity checks for the frames and intermediate devices, like another switch, even at L2, will cause the integrity checks to fail. In most cases, this means metro-Ethernet services or carrier-provided label switched services will not work for a MACSEC connection.

Reference: http://www.ciscopress.com/articles/article.asp?p=2065720

Question No: 25 – (Topic 2)

The Connectivity Management Processor monitors the active supervisor module on a Cisco Nexus 7000 switch and will reboot the device in the event of a lights-out management issue. However, which option includes features that provide similar benefits in the absence of the Connectivity Management Processor?

  1. high-availability functionality from features such as vPC and NSF

  2. traditional system connectivity models like SNMP, GUI, or SSH

  3. Cisco FabricPath

  4. VDC failover

Answer: A Explanation:

vPC uses the vPC peer-keepalive link to run hello messages that are used to detect a dual- active scenario. A Gigabit Ethernet port can be used to carry the peer-keepalive messages. A dedicated VRF is recommended to isolate these control messages from common data packets. When an out-of-band network infrastructure is present, the management interfaces of the Cisco Nexus 7000 supervisor could be also used to carry keep-alive connectivity using the dedicated management VRF. When the vPC peer-link is no longer detected, a dual-active situation occurs, and the system disables all vPC port channel

member on the quot;secondaryquot; vPC peer (lower vPC role priority value). Also SVI interfaces associated to a vPC VLAN are suspended on the secondary switch. As a result, in this condition only the “primary” vPC peer actively forwards traffic on the vPC VLANs. Multiple peer-keepalive links can be used to increase resiliency of the dual-active detection mechanism.

Both the Cisco Catalyst 6500 and the Cisco Nexus 7000 offer a variety of high-availability features. Some of the primary features to highlight are In Service Software Upgrade (ISSU), Stateful Switchover (SSO), and Nonstop Forwarding (NSF). The operation and the behavior of these features are unique to the respective platform and can be independently executed without affecting the interoperability between the two platforms.

Reference: http://www.cisco.com/c/en/us/products/collateral/switches/catalyst-6500-series- switches/white_paper_c11_589890.html

Question No: 26 – (Topic 2)

Which option is a restriction of the unified ports on the Cisco UCS 6200 Series Fabric Interconnect when connecting to the unified fabric network?

  1. Direct FC connections are not supported to Cisco MDS switches

  2. The FCoE or Fibre Channel port allocations must be contiguous on the 6200.

  3. 10-G Fibre Channel ports only use SFP interfaces.

  4. vPC is not supported on the Ethernet ports.

Answer: B Explanation:

When you configure the links between the Cisco UCS 2200 Series FEX and a Cisco UCS 6200 series fabric interconnect in fabric port channel mode, the available VIF namespace on the adapter varies depending on where the FEX uplinks are connected to the fabric interconnect ports.

Inside the 6248 fabric interconnect there are six sets of eight contiguous ports, with each set of ports managed by a single chip. When uplinks are connected such that all of the uplinks from an FEX are connected to a set of ports managed by a single chip, Cisco UCS Manager maximizes the number of VIFs used in service profiles deployed on the blades in the chassis. If uplink connections from an IOM are distributed across ports managed by separate chips, the VIF count is decreased.

Reference: http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/hw/6200-install- guide/6200_HIG/6200_HIG_chapter_01.html

Topic 3, Implement Routing and Switching Protocols

Question No: 27 – (Topic 3)

Which SCSI terminology is used to describe source and destination nodes?

  1. hosts and targets

  2. initiators and targets

  3. HBA and disks

  4. initiators and disks

  5. HBA and targets

Answer: B Explanation:

In computer data storage, a SCSI initiator is the endpoint that initiates a SCSI session, that is, sends a SCSI command. The initiator usually does not provide any Logical Unit Numbers (LUNs).

On the other hand, a SCSI target is the endpoint that does not initiate sessions, but instead waits for initiators#39; commands and provides required input/output data transfers. The target usually provides to the initiators one or more LUNs, because otherwise no read or write command would be possible.

Reference: http://en.wikipedia.org/wiki/SCSI_initiator_and_target

Question No: 28 – (Topic 3)

Which statement about Cisco FabricPath is true?

  1. It is the best solution for interconnecting multiple data centers.

  2. It optimizes STP throughout the Layer 2 network.

  3. It is a simplified extension of Layer 3 networks across a single data center.

  4. The Cisco FabricPath domain appears as a single STP bridge, where each edge port uses the same MAC address.

Answer: D Explanation:

To have a loop-free topology for the CE/FabricPath hybrid network, the FabricPath network automatically displays as a single bridge to all connected CE devices. The STP domains do not cross into the FabricPath network. If multiple STP domains are defined, BPDUs and topology change notifications (TCNs) are localized to the domain. If a connected STP domain is multihomed to the FabricPath domain, a TCN must be able to reach to all devices in the STP domain through the FabricPath domain. As a result, the TCN is sent to the FabricPath domain through the IS-IS protocol data unit (PDU) by default.

Reference: http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/mkt_ops_guides/513

_n1_1/n5k_ops_fabricpath.html

Question No: 29 – (Topic 3)

What is the grace period in a graceful restart situation?

  1. how long the supervisor waits for NSF replies

  2. how often graceful restart messages are sent after a switchover

  3. how long NSF-aware neighbors should wait after a graceful restart has started before tearing down adjacencies

  4. how long the NSF-capable switches should wait after detecting that a graceful restart has started, before verifying that adjacencies are still valid

Answer: C Explanation:

Graceful restart (GR) refers to the capability of the control plane to delay advertising the absence of a peer (going through control-plane switchover) for a quot;grace period,quot; and thus help minimize disruption during that time (assuming the standby control plane comes up). GR is based on extensions per routing protocol, which are interoperable across vendors. The downside of the grace period is huge when the peer completely fails and never comes up, because that slows down the overall network convergence, which brings us to the final concept: nonstop routing (NSR).

NSR is an internal (vendor-specific) mechanism to extend the awareness of routing to the standby routing plane so that in case of failover, the newly active routing plane can take charge of the already established sessions.

Reference: http://www.ciscopress.com/articles/article.asp?p=1395746amp;seqNum=2

Question No: 30 – (Topic 3)

In policy-based routing, which action is taken for packets that do not match any of the route-map statements?

  1. forwarded after the egress queue empties on the outbound interface

  2. forwarded using the last statement in the route map

  3. forwarded using the closest matching route-map statement

  4. forwarded using destination-based routing

Answer: D Explanation:

Each entry in a route map contains a combination of match and set statements. The match statements define the criteria for whether appropriate packets meet the particular policy (that is, the conditions to be met). The set clauses explain how the packets should be routed once they have met the match criteria.

You can mark the route-map statements as permit or deny. You can interpret the statements as follows: