How should I use these REST APIs and Data Models practice questions?

Read each scenario carefully and choose your answer before revealing the explanation. Then check why your choice was right or wrong. Repeat until the reasoning feels automatic.

Can I practise just REST APIs and Data Models questions in a focused session?

Yes — use the session launcher on this page to start a 10-, 20-, 30- or 50-question session drawn entirely from the REST APIs and Data Models domain.

350-401 · topic practice

REST APIs and Data Models practice questions

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.

Reviewed byJohnson Ajibi· MSc IT Security

20 questionsDomain: REST APIs and Data Models

Practice 10 questions Browse domain →

What the exam tests

What to know about REST APIs and Data Models

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

Common REST APIs and Data Models exam traps

▸Answering from memory before reading the full scenario.
▸Missing a constraint such as cost, availability, security, scope or command context.
▸Choosing a broad answer when the question asks for the most specific fix.
▸Ignoring why the wrong options are tempting.

Practice set

REST APIs and Data Models questions

20 questions · select your answer, then reveal the explanation

Question 1mediummultiple choice

Open the full VLAN trunking answer →

A network engineer is automating the configuration of a new VLAN on a Cisco Catalyst 9000 switch using RESTCONF. The engineer sends a PUT request to the URI 'https://switch/restconf/data/Cisco-NX-OS-device:Native/VlanList' with a JSON payload containing the VLAN details. The switch responds with a 405 Method Not Allowed error. What is the most likely cause of this error?

Trap 1: The engineer used the wrong URI; the correct URI should include a…

Incorrect because the URI for creating a new list entry does not require a specific ID; the POST method is used to add an entry to the list.

Trap 2: The payload format is incorrect; the engineer must use XML instead…

Incorrect because RESTCONF supports both JSON and XML; the format is not the cause of a 405 error.

Trap 3: The switch does not support RESTCONF for VLAN configuration;…

Incorrect because Cisco Catalyst 9000 switches support RESTCONF for VLAN configuration; the error is method-related.

Study all REST APIs and Data Models common traps →

A
The engineer used the wrong URI; the correct URI should include a specific VLAN ID.
Why wrong: Incorrect because the URI for creating a new list entry does not require a specific ID; the POST method is used to add an entry to the list.
B
The engineer should have used the POST method instead of PUT to create a new list entry.
Correct because RESTCONF uses POST to create a new resource in a list, while PUT is used to replace an existing resource.
C
The payload format is incorrect; the engineer must use XML instead of JSON.
Why wrong: Incorrect because RESTCONF supports both JSON and XML; the format is not the cause of a 405 error.
D
The switch does not support RESTCONF for VLAN configuration; NETCONF must be used instead.
Why wrong: Incorrect because Cisco Catalyst 9000 switches support RESTCONF for VLAN configuration; the error is method-related.

Full breakdown with real-world context →

Question 2mediummultiple choice

Study the full Python automation breakdown →

An engineer is using a Python script to retrieve interface statistics from a Cisco IOS-XE device via the REST API. The script sends a GET request to 'https://device/restconf/data/ietf-interfaces:interfaces/interface=GigabitEthernet1/statistics' and receives a 404 Not Found response. The interface exists and is operational. What is the most likely issue?

Trap 1: The interface name must be URL-encoded because it contains a slash.

Incorrect because 'GigabitEthernet1' does not contain a slash; URL encoding is not the issue here.

Trap 2: The device requires authentication; the script must include a valid…

Incorrect because a 404 error indicates resource not found, not authentication failure (which would be 401).

Trap 3: The REST API is not enabled on the device; the engineer must enable…

Incorrect because if the API were not enabled, the response would likely be a connection error or 403, not 404.

Study all REST APIs and Data Models common traps →

A
The interface name must be URL-encoded because it contains a slash.
Why wrong: Incorrect because 'GigabitEthernet1' does not contain a slash; URL encoding is not the issue here.
B
The URI is incorrect; statistics are under 'interfaces-state' not 'interfaces'.
Correct because operational state data like statistics is in the 'interfaces-state' container, while 'interfaces' contains configuration data.
C
The device requires authentication; the script must include a valid token.
Why wrong: Incorrect because a 404 error indicates resource not found, not authentication failure (which would be 401).
D
The REST API is not enabled on the device; the engineer must enable it first.
Why wrong: Incorrect because if the API were not enabled, the response would likely be a connection error or 403, not 404.

Full breakdown with real-world context →

Question 3hardmultiple choice

