Look at Figure 1. PC1 reaches PC3 across an SD-Access fabric.
Every switch on the path is configured.
But one question stays open.Who Configured the Fabric?
You never opened a CLI session.
You never typed a single command on a Fabric Edge.
So who configured all of this?
Figure 1 – The fabric works, but nobody typed a command
The Orchestrator
It is Cisco Catalyst Center, the controller that configures and monitors the whole fabric.

Figure 2 – Catalyst Center orchestrates every fabric device
One admin, one dashboard, pushing config down to every device.
No SSH session opened by hand.Catalyst Center also manages traditional non-fabric campuses even without SD-Access.
Note: Cisco DNA Center was renamed Cisco Catalyst Center in 2023.
The exam still uses both interchangeably.Answer the question below
What is the former name of Cisco Catalyst Center?
Answer the question below
Does Catalyst Center only manage SD-Access fabric networks?
Every action you take in Catalyst Center falls into one of four workflows.

Figure 3 – The four workflows
Design — describe the network on paper
Policy — decide who talks to whom
Provision — push the config to the devices
Assurance — watch how it behaves
Design — Describe the Network
Design is where you describe your network before touching any device.
You build a site hierarchy (Area > Building > Floor).You assign IP pools.
You set AAA servers, NTP, DNS, and SNMP for each site.

Figure 4 – A switch added to Floor 3 inherits its settings
The hierarchy is structured by location, not by role.
A device inherits the settings of the site it belongs to.Beyond the hierarchy, Design ships with the Template Editor.
One template, many devices, different values per site.Answer the question below
Under which Catalyst Center workflow do you create the site hierarchy?
Policy — Decide Who Talks to Whom
Policy is where you decide who can reach what.
You define group-based rules:Employees → data center
Contractors → Internet only
Guests → captive portal only
These groups are the Scalable Group Tags (SGT) used by SD-Access.

Figure 5 – Each group gets its own SGT and destinations
Catalyst Center integrates with Cisco ISE to assign users to groups dynamically.
802.1X authenticates, ISE returns the SGT, the Edge applies it.Answer the question below
Which external system does Catalyst Center rely on to assign users to groups dynamically?
Provision — Push the Config
Provision is where the configuration actually reaches the device.
Before that can happen, three things must be in place:IP connectivity between Catalyst Center and the device
Valid credentials (SSH or Telnet, plus SNMP) so Catalyst Center can log in and read the device
The device added to the inventory through Discovery
Catalyst Center also gives you the SWIM service (Software Image Management) to store device images and define a golden image per device family. SWIM is not a prerequisite, but you'll use it often to keep your fleet on the same version.
Answer the question below
Which Catalyst Center service holds the device images used for upgrades?
Even with everything in place, the device goes through four stages: three to prepare, one to push.
Stage 1 — Discovery
You give Catalyst Center an IP range to scan.
It uses CDP and LLDP to find the devices, then reads their inventory with SNMP. The credentials you provided (SSH or Telnet) let it log in if needed.
Figure 6 – Stage 1: device discovered
Result so far: zero lines of config written.
Answer the question below
After discovery alone, does Catalyst Center push configuration to a device?
Stage 2 — Site Assignment
You drag the switch into a site from the hierarchy you built during Design.

Figure 7 – Stage 2: device placed in the hierarchy
Now Catalyst Center knows which settings should apply: AAA servers, NTP, IP pools, VLANs, all defined at the site level.
But still no config is pushed.Answer the question below
After site assignment, does Catalyst Center push configuration yet?
Stage 3 — Device Controllability
Before any config flows, you need to check one setting: device controllability.
It is your explicit permission for Catalyst Center to write to that device. It is on by default, but you can disable it per site or per device.
Figure 8 – Stage 3: controllability authorizes the writes
When ON (default): the device receives configuration when you provision it.
When OFF: Catalyst Center reads telemetry and shows health scores, but never writes.
Think of device controllability as the master valve on a water main.
The pipes can be installed and the pumps powered on. Until you open the valve, nothing flows.Answer the question below
What setting must be turned on to give Catalyst Center permission to write to a device?
Stage 4 — Push
Catalyst Center pushes the configuration.

Figure 9 – Stage 4: configuration flows down
VLANs, IP pools, AAA, NTP, and any template you defined in Design reach the device.
The switch goes from ready to receive to fully configured.Answer the question below
At which stage does Catalyst Center actually deploy configuration to the device?
Answer the question below
How many stages does the Catalyst Center provision sequence have?
Assurance — Watch It Run
Design, Policy and Provision configured the network.
Assurance watches it run.Catalyst Center collects telemetry from every device.
It turns the raw data into health scores for the network, the clients, and the applications.The main Assurance tool is Path Trace.
You give it a source and a destination.
Catalyst Center walks the topology hop by hop and flags any ACL or QoS policy on the way.
Figure 10 – Path Trace flags the ACL on R2
Think of Path Trace as a
tracerouteyou never type.
Catalyst Center runs it on every device along the path at once.Answer the question below
Which Catalyst Center Assurance feature verifies host reachability hop by hop?
Assurance does not just monitor.
What it observes today feeds back into the next design.
Figure 11 – Assurance closes the loop back to Design
Answer the question below
SW1 and SW5 discovered in a site, SW2 with no site, SW3 bad SNMP, SW4 unreachable: how many are ready for Push?
On top of the four workflows, Cisco adds three AI features.
AI Endpoint Analytics — What Is This Device?
A new device connects to the network.
What is it?AI Endpoint Analytics inspects:
MAC OUI (vendor)
DHCP fingerprints
Traffic patterns and certificates
Then it classifies the device: corporate laptop, IP camera, printer, IoT thermostat, medical device.
The profile is fed back to ISE, which assigns the right SGT.Answer the question below
Which Catalyst Center AI feature classifies new endpoints by their behavior and fingerprints?
AI Network Analytics — What Is Normal?
Catalyst Center watches every site, every AP, every link.
Over time, it builds a baseline of what normal looks like for your network:Average Wi-Fi onboarding time
Average throughput per link
Average client count per AP
When something drifts, it raises an anomaly.
The threshold is learned from your traffic, not configured by hand.
Figure 12 – The baseline learns normal, flags every drift
On Sunday, onboarding time jumps to four times the baseline.
Catalyst Center flags it automatically.Answer the question below
What does AI Network Analytics use to detect anomalies on your network?
Machine Reasoning Engine — Why Is It Broken?
AI Network Analytics flagged the anomaly.
MRE finds the cause.The Machine Reasoning Engine (MRE) runs sequential checks across the topology to locate the failed component.

Figure 13 – MRE walks the topology and finds the root cause
MRE opens an Issue Details panel.
It tells you three things at once:Root Cause — WLC uplink saturated at 90%
Suggested Actions — add a redundant uplink, move APs to a backup WLC, review QoS
Impacted Clients — 47 users, average onboarding 12.3s vs 3s baseline
That panel alone already saves you the hour you'd usually spend chasing the cause across the CLI of every device.
To confirm the diagnosis, you hit Run Commands. Catalyst Center suggests the right
showcommands (uplink stats, interface counters, client count) and runs them on the device for you. You read the output directly in the panel, without opening a single SSH session.MRE hands you the root cause, the suggested fix, and the commands to confirm it, all in one place.
Answer the question below
Which Catalyst Center AI feature finds the root cause of a network issue?
Answer the question below
What is the primary role of Catalyst Center in a Cisco SD-Access deployment?