350-401 · topic practice
Practise ENCOR 350-401 Rest Apis And Data Models 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
Rest Apis And Data Models 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 steps to the numbered slots on the right, or tap a step then tap a slot.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
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.
Retrieve a resource
Create a new resource
Replace an existing resource entirely
Remove a resource
Apply partial modifications to a resource
Trap 1: YAML files in Python cannot contain comments, so all inventory data…
Incorrect because YAML supports comments using the '#' character, and Python's PyYAML library can parse files that include comments (though comments are not preserved when dumping).
Trap 2: JSON is always more human-readable than YAML for complex inventory…
Incorrect because YAML is often considered more human-readable due to its use of indentation and less verbose syntax; JSON can be harder to read for deeply nested structures.
A Python script can read a YAML file containing device hostnames and IP addresses, then use that data to connect to each device and gather inventory information.
Correct because this is a common pattern: use PyYAML to load a YAML inventory file, iterate over devices, and use Netmiko or NAPALM to collect facts.
The json module in Python can be used to serialize a dictionary containing device inventory data into a JSON string for storage or transmission.
Correct because Python's built-in json module provides json.dumps() to convert Python objects (like dicts) into JSON strings, which is useful for saving inventory data or sending it to other systems.
CSV files can be parsed using Python's csv module to import device inventory data, such as hostname, IP, and credentials, into a script.
Correct because the csv module allows reading and writing CSV files, which are commonly used for inventory lists in network automation.
YAML files in Python cannot contain comments, so all inventory data must be described without explanatory text.
Why wrong: Incorrect because YAML supports comments using the '#' character, and Python's PyYAML library can parse files that include comments (though comments are not preserved when dumping).
JSON is always more human-readable than YAML for complex inventory structures.
Why wrong: Incorrect because YAML is often considered more human-readable due to its use of indentation and less verbose syntax; JSON can be harder to read for deeply nested structures.
Drag a concept onto its matching description — or click a concept then click the description.
Device hostname, vendor, model, OS version, serial number
Interface name, description, IP address, status, speed
BGP neighbor IP, remote AS, state, uptime
LLDP neighbor device ID, port ID, platform
Power supply, fan, temperature status
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.
Trap 1: Tuples are commonly used to store device credentials because they…
Incorrect because tuples are immutable; they cannot be modified after creation, making them unsuitable for dynamic credential storage.
Trap 2: Sets are ordered and allow indexing to retrieve specific elements.
Incorrect because sets are unordered and do not support indexing; they are used for unique elements and set operations.
Trap 3: Strings are mutable and ideal for storing multiple device…
Incorrect because strings are immutable in Python and are not designed to hold multiple separate values; they are single sequences of characters.
Tuples are commonly used to store device credentials because they can be modified easily.
Why wrong: Incorrect because tuples are immutable; they cannot be modified after creation, making them unsuitable for dynamic credential storage.
Dictionaries are used to store key-value pairs such as device IP, username, and password.
Correct because dictionaries map keys to values, which is perfect for storing device parameters like IP, username, and password.
Sets are ordered and allow indexing to retrieve specific elements.
Why wrong: Incorrect because sets are unordered and do not support indexing; they are used for unique elements and set operations.
Lists are ordered and can be used to store multiple device names for iteration.
Correct because lists maintain order and allow iteration, making them suitable for storing a list of device names or IPs.
Strings are mutable and ideal for storing multiple device configurations.
Why wrong: Incorrect because strings are immutable in Python and are not designed to hold multiple separate values; they are single sequences of characters.
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.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Trap 1: gNMI telemetry subscriptions can only use YANG paths from…
Incorrect because gNMI can use any YANG model path—native, OpenConfig, or IETF—as long as the device supports it.
Trap 2: gNMI relies on NETCONF for session establishment and data encoding.
Incorrect because gNMI is independent of NETCONF; it uses gRPC (HTTP/2) for transport and Protocol Buffers for encoding, not NETCONF's XML-based encoding.
gRPC uses HTTP/2 as its transport protocol and Protocol Buffers as its interface definition language.
Correct because gRPC is built on HTTP/2 for multiplexed, low-latency communication and uses Protocol Buffers for serialization and service definition.
gNMI (gRPC Network Management Interface) is a gRPC-based protocol that can be used for both telemetry and configuration operations.
Correct because gNMI defines RPCs for Subscribe (telemetry), Get, Set, and Capabilities, making it suitable for both monitoring and configuration.
gNMI telemetry subscriptions can only use YANG paths from OpenConfig models.
Why wrong: Incorrect because gNMI can use any YANG model path—native, OpenConfig, or IETF—as long as the device supports it.
gNMI relies on NETCONF for session establishment and data encoding.
Why wrong: Incorrect because gNMI is independent of NETCONF; it uses gRPC (HTTP/2) for transport and Protocol Buffers for encoding, not NETCONF's XML-based encoding.
gNMI supports both periodic and on-change telemetry subscriptions.
Correct because gNMI's Subscribe RPC allows specifying a subscription mode of SAMPLE (periodic) or ON_CHANGE.
Trap 1: IP Source Guard filters traffic based on the source MAC address.
Incorrect because IPSG filters based on source IP address, not MAC address. MAC filtering is done by port security.
Trap 2: IP Source Guard is applied on Layer 3 interfaces of a switch.
Incorrect because IPSG is configured on Layer 2 access ports, not on Layer 3 routed interfaces.
Trap 3: IP Source Guard requires 802.1X authentication to function.
Incorrect because IPSG can operate with DHCP snooping alone and does not require 802.1X.
IP Source Guard uses the DHCP snooping binding database to validate source IP addresses.
Correct because IPSG relies on the DHCP snooping binding database to determine which source IP addresses are allowed on a given port.
IP Source Guard filters traffic based on the source MAC address.
Why wrong: Incorrect because IPSG filters based on source IP address, not MAC address. MAC filtering is done by port security.
IP Source Guard is applied on Layer 3 interfaces of a switch.
Why wrong: Incorrect because IPSG is configured on Layer 2 access ports, not on Layer 3 routed interfaces.
IP Source Guard can be configured with a static IP source binding for hosts with static IP addresses.
Correct because administrators can manually configure 'ip source binding' entries for devices that do not use DHCP.
IP Source Guard requires 802.1X authentication to function.
Why wrong: Incorrect because IPSG can operate with DHCP snooping alone and does not require 802.1X.
Trap 1: Native YANG models are standardized by the IETF and used…
Incorrect because native models are vendor-specific, not IETF standards.
Trap 2: NETCONF is a YANG data model used for telemetry configuration.
Incorrect because NETCONF is a protocol that uses YANG, not a data model itself.
Trap 3: RESTCONF provides a YANG-based data model for streaming telemetry.
Incorrect because RESTCONF is a RESTful protocol for YANG-driven APIs, not a data model.
YANG models are used to define the data structures streamed in telemetry subscriptions.
Correct because YANG provides the schema for telemetry data, ensuring consistent encoding.
OpenConfig YANG models are vendor-neutral and supported across multiple network operating systems.
Correct because OpenConfig is an industry effort to create standard, vendor-agnostic models.
Native YANG models are standardized by the IETF and used universally.
Why wrong: Incorrect because native models are vendor-specific, not IETF standards.
NETCONF is a YANG data model used for telemetry configuration.
Why wrong: Incorrect because NETCONF is a protocol that uses YANG, not a data model itself.
RESTCONF provides a YANG-based data model for streaming telemetry.
Why wrong: Incorrect because RESTCONF is a RESTful protocol for YANG-driven APIs, not a data model.
Trap 1: RESTCONF uses SSH for transport security.
Incorrect because RESTCONF uses HTTP/HTTPS, not SSH.
Trap 2: RESTCONF is designed to replace NETCONF entirely.
Incorrect because RESTCONF and NETCONF are complementary, not a replacement.
Trap 3: RESTCONF uses remote procedure calls (RPCs) for all operations.
Incorrect because RESTCONF uses RESTful operations, not RPCs.
RESTCONF uses SSH for transport security.
Why wrong: Incorrect because RESTCONF uses HTTP/HTTPS, not SSH.
RESTCONF uses HTTP methods such as GET, PUT, POST, DELETE, and PATCH.
Correct because RESTCONF maps to standard HTTP methods.
RESTCONF is designed to replace NETCONF entirely.
Why wrong: Incorrect because RESTCONF and NETCONF are complementary, not a replacement.
RESTCONF supports both JSON and XML encoding for data representation.
Correct because RESTCONF can use JSON or XML.
RESTCONF uses remote procedure calls (RPCs) for all operations.
Why wrong: Incorrect because RESTCONF uses RESTful operations, not RPCs.
Trap 1: YANG models are written in XML syntax.
Incorrect because YANG uses its own syntax, not XML.
Trap 2: YANG modules are compiled into MIB files for SNMP.
Incorrect because YANG is not compiled into MIBs; MIBs are for SNMP.
YANG is used to define data models for NETCONF and RESTCONF.
Correct because YANG is the standard data modeling language for NETCONF and RESTCONF.
YANG models are written in XML syntax.
Why wrong: Incorrect because YANG uses its own syntax, not XML.
YANG supports hierarchical data structures using containers and lists.
Correct because YANG uses containers and lists to organize data hierarchically.
YANG modules are compiled into MIB files for SNMP.
Why wrong: Incorrect because YANG is not compiled into MIBs; MIBs are for SNMP.
YANG includes built-in data types such as string, int32, and enumeration.
Correct because YANG provides a set of built-in data types.
Free account
Create a free account to save your results and see which topics improve across sessions.
Focused Rest Apis And Data Models sessions
Every question in these sessions is drawn from the Rest Apis And Data Models 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