Read the full Ansible explanation →

A network team is using Ansible with the iosxr_config module to push configuration changes to a Cisco IOS-XR router. The playbook uses the REST API via the 'ansible_connection: restconf' setting. The engineer notices that the changes are applied but the playbook reports 'changed: false' even when changes were made. What is the most likely reason for this behavior?

Trap 1: The REST API on the router does not return a proper response, so…

Incorrect because the REST API does return responses; the issue is with how Ansible is configured.

Trap 2: The playbook is missing the 'gather_facts: no' directive, causing…

Incorrect because gather_facts does not affect change detection for RESTCONF operations.

Trap 3: The router requires a commit operation after configuration changes,…

Incorrect because IOS-XR with RESTCONF may require commit, but the issue is the module choice, not the commit.

Study all REST APIs and Data Models common traps →

A
The REST API on the router does not return a proper response, so Ansible cannot determine if a change occurred.
Why wrong: Incorrect because the REST API does return responses; the issue is with how Ansible is configured.
B
The engineer should use the 'uri' module with the REST API instead of the 'iosxr_config' module.
Correct because 'iosxr_config' is for CLI-based connections; for RESTCONF, the 'uri' module or a dedicated RESTCONF module should be used.
C
The playbook is missing the 'gather_facts: no' directive, causing Ansible to skip change detection.
Why wrong: Incorrect because gather_facts does not affect change detection for RESTCONF operations.
D
The router requires a commit operation after configuration changes, and Ansible does not perform that.
Why wrong: Incorrect because IOS-XR with RESTCONF may require commit, but the issue is the module choice, not the commit.

Full breakdown with real-world context →

Question 4mediummultiple choice

Read the full REST/YANG explanation →

An engineer is developing a script to automate the backup of running configurations from multiple Cisco IOS-XE devices using RESTCONF. The script sends a GET request to 'https://device/restconf/data/Cisco-IOS-XE-native:native/configuration' and receives a 501 Not Implemented error. What is the most likely cause?

Trap 1: The device does not support RESTCONF; the engineer must use NETCONF…

Incorrect because IOS-XE supports RESTCONF; the error is specific to the URI.

Trap 2: The URI is incorrect; the running configuration is under…

Incorrect because that URI is for capabilities, not the running configuration.

Trap 3: The request must use the POST method instead of GET to retrieve the…

Incorrect because GET is the correct method to retrieve data; POST is for creating resources.

Study all REST APIs and Data Models common traps →

A
The device does not support RESTCONF; the engineer must use NETCONF for configuration backup.
Why wrong: Incorrect because IOS-XE supports RESTCONF; the error is specific to the URI.
B
The URI is incorrect; the running configuration is under 'ietf-netconf-monitoring:netconf-state/capabilities'.
Why wrong: Incorrect because that URI is for capabilities, not the running configuration.
C
The URI is incorrect; the running configuration is accessed via the 'Cisco-IOS-XE-native:native' module without the '/configuration' suffix.
Correct because the native model does not have a 'configuration' container; the correct URI is '/restconf/data/Cisco-IOS-XE-native:native'.
D
The request must use the POST method instead of GET to retrieve the running configuration.
Why wrong: Incorrect because GET is the correct method to retrieve data; POST is for creating resources.

Full breakdown with real-world context →

Question 5easymultiple choice

Read the full REST APIs and Data Models explanation →

A network engineer is using the Cisco DNA Center REST API to retrieve the list of network devices. The engineer sends a GET request to '/dna/intent/api/v1/network-device' and receives a 400 Bad Request response. The API documentation indicates that the request requires a query parameter 'siteId'. What should the engineer do to resolve the issue?

Trap 1: Change the HTTP method to POST because GET is not supported for…

Incorrect because the endpoint supports GET; the error is due to missing parameters.

Trap 2: Add an 'Authorization' header with a valid token because the API…

Incorrect because a missing authentication would result in a 401 error, not 400.

Trap 3: Use a different API endpoint, such as '/dna/intent/api/v1/site', to…

Incorrect because the correct endpoint for network devices is '/network-device'; the issue is the missing parameter.

Study all REST APIs and Data Models common traps →

A
Include the 'siteId' query parameter in the request URL.
Correct because the API requires the 'siteId' parameter to filter devices by site.
B
Change the HTTP method to POST because GET is not supported for this endpoint.
Why wrong: Incorrect because the endpoint supports GET; the error is due to missing parameters.
C
Add an 'Authorization' header with a valid token because the API requires authentication.
Why wrong: Incorrect because a missing authentication would result in a 401 error, not 400.
D
Use a different API endpoint, such as '/dna/intent/api/v1/site', to retrieve device information.
Why wrong: Incorrect because the correct endpoint for network devices is '/network-device'; the issue is the missing parameter.

