Examkin

Automation and Programmability

200 questions

All types200Multiple choice102Multiple select47Matching45Ordering6
Question 1Question →

A network administrator is using Software Image Management (SWIM) within Cisco DNA Center to upgrade a Catalyst switch. Place the steps of the standard SWIM deployment workflow in the correct operational sequence from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct operational sequence for Software Image Management (SWIM) in Cisco DNA Center is: 1) Import or discover the target software image into the Cisco DNA Center image repository, 2) Designate the software image as the 'Golden Image' for the corresponding device family and role, 3) Perform pre-upgrade readiness checks to verify storage capacity, hardware compatibility, and device health, 4) Distribute the software image file from Cisco DNA Center to the local storage of the target device, and 5) Activate the software image on the device and initiate a system reboot to complete the upgrade.
The Cisco DNA Center Software Image Management (SWIM) process follows a logical zero-downtime staging sequence: ingesting the image file into the central controller, tagging it as the Golden Image standard for device role compliance, running automated pre-upgrade checks to validate disk space and device health, distributing the image file to local device flash storage, and finally activating the software image through a boot configuration change and system restart.

Step-by-Step Solution

1
Import the target software image into the Cisco DNA Center repository.
The operating system image binary is ingested and stored centrally.
Cisco DNA Center cannot manage, verify, or push image files until they exist in its software image repository.
2
Designate the imported software image as a Golden Image.
Cisco DNA Center marks device models lacking this software version as non-compliant.
Establishing a Golden Image defines the software standard for a specific physical device model and site function.
3
Run pre-upgrade readiness checks on the target device.
Flash storage capacity, hardware platform compatibility, and network stability are confirmed.
Pre-checks prevent distribution failures caused by missing prerequisites or insufficient disk space.
4
Distribute the image file to the network device.
The image file is staged in the target switch's flash memory.
Transferring the image staged in device flash separates file transfer from the maintenance window reboot.
5
Activate the image and initiate a device reboot.
The device modifies its boot statement and reboots into the new operating system.
Activation finalizes the software upgrade process by applying the newly staged image to operational memory upon reboot.

Key Concept

Cisco DNA Center Software Image Management (SWIM) Workflow Sequence
Question 2Question →

A network administrator is onboarding a brand-new Cisco Catalyst switch into an enterprise network using Cisco Catalyst Center (formerly Cisco DNA Center) Network Plug and Play (PnP). Place the steps of the Day-0 PnP device discovery and provisioning process into the correct operational sequence from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct operational sequence begins with the switch extracting the controller address from DHCP Option 43, establishing a secure TLS connection to transmit its serial number, matching the serial number to claim the device in Cisco Catalyst Center, provisioning the Golden software image and Day-0 configuration template, and finally rebooting to establish full Assurance telemetry integration.
The standard Network Plug and Play (PnP) zero-touch onboarding workflow follows a strict deterministic sequence: 1) The unconfigured device boots and uses DHCP Option 43 to obtain the Cisco Catalyst Center IP. 2) It opens a TLS connection to the controller and reports its serial number and Product ID (PID). 3) Cisco Catalyst Center matches the serial number, claims the device, and assigns it to a site hierarchy. 4) The controller pushes the designated Golden software image (SWIM) and Day-0 configuration template. 5) The switch reboots with the new image/config and registers for telemetry/Assurance monitoring.

Step-by-Step Solution

1
Identify initial network discovery
The device receives network settings and decodes vendor-specific DHCP Option 43 containing the controller IP.
Factory-default switches require an automated mechanism (DHCP Option 43 or Cloud PnP Redirect) to locate Cisco Catalyst Center without local console intervention.
2
Establish control channel and device identification
The device initiates a secure TLS session to Cisco Catalyst Center and sends identity parameters (serial number and PID).
The controller requires cryptographic session establishment and device identification before executing any management operations.
3
Claim device and map site policy
Cisco Catalyst Center claims the serial number and maps it to a designated network site.
Site assignment dictates which software image policies (SWIM) and Day-0 configuration templates apply to the device.
4
Deploy image and template configuration
Cisco Catalyst Center transfers the Golden IOS XE image and provisions the Day-0 configuration.
Provisioning software compliance and base network configuration must occur prior to operational activation.
5
Finalize activation and assurance telemetry registration
The switch reloads into the new image, applies the configuration, and syncs telemetry with Assurance.
Applying the golden image and configuration requires a system reload, completing the zero-touch onboarding lifecycle.

Key Concept

Cisco Catalyst Center Network Plug and Play (PnP) Day-0 Device Onboarding Workflow
Question 3Question →

Match each traditional network management practice on the left with its primary operational benefit provided by network automation on the right.

Click a left item, then click its matching right item

Items

Manual per-device CLI configuration
Periodic NMS SNMP polling
Ad-hoc manual changes per router

