350-601 Exam Dumps - Cisco CCNP Data Center Questions and Answers

The correct answer is C. Ansible because it is the one option that matches all three stated requirements at the same time. Official Ansible documentation describes Ansible as an agentless automation tool installed on a control node, and states that it manages remote systems over SSH without requiring additional daemons or software on the managed nodes. Ansible documentation also states that its playbooks are written in YAML, which is intended to be easier for humans to read and write, making it a strong fit for teams with limited scripting experience.

The other options do not fit as cleanly. Chef can use SSH in agentless mode, but Chef’s core model is based on Chef Infra Client, which is an agent, and its automation logic is built around recipes rather than simple declarative YAML playbooks. Puppet supports declarative configuration and can use SSH through Bolt, but Puppet commonly relies on installed agents in standard deployments. PowerShell is primarily a scripting language, not the best match for the requirement for an easy-to-read declarative orchestration tool. Therefore, Ansible is the best and verified choice.

Creating a new Cisco ACI managed object requires an HTTP POST operation. The JSON payload must place the properties of the physical-domain object inside an attributes structure. The exhibit shows the physDomP object with attributes such as its name and distinguished name, followed by a child relationship that associates the VLAN namespace. Therefore, POST and attributes are the two required elements. GET retrieves existing information and cannot create the physical domain. PATCH is not the standard Cisco APIC method used for creating this managed object. The word variables is not a valid structural element in the illustrated APIC JSON managed-object payload. APIC processes the POST request, creates the physical domain, and establishes the child relationship to the specified dynamic VLAN pool using the target distinguished name.

The chassis/FEX discovery policy specifies the minimum number of links Cisco UCS Manager expects between each I/O module and its corresponding fabric interconnect. Configuring the policy for four links enables UCS Manager to discover and activate all four connected interfaces. Those links operate collectively, providing additional bandwidth and allowing connectivity to continue if an individual link fails. An LACP policy is not used for the internal chassis-to-fabric-interconnect connections in this design. Firmware Auto Sync controls firmware synchronization when a server is replaced and has no effect on link usage or resiliency. Link Group Preference is also unrelated to chassis discovery and activation of the four physical links. Cisco documentation confirms that a chassis connected with four links requires a chassis/FEX discovery policy that supports four links; otherwise, all available connections might not be discovered and activated as required. Cisco UCS equipment policies

The two RADIUS servers are reached through different Layer 2 and routing contexts. RAD1 is reachable through the management interface, while RAD2 is reachable through VLAN 22. Configuring the correct source interface for each RADIUS server group ensures that authentication requests originate from an IP address belonging to the subnet that the corresponding server permits. Separate AAA login method lists must then associate console authentication with RAD1 and remote SSH authentication with RAD2. Command authorization controls whether authenticated users may execute particular commands; it does not determine which server authenticates console or SSH access. Changing the dead timer only alters how long an unresponsive server is avoided and does not meet either authentication-selection requirement. Therefore, both the per-group source-interface configuration and the service-specific AAA authentication method lists are required.