Full breakdown with real-world context →

Question 6mediummultiple choice

Open the full VLAN trunking answer →

An engineer is using a Python script to configure a new VLAN on a Cisco Nexus 9000 switch using the NX-API REST API. The script sends a POST request to 'https://switch/api/mo/org.json' with a JSON payload containing the VLAN configuration. The switch responds with a 403 Forbidden error. What is the most likely cause?

Trap 1: The payload format is incorrect; the engineer must use XML instead…

Incorrect because NX-API supports both JSON and XML; format does not cause a 403 error.

Trap 2: The switch does not support NX-API; the engineer must use NETCONF…

Incorrect because Nexus 9000 supports NX-API; the error is authorization-related.

Trap 3: The URI is incorrect; the correct URI should be…

Incorrect because the URI '/api/mo/org.json' is correct for NX-API; a wrong URI would result in a 404 error.

Study all REST APIs and Data Models common traps →

A
The payload format is incorrect; the engineer must use XML instead of JSON.
Why wrong: Incorrect because NX-API supports both JSON and XML; format does not cause a 403 error.
B
The user account does not have the required RBAC privileges to configure VLANs.
Correct because 403 indicates authorization failure; the user needs appropriate privileges.
C
The switch does not support NX-API; the engineer must use NETCONF instead.
Why wrong: Incorrect because Nexus 9000 supports NX-API; the error is authorization-related.
D
The URI is incorrect; the correct URI should be 'https://switch/api/node/mo/org.json'.
Why wrong: Incorrect because the URI '/api/mo/org.json' is correct for NX-API; a wrong URI would result in a 404 error.

Full breakdown with real-world context →

Question 7easymultiple choice

Read the full wireless explanation →

A network engineer is using the Cisco Meraki REST API to update the SSID settings for a wireless network. The engineer sends a PUT request to 'https://api.meraki.com/api/v1/networks/{networkId}/wireless/ssids/{ssidNumber}' with a JSON payload containing the new settings. The API returns a 429 Too Many Requests error. What should the engineer do to resolve this issue?

Trap 1: Change the HTTP method to POST because PUT is not supported for…

Incorrect because PUT is the correct method for updating a resource; the error is rate limiting.

Trap 2: Add an 'X-Cisco-Meraki-API-Key' header with a higher rate limit key.

Incorrect because rate limits are per API key; there is no 'higher rate limit key'.

Trap 3: Use a different API endpoint, such as…

Incorrect because the endpoint is correct; the issue is request frequency.

Study all REST APIs and Data Models common traps →

A
Implement exponential backoff and retry the request after a delay.
Correct because rate limiting requires the client to slow down and retry after a delay.
B
Change the HTTP method to POST because PUT is not supported for this endpoint.
Why wrong: Incorrect because PUT is the correct method for updating a resource; the error is rate limiting.
C
Add an 'X-Cisco-Meraki-API-Key' header with a higher rate limit key.
Why wrong: Incorrect because rate limits are per API key; there is no 'higher rate limit key'.
D
Use a different API endpoint, such as 'https://api.meraki.com/api/v1/organizations/{orgId}/ssids'.
Why wrong: Incorrect because the endpoint is correct; the issue is request frequency.

Full breakdown with real-world context →

Question 8hardmultiple choice

Study the full SD-WAN breakdown →

An engineer is using the Cisco SD-WAN vManage REST API to retrieve the list of WAN edge devices. The engineer sends a GET request to 'https://vmanage/dataservice/device' and receives a 401 Unauthorized error. The engineer has already obtained a JSESSIONID cookie by authenticating with the API. What is the most likely cause of the error?

Trap 1: The engineer must use a different authentication method, such as…

Incorrect because vManage supports cookie-based authentication; the issue is that the cookie is not being sent.

Trap 2: The URI is incorrect; the correct URI should be…

Incorrect because the URI '/dataservice/device' is correct; a wrong URI would result in a 404 error.

Trap 3: The engineer must include a CSRF token in the request header for…

Incorrect because CSRF tokens are typically required for state-changing methods like POST, PUT, DELETE, not for GET.

Study all REST APIs and Data Models common traps →

