Drag and drop the steps of SD-WAN zero-touch provisioning (ZTP) flow into the correct order, from first to last.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
350-401 · topic practice
Practise ENCOR 350-401 Sd Access Architecture practice questions — original exam-style scenarios with answer choices, explanations, and analysis of common mistakes.
Courseiva uses original exam-style practice questions designed for learning and revision. The goal is to understand the concepts, recognise exam patterns, and improve through explanations — not memorise copied exam dumps.
What the exam tests
Sd Access Architecture questions test whether you can apply the concept in context, not just recognise a definition.
How the topic appears in realistic exam-style scenarios.
Which detail in the question changes the correct answer.
How to eliminate plausible but wrong options.
How to connect the question back to the wider exam objective.
Watch out for
Practice set
20 questions · select your answer, then reveal the explanation
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag a concept onto its matching description — or click a concept then click the description.
Applied to data traffic for SLA-based path selection
Applied to enable NetFlow-like traffic monitoring
Applied to modify forwarding, NAT, or QoS on data packets
Applied to OMP routes and TLOCs for route manipulation
Applied to define which VPNs are provisioned on a device
Drag a concept onto its matching description — or click a concept then click the description.
Predictable latency and SLA, private Layer 3 VPN
Low cost, best-effort, public IP addressing
Wireless backup, variable throughput, cellular network
High latency, global coverage, limited bandwidth
High bandwidth, low latency, metro-area Layer 2 connectivity
Trap 1: 30 seconds
Incorrect. 30 seconds is the default for NBMA networks.
Trap 2: 5 seconds
A 5-second hello interval is the default for OSPF on NBMA (Non-Broadcast Multi-Access) networks, not for Ethernet. On an Ethernet broadcast multi-access link, the default hello interval is 10 seconds. This option is tempting because 5 seconds is the default for OSPF point-to-point and NBMA interfaces, so it is correct for those specific network types, but the stem explicitly specifies an Ethernet link.
Trap 3: 40 seconds
Incorrect. 40 seconds is the default dead interval for Ethernet.
10 seconds
Correct. The default hello interval for Ethernet is 10 seconds.
30 seconds
Why wrong: Incorrect. 30 seconds is the default for NBMA networks.
5 seconds
Why wrong: A 5-second hello interval is the default for OSPF on NBMA (Non-Broadcast Multi-Access) networks, not for Ethernet. On an Ethernet broadcast multi-access link, the default hello interval is 10 seconds. This option is tempting because 5 seconds is the default for OSPF point-to-point and NBMA interfaces, so it is correct for those specific network types, but the stem explicitly specifies an Ethernet link.
40 seconds
Why wrong: Incorrect. 40 seconds is the default dead interval for Ethernet.
Trap 1: The vManage controller is the primary control plane component that…
Incorrect because vManage is the management plane (NMS), not a control plane; OMP sessions are between vSmart and edge devices.
Trap 2: vEdge and cEdge routers are both control plane devices that…
Incorrect because vEdge and cEdge are data plane devices; they do run OMP but are not control plane components.
Trap 3: The OMP protocol runs between vManage and vSmart to exchange…
Incorrect because OMP runs between vSmart and edge devices (vEdge/cEdge), not between vManage and vSmart.
The vSmart controller is responsible for distributing OMP routes and policies to all edge devices in the SD-WAN fabric.
Correct because vSmart is the centralized control plane that uses OMP to advertise routes and apply policies.
The vBond orchestrator is responsible for authenticating and onboarding vEdge and cEdge routers into the SD-WAN overlay.
Correct because vBond provides NAT traversal and initial authentication, and directs devices to vManage and vSmart.
The vManage controller is the primary control plane component that establishes OMP sessions with all edge routers.
Why wrong: Incorrect because vManage is the management plane (NMS), not a control plane; OMP sessions are between vSmart and edge devices.
vEdge and cEdge routers are both control plane devices that participate in OMP route exchange.
Why wrong: Incorrect because vEdge and cEdge are data plane devices; they do run OMP but are not control plane components.
The OMP protocol runs between vManage and vSmart to exchange routing information and policy updates.
Why wrong: Incorrect because OMP runs between vSmart and edge devices (vEdge/cEdge), not between vManage and vSmart.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Trap 1: The vEdge routers have not been rebooted after the policy change.
Incorrect because policy changes take effect immediately without reboot.
Trap 2: The OMP graceful restart timer has expired, causing the vEdge to…
Incorrect because OMP graceful restart affects route convergence, not policy application.
Trap 3: The BFD sessions between vEdge and vSmart are flapping.
Incorrect because BFD is for data plane failure detection, not for policy distribution.
The vEdge routers have not been rebooted after the policy change.
Why wrong: Incorrect because policy changes take effect immediately without reboot.
The control policy is not attached to the appropriate site list or VPN list.
Correct because a control policy must be associated with a list to be applied; otherwise, it is not enforced.
The OMP graceful restart timer has expired, causing the vEdge to ignore the policy.
Why wrong: Incorrect because OMP graceful restart affects route convergence, not policy application.
The BFD sessions between vEdge and vSmart are flapping.
Why wrong: Incorrect because BFD is for data plane failure detection, not for policy distribution.
Trap 1: Type 1 hypervisors require a host OS for device drivers, while Type…
Type 1 hypervisors have their own drivers; Type 2 rely on the host OS.
Trap 2: Type 2 hypervisors are always more secure than Type 1 because of…
The additional OS layer increases attack surface, reducing security.
Trap 3: Type 1 hypervisors cannot support hardware passthrough, but Type 2…
Both types can support hardware passthrough; Type 1 typically does it more efficiently.
Type 1 hypervisors run directly on the physical hardware, while Type 2 hypervisors run on top of a host operating system.
This is the fundamental architectural difference.
Type 1 hypervisors require a host OS for device drivers, while Type 2 hypervisors include their own drivers.
Why wrong: Type 1 hypervisors have their own drivers; Type 2 rely on the host OS.
Type 2 hypervisors are always more secure than Type 1 because of the additional OS layer.
Why wrong: The additional OS layer increases attack surface, reducing security.
Type 1 hypervisors cannot support hardware passthrough, but Type 2 can.
Why wrong: Both types can support hardware passthrough; Type 1 typically does it more efficiently.
Drag a concept onto its matching description — or click a concept then click the description.
Generates the Network LSA and maintains full adjacencies with all routers on the segment
Monitors the DR and assumes the DR role if the DR fails
Forms full adjacencies only with the DR and BDR
Connects multiple areas and advertises inter-area routes
Redistributes external routes into OSPF
Trap 1: RESTCONF supports only XML encoding for data.
Incorrect because RESTCONF supports both XML and JSON encoding.
Trap 2: RESTCONF uses SSH as the transport protocol.
Incorrect because RESTCONF uses HTTP/HTTPS, not SSH; NETCONF uses SSH.
Trap 3: RESTCONF defines its own data modeling language.
Incorrect because RESTCONF uses YANG as the data modeling language.
RESTCONF uses HTTP methods like GET, PUT, POST, and DELETE to manipulate YANG data.
Correct because RESTCONF maps HTTP methods to CRUD operations on YANG data.
RESTCONF supports only XML encoding for data.
Why wrong: Incorrect because RESTCONF supports both XML and JSON encoding.
RESTCONF uses SSH as the transport protocol.
Why wrong: Incorrect because RESTCONF uses HTTP/HTTPS, not SSH; NETCONF uses SSH.
RESTCONF provides a 'data' resource as the entry point for accessing YANG data stores.
Correct because the base URI for RESTCONF includes the 'data' resource to access configuration and state data.
RESTCONF defines its own data modeling language.
Why wrong: Incorrect because RESTCONF uses YANG as the data modeling language.
Trap 1: CoS 5, DSCP AF41
AF41 is used for video, not voice.
Trap 2: CoS 5, DSCP CS3
CS3 is lower priority than EF.
Trap 3: CoS 4, DSCP EF
CoS 4 is for video conferencing.
CoS 5, DSCP AF41
Why wrong: AF41 is used for video, not voice.
CoS 5, DSCP CS3
Why wrong: CS3 is lower priority than EF.
CoS 5, DSCP EF
CoS 5 and DSCP EF are the standard marks for voice.
CoS 4, DSCP EF
Why wrong: CoS 4 is for video conferencing.
Trap 1: Check if the syslog messages are in the correct format.
Incorrect because DNA Center accepts standard syslog formats; format issues would not prevent all messages from being received.
Trap 2: Ensure that the switch is in the Inventory and managed by DNA…
Incorrect because syslog collection does not require the device to be in Inventory; it is a separate function.
Trap 3: Restart the syslog collector service on DNA Center.
Incorrect because the collector is enabled, so restarting it is unlikely to resolve a connectivity issue.
Verify that the syslog port (UDP 514) is not blocked by a firewall or ACL.
Correct because syslog uses UDP 514, and if the port is blocked, messages will not reach DNA Center.
Check if the syslog messages are in the correct format.
Why wrong: Incorrect because DNA Center accepts standard syslog formats; format issues would not prevent all messages from being received.
Ensure that the switch is in the Inventory and managed by DNA Center.
Why wrong: Incorrect because syslog collection does not require the device to be in Inventory; it is a separate function.
Restart the syslog collector service on DNA Center.
Why wrong: Incorrect because the collector is enabled, so restarting it is unlikely to resolve a connectivity issue.
Trap 1: The switch has not been discovered by DNA Center
The switch is in 'Managed' status, so it has been discovered.
Trap 2: The switch is not in Plug and Play mode
Plug and Play is used for initial provisioning, not post-discovery.
Trap 3: The switch does not have a valid DNA license
Licensing issues would cause different symptoms.
The switch has not been discovered by DNA Center
Why wrong: The switch is in 'Managed' status, so it has been discovered.
The switch is not in Plug and Play mode
Why wrong: Plug and Play is used for initial provisioning, not post-discovery.
The switch does not have a valid DNA license
Why wrong: Licensing issues would cause different symptoms.
The switch is not assigned to a site
Site assignment is required for template application.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Trap 1: Fabric border node
The border node connects the fabric to external networks but does not enforce SGT policies at the access layer.
Trap 2: Fabric control plane node
The control plane node maintains the LISP mapping database but does not enforce SGT policies.
Trap 3: Wireless LAN controller
The WLC may assign SGTs to wireless clients, but the enforcement of SGT policies occurs at the fabric edge switch.
Fabric border node
Why wrong: The border node connects the fabric to external networks but does not enforce SGT policies at the access layer.
Fabric control plane node
Why wrong: The control plane node maintains the LISP mapping database but does not enforce SGT policies.
Fabric edge node
The fabric edge switch enforces SGT-based policies by applying SGACLs based on the SGT assigned by ISE during authentication.
Wireless LAN controller
Why wrong: The WLC may assign SGTs to wireless clients, but the enforcement of SGT policies occurs at the fabric edge switch.
A network engineer is using the Cisco DNA Center REST API to retrieve the health score of a specific device. The API response is as follows:
{
"response": [
{
"deviceId": "1234567890",
"hostname": "Core-Switch-1",
"score": 8,
"overallHealth": "good",
"timestamp": 1623456789
}
],
"version": "1.0"
}The engineer wants to extract the 'overallHealth' value. Which Python code correctly extracts it?
Trap 1: health = response['overallHealth']
This would fail because 'overallHealth' is not a top-level key.
Trap 2: health = response['response']['overallHealth']
This would fail because 'response' contains a list, not a dictionary.
Trap 3: health = response[0]['overallHealth']
This would fail because the top-level object is a dictionary, not a list.
health = response['response'][0]['overallHealth']
Correct. This accesses the first element of the list inside 'response' and then retrieves 'overallHealth'.
health = response['overallHealth']
Why wrong: This would fail because 'overallHealth' is not a top-level key.
health = response['response']['overallHealth']
Why wrong: This would fail because 'response' contains a list, not a dictionary.
health = response[0]['overallHealth']
Why wrong: This would fail because the top-level object is a dictionary, not a list.
Trap 1: RESTCONF
RESTCONF is a protocol for model-driven APIs, not for CLI-based backup.
Trap 2: Ansible
Ansible is a configuration management tool, not a Python library.
Trap 3: Netmiko
Netmiko is a high-level library built on Paramiko, but Paramiko is the underlying SSH implementation.
RESTCONF
Why wrong: RESTCONF is a protocol for model-driven APIs, not for CLI-based backup.
Ansible
Why wrong: Ansible is a configuration management tool, not a Python library.
Paramiko
Paramiko provides SSH connectivity to network devices.
Netmiko
Why wrong: Netmiko is a high-level library built on Paramiko, but Paramiko is the underlying SSH implementation.
Trap 1: Implement PIM-SM for multicast routing in the underlay.
Multicast is not required for the underlay; the overlay handles group communication.
Trap 2: Preserve existing VLANs across the fabric to minimize changes.
The underlay should be IP routed; VLANs are not used in the underlay.
Trap 3: Deploy VRF-lite on all edge nodes to isolate tenants.
VRF-lite is not a requirement; the overlay provides segmentation.
Configure a routed access layer with a link-state routing protocol (IS-IS or OSPF).
A routed underlay with IS-IS or OSPF is a key design requirement for SD-Access.
Implement PIM-SM for multicast routing in the underlay.
Why wrong: Multicast is not required for the underlay; the overlay handles group communication.
Preserve existing VLANs across the fabric to minimize changes.
Why wrong: The underlay should be IP routed; VLANs are not used in the underlay.
Deploy VRF-lite on all edge nodes to isolate tenants.
Why wrong: VRF-lite is not a requirement; the overlay provides segmentation.
Trap 1: The trunk is not allowing VLAN 20 or VLAN 30.
Incorrect because the engineer verified the trunk allows both VLANs.
Trap 2: Spanning Tree Protocol is blocking the SVI interfaces.
Incorrect because SVIs are logical interfaces and are not affected by STP.
Trap 3: The native VLAN mismatch on the trunk is causing the issue.
Incorrect because the trunk is up, so native VLAN mismatch is not present.
The hosts are not configured with the correct default gateway pointing to the SVI on the distribution switch.
Correct because hosts need a default gateway to route traffic to other VLANs; if misconfigured, inter-VLAN communication fails.
The trunk is not allowing VLAN 20 or VLAN 30.
Why wrong: Incorrect because the engineer verified the trunk allows both VLANs.
Spanning Tree Protocol is blocking the SVI interfaces.
Why wrong: Incorrect because SVIs are logical interfaces and are not affected by STP.
The native VLAN mismatch on the trunk is causing the issue.
Why wrong: Incorrect because the trunk is up, so native VLAN mismatch is not present.
Trap 1: Enable hyper-threading and overcommit CPU resources
Overcommitting CPU resources increases contention and latency, which is unsuitable for latency-sensitive workloads.
Trap 2: Use a Type 2 hypervisor (e.g., VMware Workstation) for better…
Type 2 hypervisors run on top of an OS, adding overhead; Type 1 is preferred for performance in data centers.
Trap 3: Enable memory ballooning to reclaim unused memory from VMs
Memory ballooning can cause performance variability and is not suitable for latency-sensitive workloads.
Enable hyper-threading and overcommit CPU resources
Why wrong: Overcommitting CPU resources increases contention and latency, which is unsuitable for latency-sensitive workloads.
Use a Type 2 hypervisor (e.g., VMware Workstation) for better isolation
Why wrong: Type 2 hypervisors run on top of an OS, adding overhead; Type 1 is preferred for performance in data centers.
Configure NUMA pinning and CPU pinning for each VM to dedicated cores and memory nodes
NUMA pinning and CPU pinning reduce latency by ensuring VMs use local memory and dedicated cores, avoiding hypervisor scheduling delays.
Enable memory ballooning to reclaim unused memory from VMs
Why wrong: Memory ballooning can cause performance variability and is not suitable for latency-sensitive workloads.
Free account
Create a free account to save your results and see which topics improve across sessions.
Focused Sd Access Architecture sessions
Every question in these sessions is drawn from the Sd Access Architecture domain — nothing else.
Related practice questions
Move into related areas when this topic feels solid.
Sharpen your 350-401 knowledge of Architecture.
Practise 350-401 questions linked to Virtualization.
Work through 350-401 questions on Infrastructure.
Sharpen your 350-401 knowledge of Network Assurance.
Security practice questions for 350-401.
Targeted 350-401 practice covering Automation.
Practise eBGP/iBGP peering, path attributes, route selection and BGP troubleshooting.
Practise OSPF area types, LSA types, neighbour states and multi-area design.
Practise EIGRP DUAL, metrics, stub routing and route redistribution.
Practise VLAN configuration, trunk negotiation and inter-VLAN routing.
Practise RSTP, MSTP, port roles and STP protection features.
Practise extended ACLs, CoPP rate-limiting and control-plane protection.
A free account saves results across sessions and highlights which topics need work.
Sign up free