Examkin

Automation and Programmability

200 questions

All types200Multiple choice102Multiple select47Matching45Ordering6
Question 61Question →

A network automation engineer is building Python scripts to interact with Cisco DNA Center and RESTCONF API interfaces. Match each HTTP request configuration on the left to its corresponding RESTful API operational behavior on the right.

Click a left item, then click its matching right item

Items

HTTP PUT to a specific resource URI with a Content-Type payload
HTTP PATCH to a specific resource URI with a Content-Type payload
HTTP POST to a collection URI with an Accept header specified
HTTP GET to a specific resource URI with an If-None-Match header

Matches

Show answer & explanation

Answer

HTTP PUT maps to complete resource replacement (Idempotent); HTTP PATCH maps to partial modification of specified attributes; HTTP POST with an Accept header maps to creating a subordinate resource while specifying expected response encoding; HTTP GET with an If-None-Match header maps to conditional resource retrieval based on ETag validation.
Matching each HTTP request operation to its behavior requires analyzing HTTP verb semantics, idempotency, and header roles in REST APIs. PUT performs complete resource replacement (idempotent), PATCH performs partial attribute modification, POST creates new subordinate resources with Accept defining expected response formatting, and GET with If-None-Match enables conditional retrieval using ETags.

Step-by-Step Solution

1
Analyze HTTP PUT verb characteristics and CRUD mapping
PUT represents a full update/replace operation. It is idempotent and requires transmitting the complete payload structure to overwrite the existing target resource.
Differentiating PUT from PATCH requires recognizing full resource overwrite versus selective attribute modification.
2
Analyze HTTP PATCH verb characteristics and CRUD mapping
PATCH applies delta or partial updates, modifying only the fields included in the request body while leaving all unmentioned parameters intact.
PATCH minimizes payload bandwidth when altering isolated parameters within an existing configuration.
3
Analyze HTTP POST verb behavior and header roles
POST creates new child entities under a target collection endpoint. The Accept header indicates the media type (e.g., application/json) requested for the server's response.
Content-Type describes the request payload format sent to the server, while Accept specifies the desired response format returned by the server.
4
Analyze HTTP GET conditional request headers
GET retrieves resource state without side effects. Including If-None-Match allows the client to perform conditional validation against the server's ETag, saving bandwidth if un-modified.
Conditional headers optimize RESTful network automation workflows by preventing unnecessary data transmission.

Key Concept

Characteristics of REST-Based APIs (CRUD, HTTP Verbs, Data Formats)
Estimated Time:2m 0s
Question 62Question →

A network operations department is preparing documentation to explain how device management and path computation differ between distributed legacy deployments and modern software-defined networking (SDN) controller environments. Which two statements correctly describe key operational differences of controller-based networking compared to traditional networking? (Select two.)

Select all that apply

Show answer & explanation

Answer: Control plane functions are centralized on a software controller rather than running independently on each network device.; Southbound APIs facilitate communication between the centralized controller and managed physical or virtual network devices.

Answer

In controller-based networking, control plane functions are shifted from individual devices to a centralized software controller, and Southbound APIs are used by the controller to relay configurations and forwarding state to managed network hardware.
The correct statements correctly highlight that controller-based networking shifts control plane intelligence away from individual distributed devices onto a centralized controller, and uses Southbound APIs (such as OpenFlow, NETCONF, or RESTCONF) to communicate operational policies and device state between the controller and data plane hardware.

Step-by-Step Solution

1
Analyze control plane distribution differences
In traditional networking, every device runs its own control plane protocols (distributed control plane). In SDN/controller-based networking, control plane logic is centralized in the controller.
Centralization removes distributed protocol calculations from individual network nodes.
2
Identify the role of Southbound APIs
Southbound APIs (e.g., NETCONF, RESTCONF, OpenFlow) link the centralized controller to data plane devices (switches and routers).
The controller uses Southbound protocols to instruct network hardware how to handle and forward traffic.
3
Differentiate Northbound APIs and distributed routing protocols
Northbound APIs interact upwards with applications and automation scripts, while Layer 2/3 forwarding stays in the data plane.
Northbound APIs do not handle switch-to-switch frame forwarding or peer routing table exchanges.

Key Concept

Centralized Control Plane and API Architecture in Controller-Based Networks
Question 63Question →

An enterprise network requires all Cisco Catalyst access switches within a site hierarchy to run a standardized, vendor-verified Cisco IOS XE release. An administrator notices that several switches are running inconsistent software images. Which Cisco DNA Center function should be used to designate the baseline software release for a device family and evaluate image compliance across the inventory?