A
The JSESSIONID cookie must be included in the request headers for authentication.
Correct because the session cookie must be sent with each request to maintain authentication.
B
The engineer must use a different authentication method, such as OAuth2, instead of cookies.
Why wrong: Incorrect because vManage supports cookie-based authentication; the issue is that the cookie is not being sent.
C
The URI is incorrect; the correct URI should be 'https://vmanage/dataservice/device/wanedge'.
Why wrong: Incorrect because the URI '/dataservice/device' is correct; a wrong URI would result in a 404 error.
D
The engineer must include a CSRF token in the request header for GET requests.
Why wrong: Incorrect because CSRF tokens are typically required for state-changing methods like POST, PUT, DELETE, not for GET.

Full breakdown with real-world context →

Question 9mediummultiple choice

Read the full REST/YANG explanation →

A network engineer is using the Cisco IOS-XE REST API to configure a static route. The engineer sends a PATCH request to 'https://device/restconf/data/Cisco-IOS-XE-native:native/ip/route/ip-route-interface-forwarding-list=192.168.1.0,255.255.255.0,GigabitEthernet1' with a JSON payload containing the route details. The device responds with a 204 No Content status. What does this response indicate?

Trap 1: The request failed because the route already exists; the engineer…

Incorrect because 204 indicates success, not failure; a conflict would return 409.

Trap 2: The device does not support PATCH; the engineer must use POST to…

Incorrect because PATCH is supported for partial updates; 204 indicates success.

Trap 3: The payload was empty; the engineer must include the route…

Incorrect because if the payload were empty, the request would likely fail with a 400 error.

Study all REST APIs and Data Models common traps →

A
The request was successful, and the static route has been configured.
Correct because 204 No Content indicates success with no response body; the route is configured.
B
The request failed because the route already exists; the engineer must use PUT instead.
Why wrong: Incorrect because 204 indicates success, not failure; a conflict would return 409.
C
The device does not support PATCH; the engineer must use POST to update the route.
Why wrong: Incorrect because PATCH is supported for partial updates; 204 indicates success.
D
The payload was empty; the engineer must include the route parameters in the body.
Why wrong: Incorrect because if the payload were empty, the request would likely fail with a 400 error.

Full breakdown with real-world context →

Question 10mediummultiple choice

Study the full Python automation breakdown →

A network engineer writes the following Python script using the Requests library to retrieve interface information from a Cisco IOS-XE device via RESTCONF:

```python

import requests
import json

url = "https://10.1.1.1:443/restconf/data/ietf-interfaces:interfaces" headers = {

"Accept": "application/yang-data+json",
    "Content-Type": "application/yang-data+json"
}

auth = ("admin", "password") response = requests.get(url, headers=headers, auth=auth, verify=False)

print(response.json())

```

What is the primary issue with this code?

Trap 1: The URL uses HTTPS but the device only supports HTTP, causing a…

RESTCONF typically uses HTTPS. This is not the issue.

Trap 2: The 'verify=False' parameter is not valid for the requests library;…

'verify' is a valid parameter in requests to disable SSL verification.

Trap 3: The 'auth' tuple should be passed as a dictionary with 'username'…

Requests accepts a tuple for basic auth.

Study all REST APIs and Data Models common traps →

A
The URL uses HTTPS but the device only supports HTTP, causing a connection error.
Why wrong: RESTCONF typically uses HTTPS. This is not the issue.
B
The 'Content-Type' header is misspelled as 'Contet-Type', which will cause the server to reject the request.
The header 'Contet-Type' is incorrect; it should be 'Content-Type'. This will cause the server to not recognize the media type.
C
The 'verify=False' parameter is not valid for the requests library; it should be 'ssl_verify=False'.
Why wrong: 'verify' is a valid parameter in requests to disable SSL verification.
D
The 'auth' tuple should be passed as a dictionary with 'username' and 'password' keys.
Why wrong: Requests accepts a tuple for basic auth.

Full breakdown with real-world context →

Question 11mediummultiple choice

Read the full Ansible explanation →

An engineer uses the following Ansible playbook to configure an interface on a Cisco IOS-XE device using the cisco.ios.ios_interfaces module:

```yaml --- - name: Configure interface hosts: cisco-routers gather_facts: no tasks: - name: Set interface description cisco.ios.ios_interfaces: config: - name: GigabitEthernet0/1 description: "Uplink to Core"

enabled: true

state: replaced ```

What is the result of running this playbook?

Trap 1: The interface will have the description set and all other…