Matches

Show answer & explanation

Answer

Manual per-device CLI configuration matches with Rapid, consistent deployment using centralized templates; Periodic NMS SNMP polling matches with Near real-time data collection via model-driven push telemetry; Ad-hoc manual changes per router match with Reduction of human error and prevention of configuration drift.
Automation impacts network management by enabling centralized template-driven provisioning to replace CLI entries, utilizing push telemetry instead of polling, and establishing continuous compliance to eliminate configuration drift.

Step-by-Step Solution

1
Identify the automated alternative to manual CLI provisioning.
Centralized controllers or scripts use templates to apply standardized configurations rapidly across many devices simultaneously.
Automation eliminates the need to connect to each network device individually via SSH or console.
2
Identify the automated advancement over legacy SNMP polling.
Streaming telemetry continuously pushes device performance data to monitoring systems.
Traditional SNMP pulls data periodically, whereas telemetry provides immediate visibility with lower CPU overhead.
3
Identify the operational benefit of eliminating ad-hoc per-device changes.
Standardized automated change execution prevents configuration drift and reduces human error.
Manual changes create inconsistent device states over time, which automation actively prevents.

Key Concept

Operational transformation from manual, per-device management to centralized, telemetry-driven automated network administration.
Question 4Question →

An enterprise network engineering team is evaluating the operational impact of transitioning from traditional SNMPv2c polling and manual CLI management to an automated, controller-based network architecture using RESTCONF and streaming telemetry. During a recent outage post-mortem, the team noted two major operational issues: high CPU utilization on core switches caused by frequent SNMP polling requests led to missed monitoring alerts, and manual CLI configuration updates across 200 branch switches caused severe configuration drift. Which statement accurately describes how adopting model-driven telemetry and centralized controller automation resolves these specific operational deficiencies?

Show answer & explanation

Answer: Streaming telemetry utilizes a push-based subscription model over protocols like gRPC to continuously transmit data without CPU-intensive polling, while centralized controllers leverage structured data models and APIs to enforce automated configuration consistency across all managed devices.

Answer

Streaming telemetry utilizes a push-based subscription model over protocols like gRPC to continuously transmit data without CPU-intensive polling, while centralized controllers leverage structured data models and APIs to enforce automated configuration consistency across all managed devices.
The correct answer accurately reflects the two primary operational shifts brought by network automation: (1) Replacing pull-based SNMP polling with subscription-based streaming telemetry (e.g., gRPC, NETCONF, RESTCONF) to dramatically reduce device CPU overhead and improve monitoring granularity; and (2) Replacing manual CLI configuration with centralized controller APIs and data models (YANG) to automate change management, guarantee consistency, and prevent configuration drift.

Step-by-Step Solution

1
Analyze the operational deficiency related to network monitoring (SNMP polling overhead).
Identify that traditional SNMP uses a pull mechanism where management stations repeatedly query devices, causing high CPU consumption. Streaming telemetry solves this by using a push mechanism based on subscriptions, allowing devices to continuously stream structured data with significantly less overhead.
Understanding the shift from reactive pull-based polling to proactive push-based telemetry.
2
Analyze the operational deficiency related to device configuration management (configuration drift across 200 branch switches).
Identify that manual per-device CLI configuration leads to inconsistencies and human error. Centralized controller automation uses RESTful APIs and YANG data models to treat network configurations programmatically and declaratively, ensuring uniform deployment and automated compliance auditing.
Understanding how controller-driven automation enforces central intent and eliminates manual configuration errors.
3
Evaluate the choices to identify the statement that accurately addresses both telemetry push mechanics and controller-driven configuration consistency.
Select the option stating that streaming telemetry uses push subscriptions to eliminate polling overhead and centralized controllers use structured data models/APIs to enforce consistency.
Correlating the theoretical benefits of network automation with real-world enterprise operational shifts.

Key Concept

Operational impacts of network automation: Push-based telemetry vs SNMP polling, and controller/API-driven consistency vs manual CLI drift.
Question 5Question →

A financial enterprise migrates its multi-site network infrastructure from legacy per-device CLI administration to a centralized configuration management and model-driven telemetry architecture. Which two statements accurately describe the operational impacts of adopting this automation paradigm?

Select all that apply

Show answer & explanation

Answer: Configuration drift across network switches is minimized through centralized enforcement of declarative data models.; Network health visibility improves because streaming telemetry continuously pushes structured data subscription feeds without relying on periodic pull queries.

Answer

The two correct operational impacts are that configuration drift is minimized through centralized enforcement of declarative data models, and network health visibility improves via model-driven streaming telemetry pushing real-time structured data.
Centralized network automation establishes a single source of truth using declarative configuration models, which continuously mitigates configuration drift. Furthermore, replacing legacy SNMP polling with model-driven streaming telemetry enables real-time push subscriptions of structured metrics, significantly improving network visibility and operational efficiency.