Show answer & explanation

Answer: Tagging the target software image as Golden within the Software Image Management (SWIM) repository

Answer

Tagging the target software image as Golden within the Software Image Management (SWIM) repository.
In Cisco DNA Center, Software Image Management (SWIM) allows network administrators to import software images, set specific image versions as 'Golden' baselines for device families or locations, perform readiness checks, and automate updates for non-compliant devices.

Step-by-Step Solution

1
Identify the Cisco DNA Center feature responsible for managing device software images.
Software Image Management (SWIM) is the component dedicated to image repository maintenance, compliance checks, and automated updates.
SWIM centralizes software image files across all supported hardware platforms.
2
Determine how Cisco DNA Center establishes a software baseline.
Designating an image as 'Golden' sets it as the approved compliance version for a device model or site.
Once an image is marked Golden, Cisco DNA Center compares all managed devices against this baseline to flag non-compliant software.

Key Concept

Cisco DNA Center Software Image Management (SWIM) and Golden Image Compliance
Estimated Time:1m 15s
Question 64Question →

A network administrator needs to select a configuration management tool to automate Cisco router configurations. The organization mandates an agentless architecture that executes playbooks over standard SSH or NETCONF connections without installing software on target devices. Which tool satisfies this requirement?

Show answer & explanation

Answer: Ansible

Answer

Ansible meets the requirement because it operates using an agentless architecture and executes playbooks over SSH or NETCONF.
Ansible uses an agentless architecture that does not require host agent software. It pushes configurations to network devices over standard management protocols such as SSH or NETCONF using structured YAML playbooks.

Step-by-Step Solution

1
Identify key requirements from the scenario.
The requirement calls for an agentless configuration tool that uses SSH/NETCONF transport and playbooks.
Network appliances often cannot support third-party agent daemons natively.
2
Evaluate candidate configuration management tools.
Ansible is agentless and uses YAML playbooks over SSH/NETCONF, whereas Puppet and Chef primarily rely on client agents.
Comparing tool architectures identifies Ansible as the match for agentless requirements.

Key Concept

Agentless vs Agent-Based Configuration Management Architecture
Estimated Time:45s
Question 65Question →

An automated provisioning script executes an HTTP request targeting a Cisco RESTCONF resource URI representing an interface configuration. The request payload includes only an updated description string. After execution, the interface description is updated, but all previously configured IP addressing and administrative state settings under that interface resource are completely cleared and reset to defaults. Which HTTP request method did the script use, and why did this data loss occur?

Show answer & explanation

Answer: HTTP PUT was used because it performs a complete replacement of the target resource, overwriting unreferenced fields with null or default values.

Answer

HTTP PUT was used because it performs a complete replacement of the target resource, overwriting unreferenced fields with null or default values.
In REST-based APIs (including Cisco RESTCONF and Cisco DNA Center APIs), HTTP PUT maps to replacing an existing resource in its entirety. When an API client sends an HTTP PUT request, the server expects a complete representation of the resource. If optional or unreferenced attributes (such as IP addressing or administrative status) are omitted from the PUT payload, the server replaces the current resource state with the new payload, causing omitted fields to be deleted or reset to default values. To selectively update only specific parameters while leaving unmentioned fields untouched, HTTP PATCH must be used.

Step-by-Step Solution

1
Analyze the observed behavior during API execution
The target interface resource updated the specified attribute (description) but wiped out all unspecified attributes (IP address and administrative state).
This indicates full resource replacement rather than a selective partial modification.
2
Map HTTP verbs to their operational behaviors under RESTful APIs
HTTP PUT replaces the entire target resource data structure at the specified URI, whereas HTTP PATCH performs a partial update modifying only the fields present in the payload.
Omitting existing attributes in an HTTP PUT request payload causes the RESTful server to overwrite those missing attributes with default or null values.
3
Conclude the correct verb and root cause
The script erroneously issued an HTTP PUT request instead of an HTTP PATCH request.
To preserve unreferenced attributes while modifying only the description field, HTTP PATCH should have been used.

Key Concept

Operational differences between HTTP PUT (full resource replacement) and HTTP PATCH (partial resource modification) in REST-based network automation APIs.
Estimated Time:1m 30s
Question 66Question →

In a Cisco Software-Defined Access (SD-Access) solution, an enterprise deploys a Layer 3 routed underlay network using OSPF to establish IP reachability between Routing Locator (RLOC) interfaces. During testing, host data packets transmitted between different fabric edge switches fail whenever the payload size approaches 1500 bytes. Analysis shows that packet payload expansion is occurring because host frames are encapsulated with outer IP and UDP headers before entering the physical transport. Which protocol and architectural layer are responsible for performing this data plane encapsulation?

