200-901 Understanding and Using APIs Practice Test 6 — 15 Questions

Question 1

In Postman, what feature allows you to reuse a value like a base URL or token across multiple requests?

Accepted Answer

Environments. Environments store variables that can be referenced across requests.

Answer

Mock Servers

Answer

Workspaces

Answer

Collections

Question 2

Which pagination method uses a 'Link' header with 'rel="next"' to indicate the next page of results?

Accepted Answer

Cursor-based pagination with Link header. The Link header with rel="next" is used by the Meraki Dashboard API and others for cursor-based pagination.

Answer

Offset/limit pagination

Answer

Page-based pagination

Answer

Token-based pagination

Question 3

A developer is using NETCONF to retrieve the running configuration of a network device. Which operation should be used?

Accepted Answer

. The operation retrieves configuration from a datastore (e.g., running).

Answer

<get>

Answer

<copy-config>

Answer

<edit-config>

Question 4

When using the Meraki Dashboard API, how should the API key be included in a request?

Accepted Answer

In the X-Cisco-Meraki-API-Key header. Meraki requires the API key in a custom header X-Cisco-Meraki-API-Key.

Answer

As a query parameter named 'apiKey'

Answer

In the Authorization header using Bearer scheme

Answer

In the request body as JSON

Question 5

In gNMI, what is the difference between dial-in and dial-out streaming?

Accepted Answer

Dial-in: client initiates subscription and receives data; dial-out: device pushes data to a configured receiver. In gNMI, dial-in streaming refers to the client initiating a subscription request to the device, which then streams telemetry data back over the same gRPC session. Dial-out streaming, on the other hand, is a server-initiated model where the device (gNMI target) pushes telemetry data to a pre-configured receiver (collector) without waiting for a client request. Option C correctly captures this distinction: dial-in has the client subscribe and receive data, while dial-out has the device push data to a configured receiver.

Answer

Dial-in is for configuration, dial-out for telemetry

Answer

Dial-in: device initiates the connection; dial-out: client initiates

Answer

Dial-in uses gRPC, dial-out uses HTTP

Question 6

Which Cisco platform provides an Intent API for network automation, including endpoints for network-device, topology, and site hierarchy?

Accepted Answer

Cisco Catalyst Center. Cisco Catalyst Center (formerly DNA Center) provides an Intent API that abstracts network intent into RESTful endpoints. This API includes specific endpoints for managing network devices, retrieving topology views, and interacting with site hierarchy, enabling declarative network automation without low-level device configuration.

Answer

Cisco Webex

Answer

Cisco IOS XE

Answer

Meraki Dashboard

Question 7

A developer needs to retrieve a list of network devices from Cisco DNA Center with pagination. Which TWO URL components are typically used for offset/limit pagination?

Accepted Answer

Query parameter 'limit'. In Cisco DNA Center's REST API, pagination is typically implemented using the 'offset' and 'limit' query parameters. 'offset' specifies the starting index for the results, and 'limit' specifies the maximum number of items to return per page. This is a common pattern in many RESTful APIs for offset/limit pagination.

Answer

Link header

Answer

Query parameter 'page'

Answer

Path parameter 'page'

Question 8

Which THREE statements about NETCONF are correct?

Accepted Answer

NETCONF uses SSH as the transport protocol.. NETCONF uses SSH as its transport protocol, as specified in RFC 6242. This provides a secure, encrypted channel for network device management, which is a fundamental requirement for production environments.

Answer

NETCONF uses HTTP as the transport protocol.

Answer

The <get-config> operation retrieves both configuration and state data.

Question 9

Which TWO HTTP methods are considered safe (idempotent and without side effects on the server)?

Accepted Answer

HEAD. (HEAD) is correct because the HEAD method is defined as idempotent and safe per RFC 7231: it retrieves the same headers as a GET request but without a response body, causing no side effects on the server. Option E (GET) is also correct because GET is explicitly defined as a safe method that only retrieves data and does not modify server state, making it idempotent.

Answer

POST

Answer

PUT

Answer

DELETE

Question 10

Which HTTP method should be used to replace an entire existing resource in a RESTful API?

Accepted Answer

PUT. PUT is the correct HTTP method for replacing an entire existing resource in a RESTful API because it is defined as idempotent in RFC 7231, meaning the client sends a full representation of the resource to replace the current state at the target URI. Unlike POST, PUT is intended for full updates where the client specifies the URI and the server replaces the resource entirely with the provided payload.

Answer

POST

Answer

PATCH

Answer

DELETE

Question 11

A developer is making a GET request to a REST API and needs to specify that the response should be in JSON format. Which HTTP header should be set?

Accepted Answer

Accept. The Accept header is used by the client to tell the server which media types (e.g., application/json) it can understand and prefers for the response. In a GET request, the client does not send a body, so Content-Type is irrelevant for specifying the response format. Setting Accept: application/json ensures the server returns JSON if it supports that format.

Answer

Content-Type

Answer

User-Agent

Answer

Authorization

Question 12

A network automation engineer is using the Cisco DNA Center intent API to retrieve a list of network devices. Which API endpoint should be used?

Accepted Answer

GET /dna/intent/api/v1/network-device. The correct endpoint is GET /dna/intent/api/v1/network-device because the Cisco DNA Center intent API uses this path to retrieve a list of all network devices managed by the controller. The 'network-device' resource is specifically designed for device inventory operations, returning details such as hostname, IP address, platform ID, and software version. This aligns with the intent API's purpose of abstracting underlying complexities into business-relevant resources.

Answer

GET /dna/intent/api/v1/site

Answer

GET /dna/intent/api/v1/topology

Answer

GET /dna/intent/api/v1/issue

Question 13

When using the Meraki Dashboard API, what is the correct method to authenticate requests?

Accepted Answer

Include an API key in the X-Cisco-Meraki-API-Key header. The Meraki Dashboard API uses a unique API key for authentication, which must be included in the `X-Cisco-Meraki-API-Key` header. This key is generated per user in the Meraki Dashboard and identifies the request without requiring a session or password. Option D correctly specifies this custom header, which is the only supported method for authenticating requests to the Meraki API.

Answer

Include an API key in the Authorization header as a Bearer token

Answer

Use a session token obtained from a login endpoint

Answer

Use Basic authentication with username and password

Question 14

An application needs to receive real-time notifications when a new message is posted in a Webex space. Which Webex API feature should be used?

Accepted Answer

Create a webhook that triggers on 'messages' events. Webex uses webhooks to push real-time event notifications to an external server. By creating a webhook that triggers on 'messages' events, the application receives an HTTP POST request whenever a new message is posted in the specified space, eliminating the need for polling or persistent connections.

Answer

Establish a WebSocket connection to the Webex API

Answer

Use Server-Sent Events (SSE) from the Webex API

Answer

Poll the messages endpoint every second

Question 15

A developer is configuring a RESTCONF request to retrieve the configuration of an interface on a Cisco device. Which URL path and Content-Type header are correct?

Accepted Answer

GET /restconf/data/interface with Content-Type: application/yang-data+json. RESTCONF uses the '/restconf/data' base path to retrieve configuration data (the 'data' resource), and the correct Content-Type for RESTCONF with JSON encoding is 'application/yang-data+json', as defined in RFC 8040. This combination ensures the request targets the operational or configuration datastore and specifies the YANG-encoded JSON media type.

Answer

GET /restconf/data/interface with Content-Type: application/xml

Answer

GET /restconf/data/interface with Content-Type: application/json

Answer

GET /restconf/operations/interface with Content-Type: application/yang-data+json