Step-by-Step Solution

1
Evaluate the effect of centralized configuration management on device compliance.
Centralized tools compare live configurations against a defined declarative standard, preventing unapproved local modifications and eliminating configuration drift.
Traditional manual CLI edits lead to inconsistent configurations across devices, whereas automated controllers enforce a single source of truth.
2
Evaluate the difference between legacy SNMP polling and model-driven telemetry.
Streaming telemetry pushes data continuously or on event trigger, providing granular visibility with lower CPU overhead compared to periodic SNMP polling.
Telemetry uses subscription models over transport protocols like gRPC/NETCONF to efficiently stream operational stats.
3
Analyze distractor statements for technical accuracy regarding management architecture.
Ansible is agentless (no on-box daemon required), and HTTP GET is strictly a non-mutating read operation.
Identifying agent vs agentless paradigms and standard HTTP/REST CRUD verb behaviors exposes the errors in the wrong options.

Key Concept

Impact of Automation and Model-Driven Telemetry on Enterprise Network Management
Question 6Question →

A network engineering team is evaluating configuration management tools to automate Cisco IOS XE switch deployments. The architecture mandates that managed network devices must not require a persistent local management daemon or software agent, and all configuration task execution must be driven from a central control node using native management protocols and human-readable YAML files.

Which of the following operational characteristics correctly describe the selected configuration management tool? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: The framework utilizes a push-based communication model where the control node initiates management sessions directly to target network devices.; Configuration tasks are defined in playbooks and executed across endpoints over standard SSH or NETCONF transport protocols.

Answer

The configuration management mechanism described is Ansible, which uses a push-based communication model from a control node over standard transport protocols (SSH/NETCONF) with YAML playbooks and requires no agent software on target endpoints.
The scenario describes Ansible, which is unique among the three major configuration management tools for being completely agentless on target network devices. Ansible relies on a push-based model where the control node opens standard transport sessions (such as SSH or NETCONF) to execute tasks defined in YAML playbooks.

Step-by-Step Solution

1
Analyze the architectural requirements stated in the scenario.
The requirements specify an agentless architecture, central control node driving execution, native management protocols (SSH/NETCONF), and YAML files.
Identifying these key attributes narrows the tool down to Ansible, distinguishing it from agent-based pull systems like Puppet and Chef.
2
Evaluate the delivery mechanism and transport method of Ansible.
Ansible uses a push model where the control node initiates connections to managed devices using SSH or NETCONF.
Because no persistent agent daemon is installed on managed network switches, Ansible relies on native network management transport protocols.
3
Verify file structure and contrast with alternative mechanisms.
Ansible uses YAML playbooks. In contrast, Puppet uses Puppet DSL manifests over TCP 8140 (pull), and Chef uses Ruby recipes/cookbooks over TCP 443 (pull).
This confirms that options describing push-based execution over SSH/NETCONF and YAML playbooks are correct, while options referring to TCP 8140 pull operations or Ruby cookbooks describe Puppet and Chef.

Key Concept

Ansible Agentless Push Architecture and Protocol Capabilities
Estimated Time:2m 0s
Question 7Question →

A network engineering team is evaluating the operational differences between a traditional distributed architecture and a centralized controller-based network deployment. Which operational characteristic correctly distinguishes the control plane handling in a controller-based network from that of a traditional distributed network?

Show answer & explanation

Answer: Control plane intelligence is centralized within a software controller that dictates forwarding policies across the network, whereas traditional network devices each run independent control plane processes locally.

Answer

Control plane intelligence is centralized within a software controller that dictates forwarding policies across the network, whereas traditional network devices each run independent control plane processes locally.
The correct answer highlights the fundamental shift from distributed to centralized architecture. In traditional networking, every device operates its own control plane protocols to learn routes and switching paths. In a controller-based architecture, a centralized controller offloads or manages these control plane duties and programs the forwarding tables on underlying data plane devices.

Step-by-Step Solution

1
Analyze how traditional networks handle control plane operations
Identify that traditional network infrastructure relies on distributed intelligence where each switch or router runs its own control plane algorithms (e.g., OSPF, EIGRP, STP) locally.
Understanding traditional architecture requires recognizing that every node operates autonomously to build its routing and MAC tables.
2
Analyze how controller-based networks handle control plane operations
Identify that controller-based networks shift control plane intelligence to a centralized software controller.
Centralization allows the controller to possess global visibility of the network topology and programmatically direct device forwarding behaviors via Southbound APIs.
3
Compare the two models to select the correct architectural distinction
Confirm that centralizing control plane intelligence on a software controller versus running independent local control plane algorithms per device is the primary architectural difference.
This fundamental shift enables automated management, intent-based policies, and consistent network-wide provisioning.