Show answer & explanation

Answer: Virtual Extensible LAN (VXLAN) operating at the overlay layer

Answer

Virtual Extensible LAN (VXLAN) operating at the overlay layer
The correct option correctly identifies VXLAN operating at the overlay layer. In Cisco SD-Access architectures, VXLAN is employed as the data plane encapsulation mechanism. It encapsulates original Ethernet frames into UDP-based packets (using UDP port 4789) to transport Layer 2 and Layer 3 virtual networks across an IP-only underlay. This encapsulation adds header overhead (typically 50 bytes), requiring the underlay physical network to support an increased MTU (jumbo frames).

Step-by-Step Solution

1
Differentiate between the underlay and overlay architectural components in Cisco SD-Access.
The underlay consists of physical routers/switches and an IGP (such as OSPF or IS-IS) providing IP connectivity between switch loopback interfaces (RLOCs). The overlay represents the virtual network built on top of the underlay.
Understanding the separation of underlay and overlay is necessary to determine which layer manages data encapsulation.
2
Identify the specific roles of LISP and VXLAN in the SD-Access fabric.
LISP operates as the fabric control plane mapping database (mapping EID to RLOC). VXLAN operates as the fabric data plane protocol.
LISP manages location/identity queries while VXLAN encapsulates actual host data traffic into UDP frames.
3
Analyze the cause of payload expansion and MTU issues.
VXLAN wraps the original Layer 2 Ethernet frame inside outer IP, UDP, and VXLAN headers. This adds approximately 50 bytes of overhead, causing frames near 1500 bytes to exceed standard MTU unless jumbo frames are enabled in the underlay.
VXLAN encapsulation at the overlay layer directly causes the payload expansion described in the scenario.

Key Concept

Software-Defined Architecture: Overlay vs Underlay Roles and VXLAN Data Plane Encapsulation
Estimated Time:2m 0s
Question 67Question →

A network engineer is configuring an automated Python script to manage network interfaces on a Cisco controller via a RESTful API. The script interacts with the URI endpoint `/api/v1/interfaces/GigabitEthernet0/1`. Which two statements accurately describe the behavior of HTTP verbs and headers when performing CRUD operations on this REST API endpoint?

Select all that apply

Show answer & explanation

Answer: An HTTP PUT request requires a complete payload representing the resource, as any omitted fields may be cleared or restored to default values.; The Content-Type request header identifies the data format of the sent body, while the Accept header specifies the data format expected in the response.

Answer

The two correct statements state that an HTTP PUT request requires a complete payload representing the resource because omitted fields may be cleared or reset, and that the Content-Type request header identifies the data format of the sent body while the Accept header specifies the format expected in the response.
The correct options accurately identify REST API characteristics: HTTP PUT performs a complete resource replacement, meaning any unmentioned fields in the payload will be reset or cleared on the target server. Additionally, the Content-Type request header informs the server of the payload format being transmitted, while the Accept header declares the media format requested in the server response.

Step-by-Step Solution

1
Analyze HTTP PUT verb behavior in REST APIs.
PUT is used for full resource replacements. Omitting resource attributes during a PUT call can cause the API server to delete or overwrite those attributes with default values.
Understanding verb semantics ensures configuration data is not accidentally wiped during updates.
2
Analyze HTTP request header roles.
Content-Type specifies the format of data in the outgoing HTTP payload (such as application/json), whereas Accept tells the server which format the client prefers for the incoming response.
Proper header usage guarantees proper payload serialization and content negotiation between API client and server.
3
Evaluate distractor statements regarding HTTP POST and PATCH.
HTTP POST creates resources (Create in CRUD) and is non-idempotent. HTTP PATCH applies partial updates to existing resources. HTTP GET handles Read operations.
Identifying incorrect CRUD mappings and verb characteristics eliminates wrong options.

Key Concept

Characteristics of REST HTTP Verbs, CRUD Operations, and HTTP Header Negotiation
Estimated Time:2m 0s
Question 68Question →

Which automation tool uses an agentless architecture to push network configurations to managed devices over SSH?

Show answer & explanation

Answer: Ansible

Answer

Ansible is the configuration management tool that operates using an agentless model and relies on SSH to push configurations to network devices.
The option selecting Ansible is correct because Ansible operates in an agentless fashion using SSH (or NETCONF/RESTCONF) to push YAML-defined configurations (Playbooks) directly from a control workstation to target network switches and routers.

