350-601 Sample Questions & Answers

REST API and HTTPS are the technologies most likely in use. The GET request indicates a REST API call being made to retrieve data, and TCP port 443 confirms HTTPS (HTTP Secure) is being used for encrypted communication. XML format is a common data format returned by REST APIs when querying Cisco APIC. JSON would be an alternative format, HTTP would use port 80 (not 443), and SOAP API typically uses different request methods and XML structures.

HTTPS is confirmed by the use of TCP port 443, which is the standard secure HTTP port that provides encrypted communication between the client and the APIC device. This ensures secure transmission of the XML data being retrieved.

Link-Layer Discovery Protocol (LLDP) is used for discovering private IP addresses during the Cisco APIC cluster discovery process. LLDP enables APIC controllers to discover each other and exchange private IP address information for cluster formation. This allows the APICs to establish secure tunnels and coordinate cluster operations without relying on public IP addresses or external discovery mechanisms.

REST APIs commonly produce output in XML format, which is a structured markup language that uses tags to define data elements and provides hierarchical data representation. XML is widely supported by web services and APIs, making it a standard format for data exchange. CSV and HTML are not standard REST API output formats, and binary formats are typically not used for REST API responses.

REST APIs frequently produce output in JSON (JavaScript Object Notation) format, which is a lightweight, human-readable data interchange format. JSON has become the preferred format for many REST APIs due to its simplicity, native support in web browsers and programming languages, and smaller payload size compared to XML. Binary and CSV formats are not standard REST API output formats.

Community is a cloud computing deployment model that shares infrastructure with multiple organizations that have common needs, concerns, or compliance requirements. Unlike public clouds that serve any customer, community clouds are restricted to specific groups with shared interests such as government agencies, healthcare organizations, or financial institutions. Hybrid clouds combine multiple deployment models, and public/private clouds do not specifically address shared infrastructure among organizations with common needs.

Communication between members of the same endpoint group (EPG) is not governed by contracts in a Cisco ACI fabric. By default, members of an EPG can communicate freely with each other without requiring contracts, as they are considered to be in the same security domain. Contracts are only required for inter-EPG communication, communication between different bridge domains, and external network access. This intra-EPG communication uses the bridge domain forwarding behavior.

Based on the network topology, S1 will most likely be discovered next because ACI fabric discovery follows a systematic pattern where spine switches are discovered through their direct connections. After S2 spine switch is discovered by APIC1, the fabric discovery process continues by finding adjacent spine switches that connect to the same leaf switches. S1 is the logical next spine switch in the discovery sequence as it shares connectivity with the same fabric infrastructure.

Most likely, you will deploy a Cisco Global Site Selector (GSS) device if you want to implement Global Server Load Balancing (GSLB). Cisco GSS provides intelligent DNS-based load balancing across geographically distributed data centers, optimizing user traffic routing based on server availability, proximity, and network conditions. The other options (ASA firewall, CSM module, and CSS appliance) provide different types of load balancing or security functions but are not specifically designed for global server load balancing.

Cisco FabricPath edge ports are classic Ethernet ports that connect end devices to the FabricPath fabric. These ports function as standard Layer 2 Ethernet interfaces and maintain compatibility with existing Ethernet devices and protocols. FabricPath uses Layer 3 routing combined with Layer 2 switching internally within the fabric, but edge ports present a traditional Ethernet interface to connected devices. Core ports connect FabricPath switches together, while edge ports provide device connectivity.

Tasks are best described as the atomic units of work in Cisco UCS Director Orchestrator. Tasks represent the smallest executable units that perform specific operations within workflows, such as provisioning a VM, creating a VLAN, or configuring storage. These tasks can be combined into workflows to automate complex multi-step processes. Templates, policies, and workflows are higher-level constructs that utilize tasks as their basic building blocks.

OTV STP isolation feature ensures that Bridge Protocol Data Units (BPDUs) are not forwarded across the overlay network. This feature is enabled by default and prevents spanning tree topology changes in one data center from affecting the spanning tree domain in another data center. By suppressing BPDUs, OTV maintains independent STP domains on each site while allowing data traffic to flow across the overlay. ARP suppression, MAC learning suppression, and broadcast suppression serve different isolation purposes.