Key Concept

Centralized Control Plane vs. Distributed Control Plane
Question 8Question →

A network administrator needs to deploy several new Cisco switches across enterprise branch offices. Which Cisco DNA Center feature enables zero-touch onboarding to provision these unconfigured network devices automatically upon initial power-on?

Show answer & explanation

Answer: Network Plug and Play (PnP)

Answer

Network Plug and Play (PnP) is the Cisco DNA Center feature responsible for zero-touch provisioning of new devices.
Network Plug and Play (PnP) provides a unified, secure system for Cisco DNA Center customers to onboard new Cisco routers, switches, and wireless access points with zero-touch provisioning. Unconfigured devices contact Cisco DNA Center automatically using DHCP option 43, DNS, or Cisco Smart Call Home to retrieve configuration files and initial images.

Step-by-Step Solution

1
Identify the primary requirement in the scenario.
The requirement is zero-touch onboarding of unconfigured devices upon initial power-on.
Branch deployments require automated Day-0 provisioning without manual console interaction.
2
Evaluate Cisco DNA Center functional pillars against the requirement.
Network Plug and Play (PnP) handles Day-0 automated discovery and provisioning.
PnP connects unconfigured devices to Cisco DNA Center via DHCP or DNS discovery to download configuration and software images.

Key Concept

Cisco DNA Center Network Plug and Play (PnP) Day-0 Provisioning
Question 9Question →

An enterprise network operations team is transitioning from managing 500 access switches individually via manual CLI sessions to using a centralized, controller-driven automation framework. Which operational benefit directly results from adopting this automated network management model?

Show answer & explanation

Answer: Device configurations are defined using centralized software templates and applied via programmatic APIs, significantly reducing configuration drift and human error.

Answer

Device configurations are defined using centralized software templates and applied via programmatic APIs, significantly reducing configuration drift and human error.
Moving from per-device CLI management to a centralized automation framework enables network administrators to define configurations centrally as standardized data models or templates. Pushing these configurations via programmatic APIs ensures compliance across all target devices, virtually eliminating manual entry errors and configuration drift.

Step-by-Step Solution

1
Analyze the operational transition from traditional CLI management to centralized automation.
Traditional management relies on individual per-device CLI configuration over SSH, leading to inconsistency (configuration drift) and high risk of human error.
Per-device manual configuration does not scale efficiently across hundreds of network devices.
2
Identify the primary benefit of controller-driven API management.
Centralized controllers enforce intent-based network management where policy and configuration templates are pushed automatically via RESTful or RPC APIs.
Template-driven deployment ensures configuration consistency across the entire infrastructure.

Key Concept

Impact of Centralized Controller-Based Automation on Network Operations
Question 10Question →

What is the correct sequential order of steps required to deploy a new baseline software update across enterprise switches using Cisco DNA Center Software Image Management (SWIM)?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct operational order for Cisco DNA Center Software Image Management (SWIM) is: 1) Import the software image into the repository, 2) Tag the image as Golden for the target device family, 3) Perform a compliance audit against inventory devices, and 4) Distribute and activate the image on non-compliant devices.
The standard Cisco DNA Center Software Image Management (SWIM) workflow follows four logical phases: image intake into the central repository, designating the image as Golden to define baseline compliance rules, performing compliance audits against managed network inventory, and finally scheduling distribution and activation to upgrade non-compliant hardware.

Step-by-Step Solution

1
Ingest software image
The software file is available locally within Cisco DNA Center image management.
The controller cannot manage or deploy images that have not been ingested into its central repository.
2
Define Golden Image standard
A software baseline is established for a specific switch family or role.
Designating an image as Golden tells the controller which version devices of that family are expected to run.
3
Execute compliance audit
Devices running mismatched software versions are marked non-compliant.
Compliance audits compare active device inventory versions against the assigned Golden image baseline.
4
Deploy image (distribute & activate)
Target devices are upgraded to the Golden software image.
Distributing transfers the file to device storage, and activation applies the update and reboots the hardware.

Key Concept

Cisco DNA Center Software Image Management (SWIM) Lifecycle
Question 11Question →

An enterprise network team is transitioning from traditional per-device CLI configuration management to a centralized, API-driven network automation framework using controller-based orchestration and configuration management tools. During an operational review, engineers highlight that out-of-band manual CLI edits performed directly on individual switches regularly cause configuration drift and compliance failures across sites. Which operational shift brought by network automation directly mitigates this specific issue?

Show answer & explanation

Answer: Establishing a centralized single source of truth that enables continuous compliance auditing and automated state reconciliation to remediate local configuration drift.

Answer