Step-by-Step Solution

1
Identify the key operational requirements in the question: agentless architecture and SSH push mechanism.
The target tool must not require agent software on network routers/switches and must use standard SSH transport.
Cisco network devices often run proprietary operating systems (such as IOS XE) where installing third-party agent software is difficult or unsupported.
2
Evaluate Ansible against these requirements.
Ansible uses Playbooks written in YAML, runs centrally on a control node, and connects to target devices over SSH without installing any agent on the target.
Ansible's native design is inherently agentless and push-based.
3
Evaluate Puppet and Chef against these requirements.
Both Puppet and Chef rely primarily on client/agent software installed on managed hosts to pull configurations periodically.
Puppet uses Manifests/Puppet Agent and Chef uses Recipes/Chef Client.

Key Concept

Agentless Configuration Management with Ansible
Estimated Time:45s
Question 69Question →

Match each architectural concept or communication interface to its corresponding functional role in traditional vs. controller-based networking environments.

Click a left item, then click its matching right item

Items

Northbound API Communication
Centralized Control Plane
Distributed Control Plane
Southbound API Communication

Matches

Show answer & explanation

Answer

Northbound APIs connect the controller with high-level applications; Centralized Control Planes aggregate network intelligence onto a central software controller; Distributed Control Planes require each network device to make independent control decisions locally; Southbound APIs allow the controller to communicate down to physical network infrastructure elements.
In controller-based networking, the control plane is decoupled from physical hardware and centralized on an SDN controller. Northbound APIs enable communication between software applications and the controller, while Southbound APIs allow the controller to configure and program underlying network elements. Traditional networks rely on a distributed control plane where each node executes control protocol algorithms locally.

Step-by-Step Solution

1
Analyze Northbound API functions
Identify that Northbound APIs face 'upward' toward applications and management platforms (REST/JSON).
Northbound APIs connect business applications to the centralized controller.
2
Analyze Centralized Control Plane functions
Recognize that control plane logic is removed from individual devices and relocated to a central software-defined controller.
The controller uses a global network view to compute paths centrally.
3
Analyze Distributed Control Plane functions
Recall traditional networking mechanics where every router and switch independently exchanges control messages to build forwarding databases.
In traditional deployments, control decisions are distributed per device.
4
Analyze Southbound API functions
Identify that Southbound APIs face 'downward' toward infrastructure nodes (NETCONF, RESTCONF, OpenFlow).
Southbound APIs push instructions from the SDN controller down to network devices.

Key Concept

Structural and functional distinctions between traditional distributed networks and controller-based SDN architectures.
Question 70Question →

An enterprise network engineer is designing a software-defined fabric infrastructure using Cisco SD-Access concepts. The design requires establishing IP reachability between physical switches, encapsulating tenant traffic across the fabric, and maintaining a dynamic endpoint location database. Which two statements accurately describe the operational responsibilities of the underlay and overlay network components in this architecture?

Select all that apply

Show answer & explanation

Answer: The underlay network relies on interior gateway protocols such as IS-IS or OSPF to provide IP connectivity between fabric node loopback addresses (RLOCs).; The overlay data plane uses VXLAN encapsulation to transport Layer 2 Ethernet frames and Layer 3 IP packets over the Layer 3 underlay infrastructure.

Answer

The underlay network relies on interior gateway protocols such as IS-IS or OSPF to provide IP connectivity between fabric node loopback addresses, and the overlay data plane uses VXLAN encapsulation to transport Layer 2 Ethernet frames and Layer 3 IP packets over the Layer 3 underlay infrastructure.
In software-defined campus fabric architectures like Cisco SD-Access, the underlay consists of physical switches and routers configured with a Layer 3 routing protocol (such as IS-IS or OSPF) to ensure complete IP reachability between fabric nodes (Routing Locators / RLOCs). The overlay network abstracts virtual networks above this underlay; specifically, the overlay data plane utilizes Virtual Extensible LAN (VXLAN) encapsulation to encapsulate Layer 2 Ethernet frames and Layer 3 IP packets inside UDP packets, forwarding them across the Layer 3 underlay.

Step-by-Step Solution