The 'replaced' state replaces the entire interface configuration, not just the provided parameters.

Trap 2: The playbook will fail because 'enabled' is not a valid parameter…

'enabled' is a valid parameter in the cisco.ios.ios_interfaces module.

Trap 3: The playbook will fail because 'state: replaced' requires a…

'replaced' is a valid state that replaces the configuration with the provided one.

Study all REST APIs and Data Models common traps →

A
The interface will have the description set and all other parameters remain unchanged.
Why wrong: The 'replaced' state replaces the entire interface configuration, not just the provided parameters.
B
The playbook will fail because 'enabled' is not a valid parameter for ios_interfaces.
Why wrong: 'enabled' is a valid parameter in the cisco.ios.ios_interfaces module.
C
The interface will be configured with only the description and enabled state, removing any other existing configuration.
The 'replaced' state replaces the whole interface configuration with the provided values.
D
The playbook will fail because 'state: replaced' requires a 'before' and 'after' state.
Why wrong: 'replaced' is a valid state that replaces the configuration with the provided one.

Full breakdown with real-world context →

Question 12hardmultiple choice

Review the full routing breakdown →

A network engineer is using the Cisco DNA Center REST API to retrieve the list of devices. The API call returns the following JSON response:

```json

{
  "response": [
    {
      "id": "device-123",
      "hostname": "Router1",
      "managementIpAddress": "10.10.20.1",
      "softwareVersion": "17.3.3",
      "platformId": "ISR4451-X/K9"
    },
    {
      "id": "device-456",
      "hostname": "Switch1",
      "managementIpAddress": "10.10.20.2",
      "softwareVersion": "16.12.5",
      "platformId": "C9300-24P"
    }
  ],
  "version": "1.0"
}

```

The engineer wants to filter the results to only show devices with software version 17.3.3. Which of the following API query parameters should be used?

Trap 1: /dna/intent/api/v1/network-device?version=17.3.3

'version' is not a valid filter; it refers to the API version, not the software version.

Trap 2: /dna/intent/api/v1/network-device?osVersion=17.3.3

The correct parameter is 'softwareVersion', not 'osVersion'.

Trap 3: /dna/intent/api/v1/network-device?filter=softwareVersion:17.3.3

DNA Center does not use a generic 'filter' parameter; it uses specific query parameters.

Study all REST APIs and Data Models common traps →

A
/dna/intent/api/v1/network-device?softwareVersion=17.3.3
The DNA Center API allows filtering by softwareVersion directly in the query string.
B
/dna/intent/api/v1/network-device?version=17.3.3
Why wrong: 'version' is not a valid filter; it refers to the API version, not the software version.
C
/dna/intent/api/v1/network-device?osVersion=17.3.3
Why wrong: The correct parameter is 'softwareVersion', not 'osVersion'.
D
/dna/intent/api/v1/network-device?filter=softwareVersion:17.3.3
Why wrong: DNA Center does not use a generic 'filter' parameter; it uses specific query parameters.

Full breakdown with real-world context →

Question 13mediummultiple choice

Study the full Python automation breakdown →

A network engineer writes a Python script using NAPALM to retrieve the ARP table from a Cisco IOS-XE device:

```python

from napalm import get_network_driver

driver = get_network_driver('ios') connection = driver('10.1.1.1', 'admin', 'password') connection.open() arp_table = connection.get_arp_table()

for entry in arp_table:
    print(f"IP: {entry['ip']} - MAC: {entry['mac']}")

connection.close() ```

What is the issue with this code?

Trap 1: The driver should be 'iosxr' for IOS-XE devices.

The correct driver for IOS-XE is 'ios'.

Trap 2: The 'get_arp_table' method does not exist; the correct method is…

The method exists.

Trap 3: The 'optional_args' parameter is required to specify the port.

Optional_args is not mandatory; default SSH port 22 is used.

Study all REST APIs and Data Models common traps →

A
The driver should be 'iosxr' for IOS-XE devices.
Why wrong: The correct driver for IOS-XE is 'ios'.
B
The 'get_arp_table' method does not exist; the correct method is 'get_arp_table'.
Why wrong: The method exists.
C
The driver is misspelled; it should be 'ios' but the code uses 'eos' which is for Arista.
The driver 'eos' is for Arista EOS, not Cisco IOS. This will cause connection failure.
D
The 'optional_args' parameter is required to specify the port.
Why wrong: Optional_args is not mandatory; default SSH port 22 is used.

