200-901 Understanding and Using APIs — 10 Questions

Question 1

A network engineer is using the Cisco Meraki API to retrieve a list of SSIDs for a specific network. The API returns an HTTP 200 status but an empty array for the SSIDs. Which of the following is the most likely cause?

Accepted Answer

The network exists but has no SSIDs configured.. An HTTP 200 status indicates the request was successfully processed by the Meraki API, meaning the API key, network ID, and request format were all valid. An empty array for SSIDs specifically means the network exists and the API queried it correctly, but no SSIDs have been configured on that network. This is the expected behavior when a network has no wireless profiles defined.

Answer

The network ID is incorrect.

Answer

The API key is invalid.

Answer

The request body is malformed.

Question 2

When designing a REST API client for a Cisco DNA Center deployment, which authentication method should be used to obtain a token for subsequent API calls?

Accepted Answer

HTTP Basic authentication to obtain a token.. Cisco DNA Center uses HTTP Basic authentication to obtain a token. The client sends a POST request to the /dna/system/api/v1/auth/token endpoint with a Base64-encoded string of the username and password in the Authorization header. The server returns a token that must be included in subsequent API calls via the X-Auth-Token header.

Answer

OAuth 2.0 client credentials grant.

Answer

API key in the request header.

Answer

Client certificate in the request.

Question 3

A Python script uses the Cisco Meraki API to create a new network and then immediately attempts to configure an SSID on that network. The SSID creation fails with a 400 error indicating 'network is not ready'. What is the most likely cause?

Accepted Answer

The network is not fully provisioned yet; a delay is needed.. The Meraki API returns a 400 error with 'network is not ready' because creating a network is an asynchronous operation. The network's underlying infrastructure (e.g., virtual LANs, DHCP scopes, firewall rules) must be fully provisioned before it can accept SSID configurations. Attempting to configure an SSID immediately after creation fails because the network is still in a 'pending' or 'provisioning' state, requiring a polling delay or retry logic.

Answer

The API rate limit has been exceeded.

Answer

The API key does not have write access to networks.

Answer

The SSID name contains invalid characters.

Question 4

Which TWO of the following are best practices when using REST APIs in Cisco networking environments?

Accepted Answer

Always handle HTTP error codes like 4xx and 5xx.. Option C is correct because handling HTTP error codes like 4xx (client errors) and 5xx (server errors) is essential for robust REST API integration. In Cisco environments, APIs such as those for DNA Center or Meraki return these codes to indicate issues like authentication failure (401), rate limiting (429), or server overload (503). Proper error handling allows the application to retry, log, or alert appropriately, preventing silent failures and ensuring reliable network automation.

Answer

Send credentials as plain text in every request.

Answer

Poll the API every second to get real-time updates.

Answer

Embed API keys directly in the URL query parameters.

Question 5

Refer to the exhibit. A network engineer runs a script that queries the Cisco DNA Center site health API. The response shows Branch1 with a healthScore of 10. What is the most likely action to improve Branch1's health?

Accepted Answer

Investigate the network devices and connectivity at Branch1.. A healthScore of 10 on a scale of 0–100 indicates severe degradation, typically caused by network device failures, link flaps, or connectivity loss. Investigating the network devices and connectivity at Branch1 is the correct first step to identify and resolve the root cause, such as a down switch or a routing issue.

Answer

Increase the number of clients at Branch1.

Answer

Check the API authentication token.

Answer

Use a different API version.

Question 6

A DevOps team manages a multi-site Cisco Meraki network with 50 MX appliances and 200 MR access points. They use a Python script that calls the Meraki API to collect device utilization data every hour and stores it in a CSV file. Recently, the script started failing intermittently with HTTP 429 status codes. The team suspects rate limiting but notices that the failures occur even when only one script instance runs. The script uses a single API key and makes requests to the /devices/{serial}/uplink endpoint for each MX and the /devices/{serial}/wireless/status endpoint for each MR. The script is scheduled via cron and runs sequentially. The team wants to resolve the rate limiting while minimizing changes to the script. Which course of action should the team take?

Accepted Answer

Introduce a delay between API calls to stay within the rate limit.. The intermittent HTTP 429 errors indicate the script is exceeding the Meraki API rate limit, which applies per API key. Since the script runs sequentially with a single key, introducing a delay between API calls (e.g., using time.sleep()) is the simplest fix that stays within the rate limit without requiring architectural changes. This directly addresses the root cause while minimizing modifications to the existing script.

Answer

Distribute the API requests across multiple API keys.

Answer

Switch to a webhook-based approach to receive data instead of polling.

Answer

Use the bulk API request feature to collect data in fewer calls.

Question 7

Drag and drop the steps to troubleshoot a network connectivity issue using the OSI model from bottom to top.

Question 8

Drag and drop the steps to set up a Python virtual environment for a DevNet project into the correct order.

Question 9

Match each HTTP method to its typical use case in REST APIs.

Question 10

Match each YAML structure to its description.