1
Analyze the underlay network responsibilities.
Identified that the underlay provides physical Layer 3 IP reachability between fabric nodes (RLOCs) using standard routing protocols like IS-IS or OSPF.
Overlay encapsulation (VXLAN) requires underlying IP connectivity between tunnel endpoints.
2
Analyze the overlay network data plane responsibilities.
Identified that VXLAN encapsulates original host frames with a UDP outer header to carry Layer 2/3 traffic across the routed underlay.
Overlay encapsulation decouples host connectivity and virtual networks from the underlying physical topology.
3
Evaluate and eliminate incorrect distractor options.
Disqualified options that misattribute physical port attributes to the overlay, confuse LISP control plane functionality with underlay routing, or misidentify trunking mechanics.
Clear functional separation exists: underlay manages physical reachability, overlay manages virtual encapsulation and endpoint mapping.

Key Concept

Software-Defined Architecture Component Separation (Underlay vs. Overlay)
Estimated Time:2m 0s
Question 71Question →

A network engineer is evaluating the architectural shift from legacy autonomous switches to a centralized Software-Defined Networking (SDN) model for a campus deployment. Which statement accurately describes how control plane operations and traffic handling differ in a controller-based network compared to a traditional network architecture?

Show answer & explanation

Answer: Control plane intelligence is centralized within the software controller to program policies and forwarding instructions, while individual network devices perform high-speed data plane packet forwarding.

Answer

Control plane intelligence is centralized within the software controller to program policies and forwarding instructions, while individual network devices perform high-speed data plane packet forwarding.
In controller-based networking (SDN), control plane decision-making is decoupled from local network devices and centralized within the controller. The controller maintains a global view of the network and programs the forwarding tables on physical network devices via Southbound APIs. The physical switches and routers continue to perform hardware-based data plane packet forwarding.

Step-by-Step Solution

1
Analyze traditional network architecture roles
In traditional networking, every router and switch operates distributed control, management, and data planes locally on the device.
Each node runs individual routing protocols (e.g., OSPF) to independently populate its own forwarding table.
2
Compare controller-based (SDN) plane separation
Controller-based networks decouple the control plane from distributed devices and centralize it onto an SDN controller (e.g., Cisco DNA Center / Catalyst Center).
Centralization allows global topology awareness and policy enforcement, while network elements (switches/routers) retain only the data plane for forwarding packets based on controller instructions.
3
Select the option describing this plane decoupling correctly
The statement highlighting centralized control plane policy generation paired with distributed data plane hardware forwarding accurately reflects SDN design.
It correctly identifies the operational roles of the controller and network devices.

Key Concept

Separation and centralization of control plane functions in controller-based SDN architectures versus distributed control planes in traditional networks.
Question 72Question →

A network engineer is inspecting an API interaction log between a Python script and a Cisco DNA Center REST API controller. The log indicates that the script transmitted an HTTP request targeting an existing template resource URI using the HTTP PATCH verb. Which statement correctly describes the operational effect of this request on the API controller?

Show answer & explanation

Answer: It modifies only the specific attributes provided in the request payload while keeping all other existing resource fields intact.

Answer

The HTTP PATCH request updates only the specific fields included in the payload while preserving unmentioned resource attributes.
In RESTful architecture, the HTTP PATCH method corresponds to the Update operation in CRUD, specifically designed for partial modifications. When a PATCH request is processed, the server updates only the key-value pairs defined in the request body, leaving all other attributes of the target resource unchanged.

Step-by-Step Solution

1
Identify the HTTP verb used in the REST API request.
The request utilizes the HTTP PATCH method.
Mapping the HTTP verb to its corresponding CRUD operation reveals the intended action on the resource.
2
Differentiate HTTP PATCH operational semantics from HTTP PUT and HTTP POST.
HTTP POST creates resources, HTTP PUT completely replaces existing resources, and HTTP PATCH selectively updates specified attributes.
Understanding REST API standards ensures accurate interpretation of API request payloads and controller responses.

Key Concept

REST HTTP Verbs to CRUD Mapping (PATCH vs PUT/POST)
Question 73Question →

A network security team is establishing firewall rules to allow a newly selected configuration management tool to operate between a centralized master server and enterprise network devices. The security policy permits target nodes to periodically initiate encrypted outbound connections over TCP port 8140 to pull declarative configuration manifests written in a native domain-specific language (.pp). Which configuration management mechanism and operational model match these technical requirements?

Show answer & explanation

Answer: Puppet, using an agent-based pull model where target devices initiate communication to fetch manifests from the master server.

Answer

Puppet, using an agent-based pull model where target devices initiate communication to fetch manifests from the master server.
Puppet utilizes an agent-based pull model where managed devices (or proxy agents) periodically connect to the Puppet Master over TCP port 8140 to pull compiled configuration catalogs derived from Puppet DSL manifest files (.pp).

Step-by-Step Solution