Full breakdown with real-world context →

Question 14hardmultiple choice

Read the full REST/YANG explanation →

An engineer configures model-driven telemetry on a Cisco IOS-XE device with the following gRPC dial-out configuration:

``` telemetry ietf subscription 101 encoding encode-kvgpb filter xpath /interfaces/interface/state/counters source-address 10.1.1.1 stream yang-push update-policy periodic 500 receiver ip address 10.2.2.2 50001 protocol grpc-tcp ```

What is the purpose of the 'encoding encode-kvgpb' command?

Trap 1: It sets the encoding to JSON format for human readability.

KV-GPB is not JSON; it is a binary format.

Trap 2: It enables compression of the telemetry data.

Encoding does not imply compression.

Trap 3: It sets the encoding to XML format.

KV-GPB is not XML.

Study all REST APIs and Data Models common traps →

A
It sets the encoding to JSON format for human readability.
Why wrong: KV-GPB is not JSON; it is a binary format.
B
It specifies that the data should be encoded using the Key-Value Google Protocol Buffers format.
KV-GPB is a binary encoding used for telemetry data.
C
It enables compression of the telemetry data.
Why wrong: Encoding does not imply compression.
D
It sets the encoding to XML format.
Why wrong: KV-GPB is not XML.

Full breakdown with real-world context →

Question 15easymultiple choice

Study the full Python automation breakdown →

A network engineer uses the following Python script with Netmiko to send a command to a Cisco IOS-XE device:

```python

from netmiko import ConnectHandler

device = { 'device_type': 'cisco_ios', 'ip': '10.1.1.1', 'username': 'admin', 'password': 'password', 'secret': 'enable_secret'

connection = ConnectHandler(**device) output = connection.send_command('show ip interface brief')

print(output)

connection.disconnect() ```

What is the purpose of the 'secret' parameter in the device dictionary?

Trap 1: It is used for SSH key-based authentication.

SSH key authentication is handled differently.

Trap 2: It is used to encrypt the session.

Encryption is handled by SSH.

Trap 3: It is used to set the SNMP community string.

SNMP is separate.

Study all REST APIs and Data Models common traps →

A
It is used for SSH key-based authentication.
Why wrong: SSH key authentication is handled differently.
B
It is used to enter enable mode after connecting to the device.
The 'secret' parameter provides the enable password to enter privileged EXEC mode.
C
It is used to encrypt the session.
Why wrong: Encryption is handled by SSH.
D
It is used to set the SNMP community string.
Why wrong: SNMP is separate.

Full breakdown with real-world context →

Question 16mediummultiple choice

Read the full REST/YANG explanation →

An engineer is using the Cisco IOS-XE RESTCONF API to create a new loopback interface. The following JSON payload is sent in a POST request to '/restconf/data/ietf-interfaces:interfaces':

```json

"ietf-interfaces:interface": [

{
      "name": "Loopback100",
      "description": "Management Loopback",
      "type": "iana-if-type:softwareLoopback",
      "enabled": true,

"ietf-ip:ipv4": {

"address": [
          {
            "ip": "192.168.1.1",
            "netmask": "255.255.255.0"
          }
        ]
      }
    }
  ]
}

```

What is the correct HTTP method and URL for this operation?

Trap 1: PUT /restconf/data/ietf-interfaces:interfaces

PUT is used to replace or create a specific resource, not a collection.

Trap 2: PATCH /restconf/data/ietf-interfaces:interfaces

PATCH is used for partial updates.

Trap 3: POST /restconf/data/ietf-interfaces:interfaces/interface=Loopback100

That URL would be for a specific interface, but the payload contains the interface list.

Study all REST APIs and Data Models common traps →

A
POST /restconf/data/ietf-interfaces:interfaces
POST is used to create a new resource under the interfaces collection.
B
PUT /restconf/data/ietf-interfaces:interfaces
Why wrong: PUT is used to replace or create a specific resource, not a collection.
C
PATCH /restconf/data/ietf-interfaces:interfaces
Why wrong: PATCH is used for partial updates.
D
POST /restconf/data/ietf-interfaces:interfaces/interface=Loopback100
Why wrong: That URL would be for a specific interface, but the payload contains the interface list.

Full breakdown with real-world context →

Question 17mediummultiple choice

Read the full Ansible explanation →

An Ansible playbook uses the cisco.ios.ios_l3_interfaces module to configure an IPv4 address on GigabitEthernet0/1:

