When Does Cisco DNA Center Apply Device Configurations?

When does Cisco DNA Center make changes to a device?

when the device credentials are added
when the network device is assigned to the site and device controllability is turned on Source Reference Answer
when the network device is discovered and device controllability is turned on
when a NETCONF port has been configured

Community Votes

82%

18%

82% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.

Community Insight

The question tests the distinction between passive inventory gathering and active configuration management, highlighting that DNA Center requires both site assignment and enabled device controllability to execute automated policy pushes.

This question identifies the precise trigger for configuration deployment in Cisco DNA Center. Community consensus confirms that changes are applied when a device is explicitly assigned to a site with device controllability enabled, rather than during initial discovery.

Candidates frequently choose Option C, incorrectly assuming that device discovery automatically triggers configuration changes. In reality, discovery only collects inventory and telemetry data; actual configuration modifications require explicit site assignment to apply baseline profiles and policies.

Community Discussion (9 comments)

Mekai2020 👍 12 Selected: B

When assigning devices to a site, if Device Controllability is enabled, a workflow is automatically triggered to push the device configuration from the site to the devices. https://www.cisco.com/c/en/us/td/docs/cloud-systems-management/network-automation-and-management/dna-center/2-2-2/user_guide/b_cisco_dna_center_ug_2_2_2/b_cisco_dna_center_ug_2_2_2_chapter_011.html

Shri_Fcb10 👍 1 Selected: C

https://community.cisco.com/t5/cisco-catalyst-center/network-devices-not-respond-to-dnac-configuration/td-p/4069080

Rfvaz 👍 1 Selected: B

B is ok

EAC84 👍 1 Selected: C

https://www.ciscolive.com/c/dam/r/ciscolive/apjc/docs/2020/pdf/BRKCRS-2637.pdf ^^^^ Page 21 ^^^^ Technically when DNAC discovers a new network device, it will apply the following. • PKI • IPDT • HTTP Server source • SNMP RO & RW communities • (If not already configured)

supershysherlock 👍 2 Selected: B

B. when the network device is assigned to the site and device controllability is turned on Cisco DNA Center uses a concept of 'site-based design' where devices are associated with specific sites, and profiles/policies can be applied based on site designation. Device controllability refers to the feature in Cisco DNA Center that enables it to send configuration commands to the device. Once a device is assigned to a site and this feature is enabled, Cisco DNA Center can push configuration changes to the device as per the assigned policies and profiles.

slacker_at_work 👍 2 Selected: B

Option B; Cisco DNA Center discover network devices when they are added to the network, but it doesn't necessarily make changes to the device at that moment. Changes are typically made after the device is assigned to a site and device controllability is enabled.

COLONEL_MAJOR 👍 1

i guess its c { A Note on Device Controllability Its purpose is to aid in deploying the required network settings that Cisco DNA Center needs to manage devices. Changes are made on network devices during discovery, when adding a device to Inventory, or when assigning a device to a site }

teems5uk 👍 1 Selected: C

C is correct

Mizuchan 👍 1 Selected: C

https://www.cisco.com/c/en/us/td/docs/cloud-systems-management/network-automation-and-management/dna-center/2-2-2/admin_guide/b_cisco_dna_center_admin_guide_2_2_2/b_cisco_dna_center_admin_guide_2_2_2_chapter_010.html#id_53799 Device controllability is a system-level process on Cisco DNA Center that enforces state synchronization for some device-layer features. Its purpose is to aid in the deployment of network settings that Cisco DNA Center needs to manage devices. Changes are made on network devices when running discovery, when adding a device to inventory, or when assigning a device to a site.

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Expert Analysis

Core Concept: DNA Center Device Lifecycle

Cisco DNA Center (now Catalyst Center) operates on a site-based design model. When a network device is onboarded, the platform follows a strict sequence: discovery, inventory population, site assignment, and finally, configuration enforcement.

Why Option B is Correct

Configuration changes are pushed to a device specifically when it is assigned to a site and device controllability is enabled. Site assignment links the device to a specific location profile, which dictates the baseline templates, access control policies, and QoS settings it should receive. Enabling device controllability grants DNA Center permission to actively send configuration commands via NETCONF/SSH/SNMP. As noted by candidates referencing official documentation, this combination automatically triggers a workflow that synchronizes the device state with the assigned site profile.

Why Other Options Are Incorrect

Option A is incorrect because adding credentials only establishes authentication and connectivity for management; it does not initiate any configuration workflows.
Option C is a common trap. While discovery gathers device information and may perform minimal setup (like SNMP communities or PKI certificates), it does not apply full site-level policies. Without site assignment, DNA Center lacks the context to determine what configurations to push.
Option D is incorrect because configuring a NETCONF port only defines the communication transport mechanism. It does not act as a trigger for configuration deployment.

Exam Context

Understanding this workflow is critical for the 350-401 exam, as it reflects real-world automation practices where intentional site grouping precedes policy enforcement to prevent misconfiguration across the network.

Official Reference

Exam Strategy

Focus on memorizing the DNA Center device onboarding lifecycle: Discovery (Inventory) -> Site Assignment (Policy Context) -> Controllability Enabled (Config Push). Use this sequence to quickly eliminate distractors that suggest automatic changes during discovery or credential addition. Always look for the explicit trigger that links topology/site context with active management permissions.

Related Analysis

Practice All 350-401 Questions

Access 218 questions with complete answers and detailed explanations.

View Full 350-401 Practice Test →

← Back to 350-401 Study Guide