1
Analyze the network traffic pattern and port requirement in the scenario.
The requirement specifies outbound connections initiated by nodes over TCP port 8140.
Puppet Master and agent communications default to TCP port 8140, whereas Chef uses TCP port 443 and Ansible uses SSH (TCP port 22).
2
Evaluate the file type and language described in the scenario.
Declarative manifests using .pp files correspond to Puppet DSL.
Puppet uses Puppet DSL stored in manifests (.pp files), Ansible uses YAML playbooks (.yml), and Chef uses Ruby DSL recipes (.rb).
3
Determine the operational direction (push vs. pull) and agent reliance.
Nodes periodically initiating outbound requests to fetch configurations represents a pull-based agent architecture.
Puppet operates predominantly on an agent-based pull model where the managed node requests its compiled catalog from the master.

Key Concept

Puppet Architecture and Operational Characteristics (Agent-Based, Pull Model, TCP 8140, Manifests)
Question 74Question →

An organization is modernizing its enterprise infrastructure by integrating a centralized network controller alongside legacy autonomous routing and switching equipment. Which two statements accurately highlight the operational and architectural differences between traditional networking and controller-based networking? (Select two.)

Select all that apply

Show answer & explanation

Answer: In traditional networking, each network device independently maintains its own control plane to compute path decisions, whereas controller-based networking centralizes control plane intelligence to program network-wide policy.; Controller-based architectures use Southbound APIs, such as NETCONF or RESTCONF, to communicate configuration and operational states down to physical network devices.

Answer

The two correct statements are that traditional networks rely on distributed control planes while controller-based networks centralize control plane intelligence, and that controller-based architectures leverage Southbound APIs (such as NETCONF or RESTCONF) to communicate down to physical network devices.
In traditional networking, each network device executes its own control plane algorithms independently (distributed control plane). In a controller-based architecture, control plane functions are centralized on the controller, which uses Southbound APIs (such as NETCONF or RESTCONF) to manage and program the underlying physical network devices.

Step-by-Step Solution

1
Analyze control plane separation differences between traditional and controller-based models.
Confirm that traditional network nodes individually maintain autonomous control planes, whereas controller-based SDN models centralize policy definition and control plane orchestration.
Control plane centralization is the core architectural differentiator in software-defined networking.
2
Evaluate protocol plane definitions (Northbound vs. Southbound interfaces).
Identify that Southbound APIs (e.g., NETCONF, RESTCONF, OpenFlow) operate between the controller and network devices, while Northbound APIs operate between the controller and higher-level applications.
Southbound APIs enable the controller to program data plane devices below it.

Key Concept

Decoupling of Control and Data Planes & Interface Roles (SBI vs NBI)
Question 75Question →

A network engineer is auditing a campus software-defined fabric infrastructure. During a traffic flow trace between two endpoints residing in different subnets, the engineer notes that the ingress fabric edge switch must resolve the location of a remote Endpoint Identifier (EID) to a destination Routing Locator (RLOC) IP address before encapsulating the frame. Which protocol and architectural layer are directly responsible for maintaining and querying this mapping database?

Show answer & explanation

Answer: Locator/ID Separation Protocol (LISP) operating at the fabric control plane layer

Answer

Locator/ID Separation Protocol (LISP) operating at the fabric control plane layer
The correct answer identifies LISP at the fabric control plane layer. In Cisco SD-Access fabric architectures, LISP acts as the control plane tracking system. It maintains a database mapping host addresses (Endpoint Identifiers or EIDs) to the IP addresses of the edge switches to which they are attached (Routing Locators or RLOCs).

Step-by-Step Solution

1
Identify the requirement in the scenario
The scenario describes looking up an Endpoint Identifier (EID) to find its corresponding Routing Locator (RLOC) IP address.
Before an ingress fabric edge switch can encapsulate customer traffic into VXLAN headers, it must query the mapping database to identify the remote edge node where the target destination host is currently registered.
2
Map the operation to the SDN architectural component
LISP serves as the control plane protocol that manages the map-server/map-resolver database in SD-Access fabrics.
LISP separates endpoint identity (EID) from network location (RLOC), allowing efficient lookup and tracking of host mobility across the fabric overlay.
3
Differentiate control plane, overlay data plane, and underlay transport
The control plane handles EID-to-RLOC mappings (LISP), the overlay data plane handles packet encapsulation (VXLAN), and the underlay transport handles physical IP routing (OSPF/IS-IS).
Understanding the distinct separation of duties prevents misattributing control database functions to data plane encapsulation or underlay routing protocols.

Key Concept