```yaml --- - name: Configure IPv4 address hosts: cisco-routers gather_facts: no tasks: - name: Set IP address cisco.ios.ios_l3_interfaces: config: - name: GigabitEthernet0/1 ipv4: - address: 10.1.1.1/24 state: merged ```

What is the effect of the 'state: merged' parameter?

Trap 1: It replaces the entire L3 configuration on the interface with only…

That is the behavior of 'replaced', not 'merged'.

Trap 2: It deletes the IP address if it exists.

That would be 'absent' state.

Trap 3: It only checks the configuration without making changes.

That would be 'gathered' or 'rendered'.

Study all REST APIs and Data Models common traps →

A
It replaces the entire L3 configuration on the interface with only the provided address.
Why wrong: That is the behavior of 'replaced', not 'merged'.
B
It adds the IP address to the interface, merging with any existing configuration.
'merged' adds the configuration to the existing one without removing other settings.
C
It deletes the IP address if it exists.
Why wrong: That would be 'absent' state.
D
It only checks the configuration without making changes.
Why wrong: That would be 'gathered' or 'rendered'.

Full breakdown with real-world context →

Question 18easymultiple choice

Read the full REST APIs and Data Models explanation →

A network engineer is using the Cisco DNA Center API to initiate a network discovery. The API endpoint '/dna/intent/api/v1/discovery' is called with a POST request containing the following JSON payload:

```json

{
  "discoveryType": "Range",
  "ipAddressList": "10.10.20.1-10.10.20.254",
  "protocolOrder": "SSH",
  "timeout": 5,
  "retryCount": 3
}

```

The API returns a 202 Accepted status code. What does this indicate?

Trap 1: The discovery was completed successfully and devices are added.

202 does not mean completion; it means accepted for processing.

Trap 2: The request is invalid and the payload needs correction.

A 202 indicates the request was valid and accepted.

Trap 3: The server is busy and the request is queued.

202 does not necessarily mean queued; it means accepted for processing.

Study all REST APIs and Data Models common traps →

A
The discovery was completed successfully and devices are added.
Why wrong: 202 does not mean completion; it means accepted for processing.
B
The request is invalid and the payload needs correction.
Why wrong: A 202 indicates the request was valid and accepted.
C
The discovery has been accepted and is being processed asynchronously.
202 Accepted is used for asynchronous operations.
D
The server is busy and the request is queued.
Why wrong: 202 does not necessarily mean queued; it means accepted for processing.

Full breakdown with real-world context →

Question 19mediummultiple choice

Read the full NAT/PAT explanation →

Examine the following configuration snippet applied to a Cisco IOS-XE device:

interface GigabitEthernet0/1
 ip address 10.1.1.1 255.255.255.0
 ip nat inside

interface GigabitEthernet0/2
 ip address 192.168.1.1 255.255.255.0
 ip nat outside

access-list 100 permit ip 10.1.1.0 0.0.0.255 any
ip nat inside source list 100 interface GigabitEthernet0/2 overload

What is the effect of this configuration?

Trap 1: It performs static NAT for the host 10.1.1.1 to 192.168.1.1.

Incorrect. Static NAT would require 'ip nat inside source static' commands, not an access list with overload.

Trap 2: It translates all traffic from 192.168.1.0/24 to the IP address…

Incorrect. The inside network is 10.1.1.0/24, not 192.168.1.0/24. The outside interface is 192.168.1.1.

Trap 3: It allows all IP traffic from any source to any destination without…

Incorrect. The access list permits only traffic from 10.1.1.0/24, and the NAT command translates it. It does not permit all traffic.

Study all REST APIs and Data Models common traps →

A
It translates all IP traffic from 10.1.1.0/24 to the IP address 192.168.1.1 using port address translation.
Correct. The 'ip nat inside source list 100 interface GigabitEthernet0/2 overload' command performs PAT, translating the inside network to the outside interface IP.
B
It performs static NAT for the host 10.1.1.1 to 192.168.1.1.
Why wrong: Incorrect. Static NAT would require 'ip nat inside source static' commands, not an access list with overload.
C
It translates all traffic from 192.168.1.0/24 to the IP address 10.1.1.1.
Why wrong: Incorrect. The inside network is 10.1.1.0/24, not 192.168.1.0/24. The outside interface is 192.168.1.1.
D
It allows all IP traffic from any source to any destination without translation.
Why wrong: Incorrect. The access list permits only traffic from 10.1.1.0/24, and the NAT command translates it. It does not permit all traffic.