Establishing a centralized single source of truth that enables continuous compliance auditing and automated state reconciliation to remediate local configuration drift.
Centralized network automation replaces ad-hoc local CLI changes with a single source of truth (such as version-controlled repositories or controller-based policies). Automated systems continuously monitor device states, detect configuration drift caused by manual intervention, and automatically re-apply standard configurations to restore compliance across the network infrastructure.

Step-by-Step Solution

1
Identify the core operational problem described in the scenario.
The primary issue is configuration drift resulting from manual, out-of-band CLI changes on individual switches across multiple sites.
Traditional per-device management creates inconsistency because manual local changes are not tracked centrally.
2
Evaluate how network automation shifts operational management models.
Automation shifts configuration management from decentralized manual entry to central controller/repository orchestration (version-controlled single source of truth).
By defining intent centrally (e.g., via Git, DNA Center, or Ansible playbooks), automation tools can periodically validate real-time device states against defined templates.
3
Match the solution to the specific mitigation outcome.
Automated compliance checks detect discrepancies between actual device states and intended states, enforcing automated reconciliation to reverse manual CLI edits.
This directly resolves configuration drift and enforces enterprise-wide consistency.

Key Concept

Impact of Automation on Network Management - Configuration Drift and Centralized Single Source of Truth
Question 12Question →

A network engineer is deploying new Cisco Catalyst switches across multiple branch offices using Cisco DNA Center Network Plug and Play (PnP). The switches are unpacked and powered on with default factory settings. Which mechanism enables these unconfigured devices to locate the Cisco DNA Center controller for Day-0 automated onboarding?

Show answer & explanation

Answer: DHCP Option 43 configured on the local DHCP server specifying the Cisco DNA Center controller IP address.

Answer

DHCP Option 43 configured on the local DHCP server specifying the Cisco DNA Center controller IP address.
In Cisco Network Plug and Play (PnP), factory-default devices request an IP address via DHCP upon boot. By configuring DHCP Option 43 on the local DHCP server, the server returns vendor-specific information containing the IP address or URL of the Cisco DNA Center PnP server, enabling the switch to automatically contact the controller for Day-0 provisioning.

Step-by-Step Solution

1
Identify the requirement for Day-0 network device onboarding in Cisco DNA Center.
The devices are in a factory-default state without IP addresses or SSH credentials configured.
Day-0 provisioning relies on Network Plug and Play (PnP) zero-touch discovery mechanisms.
2
Evaluate how unconfigured devices request network configuration and controller location.
Upon booting, the device sends a DHCP request to acquire an IP address and vendor-specific DHCP options.
DHCP Option 43 conveys the IP address of the PnP server (Cisco DNA Center) to the device.
3
Select the correct discovery mechanism.
DHCP Option 43 allows the switch to automatically locate and establish communication with Cisco DNA Center.
This enables fully automated, zero-touch Day-0 device provisioning.

Key Concept

Cisco DNA Center Network Plug and Play (PnP) Day-0 Discovery
Question 13Question →

An enterprise network engineer is using Cisco DNA Center Software Image Management (SWIM) to standardize software images across a fleet of Catalyst access switches. A target switch is currently flagged as non-compliant against the designated Golden Image. When the engineer initiates the software image distribution and activation workflow from Cisco DNA Center, which operational sequence does the controller follow to complete the upgrade?

Show answer & explanation

Answer: Cisco DNA Center runs pre-upgrade checks, copies the Golden Image file to the switch storage, verifies checksum integrity, updates the boot order, reboots the switch, and performs post-upgrade compliance checks.

Answer

Cisco DNA Center runs pre-upgrade checks, copies the Golden Image file to the switch storage, verifies checksum integrity, updates the boot order, reboots the switch, and performs post-upgrade compliance checks.
The correct answer accurately outlines the step-by-step process of Cisco DNA Center Software Image Management (SWIM). SWIM performs pre-checks (such as storage availability validation), securely distributes the software image to the switch local flash, validates the checksum to prevent image corruption, updates the device boot options, reboots the switch to load the new image, and runs post-checks to confirm device health and Golden Image compliance.

Step-by-Step Solution

1
Analyze the Software Image Management (SWIM) workflow in Cisco DNA Center.
SWIM is structured into two main operational phases: Distribution (copying image to device) and Activation (applying and rebooting).
Separating distribution from activation allows network administrators to pre-stage software images during production hours and schedule activations during maintenance windows.
2
Identify the automated checks and execution steps performed during SWIM execution.
Pre-upgrade checks verify disk space and hardware compatibility, the image file is transferred securely, MD5/SHA integrity checks confirm file soundness, boot variable statements are updated, the switch reboots into the new software version, and post-upgrade validation confirms operational health and golden image compliance.
These structured validation steps ensure minimal risk of device corruption or unrecoverable boot failure during automated controller-led updates.

Key Concept