Separation of Underlay Routing, Overlay Encapsulation, and Fabric Control Plane Mapping in Software-Defined Architectures
Question 76Question →

A network engineer is evaluating configuration management mechanisms for enterprise network automation. Which TWO statements accurately describe the operational capabilities and architecture of Ansible? (Select two.)

Select all that apply

Show answer & explanation

Answer: It operates using an agentless architecture, communicating with managed devices over standard protocols such as SSH or NETCONF.; It uses YAML-formatted files known as Playbooks to define configuration tasks and desired states.

Answer

The correct statements are those identifying Ansible's agentless architecture over SSH/NETCONF and its usage of YAML-formatted Playbooks for configuration automation.
Ansible is defined by its agentless operational model (connecting over SSH, NETCONF, or REST APIs) and its use of YAML-formatted Playbooks to define configuration tasks. These traits eliminate the need to install and maintain client-side agent daemons on network devices.

Step-by-Step Solution

1
Analyze Ansible's communication model
Ansible executes commands remotely without installing client agent software on target network nodes, leveraging standard protocols such as SSH and NETCONF.
Agentless operation simplifies network management because routers and switches often run closed operating systems where agent installation is restricted.
2
Identify Ansible's data structures and configuration files
Ansible leverages human-readable YAML syntax structured into Playbooks.
YAML Playbooks describe the target host inventories, task modules, and parameters sent from the central control node to managed devices.

Key Concept

Operational capabilities and architecture of Ansible vs Puppet and Chef
Estimated Time:1m 0s
Question 77Question →

A network engineer is implementing automated API calls against a Cisco Catalyst Center controller. Match each HTTP request verb to its corresponding CRUD operation and database handling behavior.

Click a left item, then click its matching right item

Items

HTTP POST
HTTP PUT
HTTP PATCH
HTTP DELETE

Matches

Show answer & explanation

Answer

HTTP POST matches creating a new collection resource (CRUD: Create); HTTP PUT matches full resource replacement (CRUD: Update/Replace); HTTP PATCH matches partial attribute updates (CRUD: Update/Modify); HTTP DELETE matches target resource removal (CRUD: Delete).
In REST-based automation, HTTP verbs map directly to specific CRUD operations: POST instantiates new entries, PUT performs a full resource replacement, PATCH updates partial attributes, and DELETE removes resources.

Step-by-Step Solution

1
Map the resource creation and deletion verbs to their primary CRUD definitions.
POST creates new sub-resources under a endpoint collection, while DELETE removes existing resources.
RESTful conventions define POST for creation operations and DELETE for resource removal.
2
Differentiate between full and partial resource update operations.
PUT executes a complete replacement of the entity, whereas PATCH updates only designated fields.
Sending a PUT request replaces the entire target state, while PATCH modifies specific attributes without wiping omitted parameters.

Key Concept

RESTful API HTTP Verbs and CRUD Mapping
Question 78Question →

A network automation engineer is selecting configuration management tools for an enterprise infrastructure overhaul. Match each configuration management mechanism or artifact on the left with its corresponding operational model, transport mechanism, and configuration language characteristics on the right.

Click a left item, then click its matching right item

Items

Ansible
Puppet
Chef
Ansible Playbook

Matches

Show answer & explanation

Answer

Ansible matches with the agentless push model using SSH/NETCONF and YAML; Puppet matches with the agent-based pull model communicating over TCP 8140 using Puppet DSL manifests; Chef matches with the agent-based pull model communicating over TCP 443 using Ruby DSL recipes; Ansible Playbook matches with the YAML-encoded file mapping host inventory groups to task executions.
Each automation mechanism exhibits specific architectural and transport signatures. Ansible uses an agentless push architecture over SSH/NETCONF with YAML files (Playbooks). Puppet uses an agent-based pull model communicating over TCP port 8140 with Puppet DSL manifests. Chef uses an agent-based pull model communicating over TCP port 443 (HTTPS) with Ruby DSL recipes.

Step-by-Step Solution

1
Analyze Ansible's core architecture and communication method.
Ansible is agentless, uses an active push model, relies on SSH/NETCONF for network devices, and uses YAML formatting.
Eliminates the requirement to install local daemon agents on network switches and routers.
2
Analyze Puppet's operational model, transport ports, and configuration structure.
Puppet defaults to an agent-based pull model, communicates with a central master over TCP port 8140, and uses Puppet DSL manifests.
Agents periodically poll the Puppet Master to pull catalog updates and maintain state enforcement.
3
Analyze Chef's operational model, transport ports, and configuration structure.
Chef uses an agent-based pull model, communicates with the Chef server over TCP port 443 (HTTPS), and utilizes Ruby DSL recipes/cookbooks.
Chef Client runs periodically on target nodes to pull recipes from the server.
4
Identify the role and structure of an Ansible Playbook.
An Ansible Playbook is the YAML document containing plays, host specifications, and task lists executed by Ansible.
Distinguishes the tool framework (Ansible) from its execution file artifact (Playbook).