Full breakdown with real-world context →

Question 20mediummultiple choice

Review the full OSPF breakdown →

Given the following configuration on a Cisco IOS-XE device:

router ospf 1
 network 10.0.0.0 0.255.255.255 area 0

interface GigabitEthernet0/0
 ip address 10.1.1.1 255.255.255.0
 ip ospf cost 10

interface GigabitEthernet0/1
 ip address 10.2.2.1 255.255.255.0

Which statement is true about OSPF operation?

Trap 1: Both interfaces will have an OSPF cost of 10.

Incorrect. Only GigabitEthernet0/0 has the explicit cost of 10. GigabitEthernet0/1 will use the default cost based on its bandwidth (e.g., 1 for GigabitEthernet).

Trap 2: Both interfaces will have the same OSPF cost because they are in…

Incorrect. OSPF cost is interface-specific and not determined by area membership alone.

Trap 3: OSPF will not run on either interface because the network command…

Incorrect. The wildcard mask 0.255.255.255 matches all addresses starting with 10.x.x.x, so both interfaces are included.

Study all REST APIs and Data Models common traps →

A
Both interfaces will have an OSPF cost of 10.
Why wrong: Incorrect. Only GigabitEthernet0/0 has the explicit cost of 10. GigabitEthernet0/1 will use the default cost based on its bandwidth (e.g., 1 for GigabitEthernet).
B
GigabitEthernet0/0 will have an OSPF cost of 10, and GigabitEthernet0/1 will have a default cost based on its bandwidth.
Correct. The explicit cost applies only to the interface it is configured on. The other interface uses the default cost.
C
Both interfaces will have the same OSPF cost because they are in the same area.
Why wrong: Incorrect. OSPF cost is interface-specific and not determined by area membership alone.
D
OSPF will not run on either interface because the network command uses a wildcard mask of 0.255.255.255.
Why wrong: Incorrect. The wildcard mask 0.255.255.255 matches all addresses starting with 10.x.x.x, so both interfaces are included.

Full breakdown with real-world context →

Continue with 20-question session →

Free account

Track your progress over time

Create a free account to save your results and see which topics improve across sessions.

Focused REST APIs and Data Models sessions

Start a REST APIs and Data Models only practice session

Every question in these sessions is drawn from the REST APIs and Data Models domain — nothing else.

10 questions 20 questions 30 questions 50 questions

Browse all REST APIs and Data Models questions →Mixed 350-401 session

Frequently asked questions

What does the 350-401 exam test about REST APIs and Data Models?: REST APIs and Data Models questions test whether you can apply the concept in context, not just recognise a definition.
How should I use these practice questions?: Select your answer before revealing the explanation. Then read why each option is right or wrong — this active recall approach builds retention far faster than re-reading notes.
Can I practise just REST APIs and Data Models questions in a focused session?: Yes — the session launcher on this page draws every question from the REST APIs and Data Models domain. Use a 10-question session first to gauge your baseline, then move to 20 or 30 once the weak spots are clear.
Where can I practise other 350-401 topics?: Use the topic links above to move to related areas, or go back to the 350-401 question bank to see all topics.
Are these real exam questions or dumps?: These are original practice questions written to test the same concepts the 350-401 exam covers. They are not copied from any real exam or dump site.

REST APIs and Data Models only

10 questions 20 questions 30 questions 50 questions

Mixed 350-401 session

Track your progress

A free account saves results across sessions and highlights which topics need work.

Study resources

All 350-401 questions REST APIs and Data Models domain overview 350-401 exam guide

Exam traps to avoid

▸Answering from memory before reading the full scenario.
▸Missing a constraint such as cost, availability, security, scope or command context.
▸Choosing a broad answer when the question asks for the most specific fix.
▸Ignoring why the wrong options are tempting.

REST APIs and Data Models practice questions

What to know about REST APIs and Data Models

Common REST APIs and Data Models exam traps

REST APIs and Data Models questions

Track your progress over time

Start a REST APIs and Data Models only practice session

Related 350-401 topic practice pages

Architecture practice questions

Enterprise Network Design practice questions

SD-Access Architecture practice questions

SD-WAN Architecture practice questions

QoS Architecture practice questions

Virtualization practice questions

Network Function Virtualization practice questions

Virtual Machines and Hypervisors practice questions

VRF and Path Isolation practice questions

Infrastructure practice questions

OSPF practice questions

BGP practice questions

Frequently asked questions

Track your progress

Study resources

Exam traps to avoid