Free Cisco 300-170 Exam Practice Questions & Explanations
Prepared & Reviewed by the ValidExamDumps Editorial Team
At ValidExamDumps, we consistently monitor updates to the Cisco 300-170 exam questions by Cisco. Whenever our team identifies changes in the exam questions, objectives, focus areas or requirements, We immediately update our exam questions for both PDF and online practice exams. This commitment ensures our customers always have access to the most current and accurate questions. By preparing with these up to date and 100% exam domain coverage questions, our customers can successfully pass the Cisco Implementing Cisco Data Center Virtualization and Automation exam on their first attempt without needing additional materials or study guides.
Other certification materials providers often include outdated or removed questions by Cisco in their 300-170 exam. These outdated questions lead to customers failing their Cisco Implementing Cisco Data Center Virtualization and Automation exam. In contrast, we ensure our questions bank includes only precise and up-to-date questions. Our main priority is your success in the Cisco 300-170 exam, not profiting from selling obsolete exam questions in PDF or Online Practice Test.
An engineer wants to standardize per-tenant network settings on a Nexus fabric by placing VLAN, SVI, and VRF commands inside a configuration profile, and then instantiating that profile with different parameter values on each leaf switch as endpoints appear.
Statement: A Cisco NX-OS configuration profile can include variables that are substituted at instantiation time, allowing one profile definition to be reused with different parameters across multiple switches.
True. NX-OS configuration profiles are named containers of configuration commands that support parameters/variables (for example $vlanId, $vrfName). The same profile definition can be distributed to many switches and applied with different parameter values, which is the basis of auto-configuration in a fabric. The commands take effect only when the profile is applied/instantiated, so the profile itself can be pre-staged without impacting the running configuration.
A network team manages hundreds of Nexus switches and wants to move from CLI screen-scraping to a programmatic method that returns structured data. They require an API that runs over HTTP/HTTPS, supports both CLI-based and JSON/XML-encoded requests, and can be tested from a browser-based sandbox on the switch itself.
Which interface should they use?
A is correct. NX-API, enabled with feature nxapi, exposes NX-OS CLI and object-model operations over HTTP/HTTPS and returns JSON or XML structured output. The NX-API Developer Sandbox is a web page hosted on the switch that converts CLI commands into the corresponding JSON/XML payloads for testing.
B is wrong: SNMP is not a configuration API for arbitrary CLI and returns OID data, not structured JSON. C is wrong: Expect over SSH is still screen-scraping unstructured text. D is wrong: Telnet is insecure and is not the transport used by NX-API.
An engineer is racking 40 new Nexus 9000 switches and wants them to configure themselves at first boot with no console access. The switches boot with no startup configuration and reach a DHCP server. Which two elements must the DHCP offer supply so that POAP can proceed to download and execute the configuration script? (Choose two.)
A and B are correct. During POAP, a switch with no startup configuration sends DHCP discovers on its management and front-panel interfaces. The DHCP offer must include an IP address/mask (and typically a gateway) plus the script server address (siaddr/option 150 or 66) and the bootfile name (option 67) that identifies the POAP script. The switch then downloads and executes the script, which handles image and configuration download.
C is wrong: the MD5 is defined inside the POAP script for image verification, not in DHCP. D is wrong: AAA is not part of the POAP bootstrap. E is wrong: a startup-config present in bootflash actually prevents POAP from running.
A team is deploying the Cisco Nexus 1000V in a VMware vSphere environment. The virtualization administrator needs to place a new VM into a port group that enforces a QoS policy and an ACL applied by the network team, and the configuration must persist if the VM is migrated with vMotion to another host.
Which action correctly accomplishes this?
A is correct. On the Nexus 1000V, vEthernet port profiles define policy for VM virtual interfaces and are published to vCenter as distributed port groups. Because the interface state and policy are tracked per VM, the configuration follows the VM during vMotion.
B is wrong: ethernet-type port profiles are for the physical uplink NICs (VMNICs) of the ESXi hosts, not VM vNICs. C is wrong: the VEM is not independently configurable; all configuration is done on the VSM and pushed to VEMs. D is wrong: policy on an upstream physical switch or standard vSwitch does not follow the VM after migration.
A data center engineer must give the storage team administrative control over a subset of interfaces and VSAN configuration on a Cisco Nexus 7000, while the network team retains control of the Ethernet LAN interfaces. Each team must have its own configuration file, its own set of VLANs/VSANs, and independent process instances for protocols so that a crash in one team's environment does not affect the other.
Which technology satisfies this requirement?
A is correct. A VDC provides true logical device separation on a Nexus 7000: each VDC has its own configuration file, its own VLAN/VSAN and interface allocation, its own administrator, and separate protocol process instances, so a process failure in one VDC does not impact another.
B is wrong because a VRF separates only the Layer 3 routing/forwarding table within a single device context, not management, interfaces, or process instances. C is wrong because vPC is a multichassis link aggregation feature, not an administrative separation feature. D is wrong because RBAC restricts commands a user can execute, but all users still share a single configuration file and single set of protocol processes.