Key Concept

Capabilities and Architectural Differences of Network Configuration Management Tools (Ansible, Puppet, Chef)
Question 79Question →

Match each Cisco Software-Defined Architecture component or protocol on the left with its corresponding architectural role or operational function on the right.

Click a left item, then click its matching right item

Items

Physical Routed Underlay
VXLAN Overlay Data Plane
LISP Fabric Control Plane
Fabric Edge Node

Matches

Show answer & explanation

Answer

The Physical Routed Underlay provides transport IP reachability via traditional routing protocols; the VXLAN Overlay Data Plane encapsulates data frames into UDP packets; the LISP Fabric Control Plane manages the mapping database between Endpoint Identifiers (EIDs) and Routing Locators (RLOCs); and the Fabric Edge Node authenticates endpoints and initiates overlay encapsulation.
In software-defined fabric architectures, responsibilities are strictly divided: the physical routed underlay provides IP transport for fabric nodes using standard IGPs; VXLAN handles data plane encapsulation of user traffic into UDP tunnels; LISP acts as the control plane to map host identities (EIDs) to switch locations (RLOCs); and Fabric Edge nodes interface directly with endpoints to perform authentication and overlay encapsulation.

Step-by-Step Solution

1
Identify the primary role of the Physical Routed Underlay.
Determined that the underlay strictly provides underlying IP reachability between switch loopback interfaces using standard IGPs.
The underlay infrastructure provides basic packet transport between fabric switches and operates independently of overlay endpoints.
2
Identify the function of the VXLAN Overlay Data Plane.
Matched VXLAN to data plane encapsulation of Layer 2 frames within UDP port 4789 headers.
VXLAN is the data plane encapsulation standard used in modern software-defined fabrics to tunnel endpoint traffic over an IP underlay.
3
Identify the function of the LISP Fabric Control Plane.
Matched LISP to the control plane tracking mechanism that maps EID host addresses to RLOC switch addresses.
LISP eliminates the need for broadcast-based flood-and-learn mechanisms by maintaining an explicit mapping database of host locations.
4
Identify the operational responsibilities of the Fabric Edge Node.
Matched the Fabric Edge Node to connecting, authenticating, and encapsulating endpoint traffic into the fabric overlay.
Fabric Edge nodes act as first-hop access switches where endpoints connect and where overlay tunnel encapsulation originates.

Key Concept

Software-Defined Fabric Architecture: Separation of Underlay, Overlay Data Plane, Control Plane, and Edge Roles
Estimated Time:2m 0s
Question 80Question →

An enterprise network operations team is replacing a legacy distributed routing environment with a controller-based architecture using Cisco DNA Center. When an administrator configures a new quality-of-service (QoS) policy across all campus switches, how does the deployment of this policy differ in the controller-based model compared to the traditional network model?

Show answer & explanation

Answer: The policy is defined once on the centralized controller and automatically provisioned to all managed switches using southbound APIs, whereas traditional networks require manual device-by-device configuration via CLI or SNMP.

Answer

In a controller-based network model, policies are defined centrally on the controller and provisioned down to network devices via southbound APIs, replacing per-device CLI manual configurations.
Controller-based networking abstracts network management and centralizes policy control. Administrators specify intent once on the controller (e.g., Cisco DNA Center), which uses southbound APIs to translate policies and configure all underlying network devices automatically. In contrast, traditional networks rely on per-device management where each switch must be configured individually via CLI or scripts.

Step-by-Step Solution

1
Analyze policy provisioning in traditional network architectures.
In traditional networks, control and management planes are distributed across each individual device, requiring network engineers to log into each device separately to apply configurations using CLI scripts or SNMP.
Every network node functions autonomously in terms of configuration management.
2
Analyze policy provisioning in controller-based SDN architectures.
In controller-based networks, management and control intelligence are centralized. High-level intent is configured on the controller and propagated automatically to all target devices through southbound protocols (e.g., NETCONF, RESTCONF, OpenFlow).
Centralized abstraction separates policy creation from physical infrastructure execution.

Key Concept

Centralized Management vs Distributed Configuration and Southbound API Roles
Estimated Time:1m 30s
PreviousPage 4 / 10Next