Valid 300-165 Dumps shared by ExamDiscuss.com for Helping Passing 300-165 Exam! ExamDiscuss.com now offer the newest 300-165 exam dumps, the ExamDiscuss.com 300-165 exam questions have been updated and answers have been corrected get the newest ExamDiscuss.com 300-165 dumps with Test Engine here:
Access 300-165 Dumps Premium Version
(326 Q&As Dumps, 35%OFF Special Discount Code: freecram)
| Exam Code: | 300-165 |
| Exam Name: | Implementing Cisco Data Center Infrastructure |
| Certification Provider: | Cisco |
| Free Question Number: | 150 |
| Version: | v2018-05-07 |
| Rating: | |
| # of views: | 943 |
| # of Questions views: | 63740 |
| Go To 300-165 Questions | |

Recent Comments (The most recent comments are at the top.)
No.# it must be C.
No.# Its A, B D. Switch IDs can be configured manually its not a necessity!
No.# This one should be C. When enabling peer-switch both vPC peer switches will act as a root for eachother. This also means they will use the same root ID / bridge iD. F. doesn't make sense, because the vpc secondary switch also serves as a STP root, so not only the primary....
When peer-switch is enabled, each Nexus 7000 switch shares a virtual bridge ID, which allows both switches to act as root for the VLAN. For devices with a connection to each Nexus 7000 switch in the vPC domain that are not capable of port channeling, the Layer 2 (L2) topology relies on Spanning Tree Protocol (STP) in order to block the redundant links. The peer-switch feature allows for pseudo-STP configurations to allow non-vPC connections to load balance STP states between the two Nexus 7000 switches. This document discusses in detail the reason for the pseudo-STP configurations and how they affect non-vPC and vPC links.
https://www.cisco.com/c/en/us/support/docs/routers/7000-series-routers/116140-config-nexus-peer-00.html#anc11
No.# To enable the graceful restart feature you actually on have to use "graceful-restart" if you want to use the helper feature aswell, you can also enable the graceful-restart-helper. Probably because the answer is not in global config mode....
But it should be A.
https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus7000/sw/unicast/command/reference/n7k_unicast_cmds/l3_cmds_g.html
No.# This should be B and D. Only one SAN zone set can be active per VSAN, but when activated its automatically activated on all fabric nodes. You have the option to manually disable it per node, but not a requirement.
No.# Obviously LACP so B and the other one would be D. non-LACP Etherchannel
https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/layer2/b_Cisco_Nexus_5000_Series_NX-OS_/Cisco_Nexus_5000_Series_NX-OS__chapter8.pdf
PAgP is not supported on Nexus, so its not an option for vPC
Cisco Fabric Services protocol is not a link aggregation protocol
VSL control link is actually used for VSS (Catalyst portchannels) so that has nothing to do with vPC
No.# Hosts in the "acl" class are exempt from the quiet-mode. Quiet-mode actually denies all SSH and telnet sessions when the block for command hits in. Which means block for 60 seconds when there is 10 failed attempts within 180 seconds.
So the only correct answer would be B. As they are excluded from this blocking period.
https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/sec_usr_cfg/configuration/xe-3s/sec-usr-cfg-xe-3s-book/sec-login-enhance.html
No.# I would go for A and C. Policy based routing gives the preference to the policy routing first. Next hop is configured before the default next hop. So in case that next hop has a higher metric (less preferred in the routing table) it will still gets preferences because of the overrule from policy routing. Which means the packet is not being routed as desired. If the lower metric is in place, then there is no problem i would say.
No.# You dont do anything with keep alive when implementing vpc+ with fabricpath. Also configuring PagP or EtherChannel doesnt make sense.
So for me it should be B, D and E.
No.# Should be C. as the peer gateway command in a vpc configuration wants to bring down the usage of the vPC peer link between the peer switches. So there is no reason to try and improve a fallback mechanism as stated in D.
No.# bpdufilter has been configured globally for edge devices. Which means it prevents edge devices from sending or receiving BPDU's globally, answer D
bpduguard is enabled for the interface range e1/1-24, when either of these ports receive a BPDU, BPDU Guard will disable the port. There is actually no answer which is describes this correctly, but if B. would've been described better i would go for B.
No.# Answer should be D. multicast.
B. VXLAN is a overlay technology and VTEP is part of this -> VXLAN tunnel endpoint (VTEP). So thats incorrect.
Multicast used as an underlay technology for remote VTEP discovery
https://www.cisco.com/c/en/us/td/docs/switches/datacenter/pf/configuration/guide/b-pf-configuration/IP-Fabric-Underlay-Options.pdf
https://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/nx-os-software/200262-Configure-VxLAN-Flood-And-Learn-Using-Mu.html#anc6
No.# B. should be the correct one in this case. There is no vPC or anything else mentioned so C. doesnt make sense.
https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5500/sw/san_switching/6x/b_5500_SAN_Switching_Config_6x/configuring_fibre_channel_domain_parameters.pdf
No.# From my understanding an MST instance is nothing more than a route from point A to B, but point A to B could have multiple MST instances active. So A. would make no sense.
As Cisco describes diameter command: to specify the network diameter (that is, the maximum number of hops between any two end stations in the network). I would go for D. As that would describe more closely the term "end stations" rather than two "virtual" MST instances.
https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/configuration/guide/cli_rel_4_0_1a/CLIConfigurationGuide/MST.html
No.# In order to extend the network to use more than 16 million segments you need two things:
FabricPath feature and configure segment-id for your VLANs, The question itself is poorly described.
Either FabricPath is already enabled and i would go for C. because enabling vn-segment-vlan-based feature and configure segment IDs for your VLANs is necessary or you can say D. enable FabricPath feature and configure the VLAN IDs (as part of your segment ID configuration).
I would prefer C as this is closer to the answer.
https://communities.cisco.com/docs/DOC-55222
No.# This should be A. If the configured RTT is smaller than the measured RTT, the link is not able to fully utilize.
https://www.cisco.com/c/en/us/td/docs/switches/datacenter/mds9000/sw/5_0/configuration/guides/ipsvc/nxos/ipsvc/cfcip.pdf
No.# This should be C. As the fabricpath switch-id / domain-id and the second switch-id should be the same for both peer switches in a vPC+ environment.
No.# This should be A. FCID's are dynamically assigned by the fabric to the WWPN's. You will have to manually configure the FCID's towards a vsan based on the WWN.
https://overlaid.net/2014/08/16/fibre-channel-fc-basics-for-ccie-dc/
https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5500/sw/san_switching/6x/b_5500_SAN_Switching_Config_6x/b_5500_SAN_Switching_Config_602N12_chapter_011.pdf
No.# This should be A. As the peer-gateway function for vPC configuration enables the peer switch to be an active gateway to lower the usage of the vPC peer link. So D. doesn't make sense because this scenario describes the actual fallback scenario when the peer link flaps.