Cisco DNA Center Software Image Management (SWIM) Workflow
Estimated Time:2m 0s
Question 14Question →

Match each network management paradigm or mechanism on the left with its corresponding operational impact on enterprise network management on the right.

Click a left item, then click its matching right item

Items

Model-Driven Streaming Telemetry
Declarative Configuration Management
Centralized API Orchestration
Continuous Automated Compliance Auditing

Matches

Show answer & explanation

Answer

Model-Driven Streaming Telemetry matches with eliminating periodic SNMP polling via real-time YANG subscriptions. Declarative Configuration Management matches with defining the intended end-state policy. Centralized API Orchestration matches with replacing per-device manual CLI configuration with programmatic REST operations. Continuous Automated Compliance Auditing matches with preventing configuration drift against a version-controlled single source of truth.
Each automated management paradigm addresses a key inefficiency of traditional CLI and legacy monitoring. Streaming telemetry converts monitoring from reactive pull-based polling to proactive push-based streaming using YANG schemas. Declarative tools focus on target state definition, allowing automation engines to compute differential changes automatically. Centralized APIs eliminate fragmenting configuration management across hundreds of individual SSH sessions. Automated compliance auditing establishes a deterministic feedback loop between live infrastructure and source control repositories to eliminate configuration drift.

Step-by-Step Solution

1
Analyze the operational role of Model-Driven Streaming Telemetry.
Identified as a push-based telemetry framework using structured YANG models to deliver near real-time operational data without SNMP polling overhead.
Traditional SNMP uses pull-based polling that degrades control plane performance under scale, whereas telemetry streams data continuously.
2
Differentiate between Imperative and Declarative Configuration Management paradigms.
Declarative management describes 'what the network state should be' rather than 'how to execute each CLI step'.
Declarative models allow administrators to define target states in data files (e.g., JSON/YAML) while the controller handles enforcement.
3
Evaluate the operational transition from per-device CLI management to Centralized API Orchestration.
Centralized API orchestration uses northbound/southbound RESTful endpoints to programmatically push changes across many devices simultaneously.
This shifts management from isolated SSH/Telnet sessions to repeatable software-driven transactions.
4
Examine the mechanism for preventing and mitigating configuration drift in automated environments.
Continuous automated compliance tools poll or listen for changes and compare running configurations against a version-controlled single source of truth.
Manual changes lead to state inconsistency (drift); automated auditing detects unauthorized modifications and enforces policy alignment.

Key Concept

Impact of Automation on Network Management Paradigms
Estimated Time:2m 30s
Question 15Question →

An enterprise network engineer successfully performs discovery and inventory integration for a Cisco Catalyst 9300 switch within Cisco DNA Center using SNMPv3 and SSH credentials. In the Cisco DNA Center inventory, the switch shows a status of Reachable. However, when navigating to the Assurance dashboard, the overall health score for the switch continuously reads N/A, and no telemetry data or health metrics are displayed. Further inspection shows that ICMP, SSH (TCP port 22), and SNMPv3 (UDP port 161) traffic are completely permitted through firewalls between Cisco DNA Center and the switch. Which condition is the most likely root cause for the missing Assurance health metrics?

Show answer & explanation

Answer: NETCONF traffic over TCP port 830 is blocked by an intervening security policy, preventing Cisco DNA Center from deploying telemetry profiles and establishing model-driven telemetry subscriptions.

Answer

The missing Assurance metrics are caused by NETCONF traffic over TCP port 830 being blocked by an intervening security policy, which prevents Cisco DNA Center from deploying telemetry profiles and establishing model-driven telemetry subscriptions.
Cisco DNA Center uses NETCONF (TCP port 830) to push network telemetry profiles and configure model-driven telemetry streaming on Catalyst switches. When SSH and SNMP are allowed, basic reachability and discovery succeed; however, if TCP port 830 is blocked by a firewall, Cisco DNA Center cannot apply the necessary telemetry subscriptions, causing the Assurance dashboard to report a health score of N/A.

Step-by-Step Solution

1
Analyze the management channels used by Cisco DNA Center.
Inventory discovery and basic status check rely on SSH (TCP 22) and SNMP (UDP 161), both of which are functioning.
This explains why the switch appears as Reachable in the inventory despite lacking telemetry metrics.
2
Identify the protocol requirements for Cisco DNA Center Assurance telemetry deployment.
Cisco DNA Center configures and subscribes to telemetry metrics on IOS XE switches via NETCONF using TCP port 830.
Model-driven telemetry and telemetry profile provisioning fail if NETCONF communication over TCP port 830 is blocked between the controller and managed devices.
3
Evaluate why alternative causes are incorrect.
Cisco DNA Center is controller-based and agentless, so manual HTTP POST dispatches from switch CLI or Ansible agent containers are inaccurate.
Understanding controller-led agentless workflows isolates port-blocking as the true failure point.

