Free 350-601 Practice Test

:

:

A nondisruptive update, or In-Service Software Upgrade (ISSU), on a Cisco MDS switch involves loading a new software image onto the standby supervisor module while the active supervisor continues to forward traffic. A key part of this process is the system managing its resources to accommodate the new image. The system must allocate memory (RAM) and check for sufficient bootflash space to load and run the new software on the standby supervisor before initiating a switchover. This action of managing and assigning resources for the new image is an intrinsic part of the update process itself.

A. The upgrade being aborted due to pending CFS commits is the result of a failed pre-upgrade check, not an impact of the update process itself.
B. An ISSU process is blocked and will not continue if a critical fabric operation like a zone merge is in progress; it does not run uninterrupted.
C. The system BIOS (or bootloader) is typically updated automatically as part of the install all process if required, not as a separate manual step after completion.

1. Cisco, Cisco MDS 9000 Series NX-OS Software Upgrade and Downgrade Guide, Release 8.x, Chapter: "About In-Service Software Upgrades", Section: "ISSU Process". The guide describes the process: "The new software is loaded on the standby supervisor... The standby supervisor is brought up with the new software." This loading process inherently requires system resource allocation.

2. Cisco, Cisco MDS 9000 Family NX-OS Fundamentals Configuration Guide, Chapter: "In-Service Software Upgrades". This guide details the ISSU process, including the step of loading the new image onto the standby supervisor, which implies the allocation of system resources like memory and storage space.

In Cisco ACI, a Virtual Port-Channel (vPC) allows links that are physically connected to two different leaf switches to appear as a single Port-Channel to a third device. Each logical vPC requires a set of policies that define its behavior (e.g., LACP, CDP). These policies are bundled into a vPC Interface Policy Group. Since the scenario requires creating two distinct vPCs connecting to two different servers, two separate vPC Interface Policy Groups must be created. This allows for independent policy management for each server's connection, which is a fundamental ACI design principle for scalability and modularity.

B. An access port interface policy group is used for individual, non-Port-Channel interfaces, which is incorrect for a vPC configuration.
C. A "PortChannel interface policy group" is used for a Port-Channel on a single leaf, not a vPC that spans two leaf switches.
D. Using one vPC interface policy group for two different vPCs is not best practice and limits policy flexibility, as both vPCs would be forced to share the exact same policies.

1. Cisco, Cisco APIC Layer 2 Networking Configuration Guide, Release 4.2(x), "vPC Interfaces", Section: "About vPC Interface Policy Groups". It states, "The vPC interface policy group is a container for all the policies that are related to a vPC interface."

2. Cisco, ACI Design Guide, "Access Policies", Section: "Interface Policies". The guide details the ACI object model where distinct logical constructs like separate vPCs are configured with their own policy groups for granular control.

:

The correct answer is C. standby supervisor. From the exhibit, the command output clearly shows: Module 6 SUP Yes disruptive Module Upgradable and later confirms: Module 6 EPLD upgrade is successful and 6 SUP Success. This indicates that the EPLD upgrade was performed on a Supervisor (SUP) module, specifically module 6. In Cisco MDS 9700 architecture, supervisor modules operate in a redundant pair (active and standby). When EPLD upgrades are performed, Cisco best practice and system behavior typically upgrade the standby supervisor first, because it allows the system to maintain control-plane continuity and minimizes disruption. The output does not mention PSU, fan, or fabric modules, eliminating options A, B, and D. The explicit reference to SUP confirms that the upgrade applies to a supervisor module. Thus, based on the module type shown in the output and standard Cisco upgrade behavior, the EPLD upgrade is applied to the standby supervisor, making C the correct answer.

:

Ansible is an automation tool that perfectly aligns with the specified requirements. It is agentless, which contributes to its ease of configuration and management as no client software needs to be installed on the network devices. Ansible is built on Python, allowing for extensive customization with Python modules. Its playbooks, which define the configuration tasks, are written in YAML (YAML Ain't Markup Language), a human-readable data serialization language.

A. Puppet uses a proprietary Puppet DSL (Domain Specific Language) and is based on Ruby, not primarily Python and YAML for its core configuration.
B. While SaltStack is Python-based and uses YAML, Ansible's agentless model is widely considered simpler to set up and manage for many use cases.
C. Chef uses recipes written in Ruby to manage configurations, not Python and YAML as its primary languages.

1. Cisco Press, "Network Programmability and Automation Fundamentals" by J. Edelman, S. Lowe, M. Oswalt. Chapter 8, "Automation Tools," describes Ansible as an agentless tool that uses YAML playbooks.

2. Cisco DevNet Learning Labs, "Introduction to Ansible for Network Automation." The lab introduction states, "Ansible is a simple, yet powerful, IT automation engine... Playbooks are the YAML files that describe the tasks to be done."

3. Ansible, Official Documentation, "Introduction to Ansible." The documentation highlights its agentless architecture, use of YAML, and extensibility with Python.

The "network administrator" role in Cisco UCS Manager is responsible for configuring network-related components. This includes creating and managing vNICs (virtual network interface cards) and vHBAs (virtual host bus adapters), which define server connectivity to LAN and SAN fabrics. Crucially, this role also has privileges to configure the physical ports on the Fabric Interconnects, including setting them as server ports. While a server administrator manages service profiles that contain vNICs/vHBAs, the network administrator role is required for the comprehensive network and fabric configuration mentioned, especially for "server port types."

B. operations: This role is primarily for monitoring and performing basic operational tasks like power cycling servers; it lacks configuration privileges for network or server policies.
C. server-compute: This role (typically Server Administrator) focuses on server-specific objects like service profiles and boot policies, but not the underlying fabric port configuration.
D. AAA administrator: This role is restricted to managing authentication, authorization, and accounting, which includes users, roles, and organizations, not hardware or policy configuration.

Cisco, Cisco UCS Manager Administration Guide, Release 4.1, "User Management" chapter, section "User Roles," Table "Pre-Login and User Roles and Privileges." This table details that the Network Administrator role includes privileges for ext-lan-config and ext-san-config, which cover vNICs, vHBAs, and port configurations.

Cisco, Cisco UCS Manager Administration Management Guide, Release 4.0, "Managing Users, Roles, and Organizations" chapter, section "Default User Roles." It states, "Network Administrator: Manages network related configuration, including VLANs, VSANs, vNICs, vHBAs, and quality of service."

The correct answer is D. through dual fabric interconnects. Cisco UCS X-Series achieves management high availability by using a pair of Fabric Interconnects (FIs), which provide redundant connectivity and management-plane resiliency for the chassis and its components. In UCS architecture, the fabric interconnects are the central control and management point for the compute domain, so deploying them as a redundant pair ensures that management access and infrastructure communication continue if one FI fails.
Option A is incorrect because UCS Director is an orchestration platform, not the native HA mechanism for UCS-X management components. Option B is incorrect because UCS Manager is associated with classic UCS domains and is not described as separate redundant manager instances in this context. Option C is also incorrect because Cisco Intersight is a SaaS or appliance-based management platform, but UCS-X high availability at the domain level is not achieved by running multiple Intersight instances. The actual device-level resiliency for management in UCS-X comes from the redundant fabric interconnect design, which protects management and connectivity paths for the chassis, I/O, and compute resources. Therefore, dual fabric interconnects are the correct answer.