Key Concept

Cisco DNA Center Assurance and Model-Driven Telemetry Provisioning
Estimated Time:2m 30s
Question 16Question →

Network automation fundamentally shifts how enterprise networks are deployed, monitored, and maintained compared to traditional management methods. Match each automation capability to its corresponding operational impact on network management.

Click a left item, then click its matching right item

Items

Streaming Telemetry (Push Model)
Declarative State Models
Version-Controlled Configuration Repositories
Controller-Based API Orchestration

Matches

Show answer & explanation

Answer

Streaming Telemetry matches with replacing SNMP polling for real-time metrics; Declarative State Models match with eliminating configuration drift; Version-Controlled Repositories match with providing change auditing and rollbacks; Controller-Based APIs match with replacing per-device CLI provisioning.
Each automation component transforms network operations by moving from manual, reactive, per-device workflows to central, proactive, state-driven paradigms. Streaming telemetry replaces legacy SNMP pull requests with efficient push updates. Declarative models continuously enforce intended state to stop configuration drift. Version control repositories ensure change tracking and rapid rollbacks. API-driven controllers centralize configuration tasks across network fabrics.

Step-by-Step Solution

1
Analyze monitoring shift
Identify that pushing data continuously (streaming telemetry) replaces polling devices via SNMP.
Traditional network monitoring relies on periodic SNMP GET requests, whereas automated telemetry pushes state changes continuously.
2
Analyze configuration methodology shift
Link declarative state management to automated reconciliation of configuration drift.
Imperative CLI commands describe step-by-step actions, whereas declarative models define the target state so the system can resolve any deviation (drift).
3
Analyze change management shift
Associate Git/version control repositories with auditing and rollback features.
Infrastructure as Code (IaC) principles mandate storing configuration files in version control for tracking, auditing, and fast reversion.
4
Analyze device provisioning shift
Pair API controller management with central abstraction over per-device CLI sessions.
Central software-defined controllers use northbound APIs to automate changes across numerous devices rather than requiring individual SSH/CLI sessions.

Key Concept

Impact of Automation on Network Management
Question 17Question →

Match each network management paradigm with its defining operational impact on enterprise network environments.

Click a left item, then click its matching right item

Items

Model-Driven Streaming Telemetry
Imperative CLI Scripting
Declarative Configuration Management
Centralized Controller API Orchestration

Matches

Show answer & explanation

Answer

Model-Driven Streaming Telemetry pairs with real-time push data streams over gRPC/NETCONF. Imperative CLI Scripting pairs with rigid step-by-step execution increasing configuration drift risk. Declarative Configuration Management pairs with defining target end-state to audit and enforce consistency. Centralized Controller API Orchestration pairs with translating high-level policy via RESTful interface calls.
Model-Driven Streaming Telemetry provides real-time push telemetry via gRPC/NETCONF; Imperative CLI Scripting executes unvalidated sequential commands risking drift; Declarative Configuration Management defines the target state to enforce continuous compliance; and Centralized Controller API Orchestration uses REST APIs to apply intent-based policies across a fabric.

Step-by-Step Solution

1
Analyze Model-Driven Streaming Telemetry
Identify that streaming telemetry relies on push-based data subscription models rather than SNMP GET polling queries.
Automation shifts network visibility from reactive SNMP polling intervals to continuous real-time data streaming.
2
Analyze Imperative CLI Scripting
Identify that procedural CLI commands execute line-by-line without state awareness, leading to configuration drift.
Imperative methods specify step-by-step actions without verifying if the underlying state matches expectations.
3
Analyze Declarative Configuration Management
Identify that declarative tools focus on defining the desired end-state using data structures like YAML or JSON.
Declarative engines compare actual state against desired state to maintain system compliance automatically.
4
Analyze Centralized Controller API Orchestration
Identify that SDN controllers abstract physical underlays by exposing REST APIs for intent-based policy enforcement.
Controllers replace per-device management with centralized fabric orchestration via HTTP REST verbs.

Key Concept

Impact of Automation on Network Management
Question 18Question →

A network administrator is executing an automated software upgrade for a cluster of Cisco Catalyst access switches using Cisco DNA Center Software Image Management (SWIM). What is the correct sequence of steps required to complete the complete end-to-end SWIM deployment workflow?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct operational order for the Cisco DNA Center Software Image Management (SWIM) workflow is: 1) Upload the software image file into the Cisco DNA Center Image Repository, 2) Designate the software image as Golden for the specific Catalyst switch model family, 3) Initiate the Image Distribution job to copy the binary file to switch flash storage, 4) Run Pre-checks validation to verify system readiness, and 5) Execute the Image Activation job to set boot variables, reboot the device, and run Post-checks.
The Cisco DNA Center SWIM lifecycle follows a strict logical process. First, the installation file is uploaded into the central repository. Next, administrators tag the image as 'Golden' for the targeted switch family to establish compliance baseline. Then, distribution transfers the binary onto the managed switch's local storage. Pre-checks validate storage capacity and configuration state prior to disruption. Finally, activation updates boot parameters, reloads the node into the new release, and executes post-checks to confirm full network recovery.

Step-by-Step Solution

1
Add the installation binary to the system repository
The target Cisco IOS XE image is stored in Cisco DNA Center Image Repository
Cisco DNA Center cannot manage, evaluate compliance for, or deploy an image that has not been imported into its local repository.
2
Set the Golden Image compliance standard
The image is marked as Golden for the selected device family
Marking an image as Golden defines the standardized baseline operating system version for all devices assigned to that family/role.
3
Distribute the software image to target switches
The image binary file is transferred to local flash memory on the switches
Distribution moves the image onto the device storage in advance so that activation can take place swiftly during a designated maintenance window.
4
Run Pre-upgrade check validations
System checks confirm sufficient disk space, configuration compatibility, and stack stability
Pre-checks prevent failed upgrades by identifying potential issues (such as insufficient flash storage or corrupt configuration statements) before the reboot sequence starts.
5
Activate the image and run Post-checks
Boot configuration is modified, device reboots, and Post-checks confirm healthy status
Activation updates the startup system boot statements and reboots the switch to complete the upgrade, followed by post-check verification to validate operational health.

Key Concept

Cisco DNA Center Software Image Management (SWIM) Workflow
Question 19Question →

An organization transitions its enterprise infrastructure to an automated network management framework utilizing programmatic RESTful APIs and declarative configuration templates. During a routine security audit, network engineers observe that out-of-band configuration changes manually made directly on individual switch command-line interfaces are automatically reverted to the intended state within minutes. Additionally, real-time interface statistics are continuously transmitted to a central analytics engine without requiring polling requests. Which statement accurately describes the core operational impact of this automation model on enterprise network management?

Show answer & explanation

Answer: It enforces a single source of truth to eliminate configuration drift across managed nodes while providing continuous, low-overhead operational visibility through push-based telemetry.

Answer

It enforces a single source of truth to eliminate configuration drift across managed nodes while providing continuous, low-overhead operational visibility through push-based telemetry.
Automated network management shifts operational workflows from per-device manual CLI administration to centralized, code-driven orchestration. Storing device configurations in declarative code repositories establishes a single source of truth, enabling automated controllers to detect and override out-of-band configuration drift. Furthermore, replacing pull-based SNMP requests with push-based streaming telemetry provides granular, real-time operational metrics with lower CPU overhead.

Step-by-Step Solution

1
Analyze the impact of declarative automation models on device state.
Declarative automation uses a central repository (version control) as the single source of truth, continuously detecting and reconciling out-of-band CLI changes (configuration drift).
Centralized automation enforces consistency and compliance across the fleet automatically.
2
Evaluate the telemetry mechanism described in the scenario.
Real-time continuous transmission of metrics to an analytics engine without polling describes push-based streaming telemetry.
Streaming telemetry reduces CPU overhead and provides near-real-time operational visibility compared to legacy SNMP polling.
3
Synthesize the operational impact on network management.
Combining drift mitigation via a single source of truth with real-time push telemetry represents the primary operational shift from traditional per-device manual CLI operations to automated management.
This alignment satisfies both operational consistency and modern telemetry requirements.

Key Concept

Impact of Automation on Network Management (Single Source of Truth, Drift Mitigation, and Streaming Telemetry)
Question 20Question →

Which Cisco DNA Center feature continuously collects telemetry data from network devices and clients to generate health scores and provide proactive troubleshooting insights?

Show answer & explanation

Answer: Cisco DNA Center Assurance

Answer

Cisco DNA Center Assurance is the core component that aggregates telemetry data to provide health scores and proactive diagnostics for network devices and clients.
Cisco DNA Center Assurance synthesizes streaming telemetry data to evaluate network performance, calculate health scores, and deliver proactive troubleshooting guidance.

Step-by-Step Solution

1
Analyze the functional requirement presented in the question.
The requirement asks for the Cisco DNA Center subsystem responsible for continuous telemetry collection and health score generation.
Identifying the functional domain distinguishes operational monitoring tools from deployment or provisioning tools.
2
Match the functional requirement with the appropriate Cisco DNA Center pillar.
Assurance is specifically designed to collect network telemetry and render global health scores ranging from 1 to 10 for network elements and client devices.
Assurance provides complete network visibility and predictive analytics.

Key Concept

Cisco DNA Center Assurance and Telemetry
Page 1 / 10Next
Automation and Programmability Practice Questions — Cisco CCNA | Examkin