CCNA AI and Network Operations Questions — Page 3 of 3

151

MCQhard

In a controller-based design, which statement best describes a northbound API?

A.An application-facing API used by external software to communicate with the controller

B.A cable type used between controller clusters

C.The link-state protocol the controller uses to reach switches

D.A mechanism that removes the need for authentication

AnswerA

In a controller-based architecture, the northbound API (often RESTful) faces applications and orchestration systems, allowing them to request network services or retrieve telemetry without manual device-level configuration. It abstracts the underlying network complexity, so external software can communicate intent to the controller, which then translates that intent into device-specific actions. This direction is 'north' because it sits above the controller in the logical hierarchy.

Why this answer

A northbound API is the interface exposed by the controller to external applications, orchestration systems, dashboards, or automation tools. In plain language, it is the way software above the controller communicates with the controller so that it can request data, apply policy, or trigger changes. This is different from the southbound side, where the controller interacts with the underlying infrastructure devices.

This concept appears often in automation topics because it helps define where the controller sits in the larger architecture. A northbound API is not a physical cable, and it does not replace security controls. It is an application-facing software interface, which is exactly what the correct answer should capture.

Exam trap

A frequent exam trap is mistaking the northbound API for a physical cable or a routing protocol. Some candidates incorrectly associate 'northbound' with physical connections between controllers or with link-state protocols, which is incorrect. Northbound APIs are purely logical interfaces used by applications to communicate with the controller, not hardware or routing mechanisms.

Another trap is assuming northbound APIs bypass security controls; in reality, these APIs require proper authentication and authorization. Misunderstanding these points can lead to selecting incorrect answers that describe physical or protocol-related concepts rather than software interfaces.

Why the other options are wrong

This option incorrectly describes a northbound API as a cable type, which is a physical concept unrelated to the logical API direction in controller architectures.

This option confuses northbound APIs with routing protocols like link-state protocols, which are unrelated to the software interface role of northbound APIs.

This option falsely claims that northbound APIs remove the need for authentication, ignoring that security controls remain essential for API access.

Practice this question →

152

MCQhard

Why is HTTPS preferred over HTTP when accessing sensitive controller APIs?

A.Because HTTPS encrypts the API traffic in transit.

B.Because HTTPS removes the need for tokens and credentials.

C.Because HTTPS is the only way JSON can be transmitted.

D.Because HTTP cannot carry API requests at all.

AnswerA

HTTPS wraps the API payload in TLS/SSL encryption, so any sensitive data transmitted over the network—such as passwords, tokens, or personal information—remains unreadable to anyone who intercepts the packets. This prevents eavesdropping and man-in-the-middle attacks, which is why secure communication is mandatory for sensitive operations. In contrast, HTTP sends all data as plaintext, leaving it exposed on shared networks.

Why this answer

HTTPS is preferred because it encrypts the traffic in transit. In practical terms, sensitive controller APIs may carry tokens, credentials, operational details, and configuration data. Sending that information over plain HTTP would expose it to interception on the network. HTTPS reduces that risk by protecting the session.

This does not make HTTPS a replacement for authentication. It is a transport-security choice that works alongside access control, not instead of it.

Exam trap

A frequent exam trap is believing that HTTPS removes the need for tokens or credentials in API access. Some candidates incorrectly assume that because HTTPS encrypts traffic, authentication is unnecessary. However, HTTPS only secures the transport layer and does not provide access control.

Another trap is thinking HTTP cannot carry API requests, which is false since HTTP can transmit API data but without encryption. Also, confusing the data format with the transport protocol leads to the incorrect belief that JSON requires HTTPS, when in fact JSON can be sent over any protocol. Understanding these distinctions is crucial to avoid selecting incorrect answers.

Why the other options are wrong

Option B is incorrect because HTTPS does not remove the need for tokens or credentials; it only secures the transport layer. Authentication is still required to control access to APIs.

Option C is incorrect since JSON can be transmitted over any protocol, including HTTP and HTTPS. The choice of HTTPS is about securing the transport, not the data format.

Option D is incorrect because HTTP can carry API requests; however, it does so without encryption, making it unsuitable for sensitive data transmission.

Practice this question →

153

MCQhard

An API response returns a list of interface objects in JSON. Which structure most likely represents that list?

A.An array containing multiple interface objects

B.A single integer with the value 1

C.A native VLAN field

D.An STP root bridge ID

AnswerA

An array containing multiple interface objects is the correct representation because JSON arrays are explicitly designed to hold an ordered collection of repeated items, with each element separated by a comma and enclosed in square brackets. In a REST API response, a list of interfaces is naturally modeled as an array where each element is a JSON object containing key-value pairs such as interface name, status, and IP address. This directly matches the request for a list of interface objects, making it the appropriate structure for the response.

Why this answer

In JSON, a list is most naturally represented as an array. In plain language, when an API needs to return several interfaces, routes, VLANs, or similar repeated items, it usually places them inside square brackets as an ordered collection. Each item inside that array might itself be an object containing keys such as name, status, or IP address.

CCNA automation questions usually test whether you recognize that square brackets signal a list. If the response contains many similar interface records, the best structure is the one that looks like a JSON array of interface objects rather than a single scalar value.

Exam trap

Remember that arrays in JSON are denoted by square brackets, and each item should be a complete object if details are needed.

Why the other options are wrong

Option B is incorrect because an API response that returns a list of interface objects should be structured as an array, not as a single integer. A single integer does not represent a collection of objects.

A native VLAN field is not a valid representation of a list of interface objects in JSON; it typically refers to a specific VLAN configuration in networking, not an array structure.

Option D is incorrect because an STP root bridge ID is a specific identifier related to Spanning Tree Protocol, not a representation of a list of interface objects in JSON format.

Practice this question →

154

MCQmedium

A network engineer needs to automate the configuration of multiple Cisco IOS XE routers in a data center. The team requires a standard, vendor-neutral data modeling language to define the configuration parameters, and they need a protocol that uses XML-based remote procedure calls over SSH for secure, reliable configuration transactions. Which combination of technologies best meets these requirements?

A.Use YANG data models combined with RESTCONF over HTTPS.

B.Use YANG data models combined with NETCONF over SSH.

C.Use CLI commands combined with NETCONF over SSH.

D.Use CLI commands combined with RESTCONF over HTTPS.

AnswerB

YANG plus NETCONF over SSH is the standard model-driven management combination: YANG provides a vendor-neutral, hierarchical data model for configuration and state data, while NETCONF carries those models in XML-encoded RPCs over an encrypted SSH session. The NETCONF session supports transactions across multiple configuration datastores (candidate, running, startup), giving reliable commit/rollback behavior. This pairing exactly matches the requirements for a standardized data model and secure, remote procedure-style configuration exchange.

Why this answer

YANG is a standard, vendor-neutral data modeling language (RFC 6020) for defining configuration parameters, and NETCONF (RFC 6241) uses XML-based remote procedure calls (RPCs) over SSH for secure, reliable configuration transactions. This combination directly satisfies the requirement for a standard data model and XML-based RPCs over SSH, unlike RESTCONF which uses HTTPS and JSON/XML but not SSH.

Exam trap

Cisco often tests the distinction between NETCONF (XML RPCs over SSH) and RESTCONF (RESTful operations over HTTPS), and candidates mistakenly choose RESTCONF because it is more modern, but the question explicitly requires XML-based RPCs over SSH, which only NETCONF provides.

Why the other options are wrong

The scenario specifies a protocol that uses XML-based RPCs over SSH, which is a characteristic of NETCONF, not RESTCONF.

The scenario specifically asks for a standard, vendor-neutral data modeling language, which CLI is not.

Neither the data modeling language (CLI) nor the protocol (RESTCONF) matches the specified requirements of vendor-neutral data modeling and XML-based RPCs over SSH.

Practice this question →

155

Multi-Selectmedium

A script authenticates to a controller API and receives a token that it presents in later requests. Which two statements about that token-based workflow are correct?

Select 2 answers

A.The token is often sent in an HTTP header in subsequent requests

B.The token proves identity for that authenticated session or request set

C.The token changes the API from REST to SNMP

D.The token must be stored in the router startup-config

AnswersA, B

The token is typically included in the Authorization header of subsequent HTTP requests, often using the Bearer authentication scheme. This allows the controller API to validate the token and associate the request with the previously authenticated session without re-prompting for credentials. Stateless API servers rely on this per-request header transmission to maintain authentication context across multiple REST calls.

Why this answer

After authentication, many APIs issue a token that the client includes in later HTTP requests. That token acts as proof that the client already authenticated successfully.

Exam trap

A common exam trap is assuming that the presence of a token changes the network management protocol from REST to SNMP or another protocol. This is incorrect because token-based authentication is a security mechanism layered on top of the existing API protocol and does not alter it. Another trap is believing that tokens must be stored in the router’s startup-config, which is false since tokens are ephemeral credentials managed by client applications, not static device configurations.

Misunderstanding these points can lead to selecting incorrect answers about token workflows in automation scenarios.

Why the other options are wrong

Option C is incorrect because the token does not change the API protocol from REST to SNMP; authentication methods do not alter the underlying management protocol.

Option D is incorrect because tokens are managed dynamically by client applications and are not stored in router startup-config files, which hold static device configurations.

Practice this question →

156

PBQhard

You are connected to R1. Configure SNMP v2c with a read-only community string 'monitorRO' and a read-write community string 'controlRW', and enable SNMP traps for link status to the management server at 203.0.113.100. Additionally, configure NetFlow to export version 9 flow records to the same server on UDP port 2055, and ensure that only traffic from the 10.10.10.0/24 network is monitored. Finally, verify your configurations with the appropriate show commands.

Network Topology

Hints

•Remember to specify the SNMP version when configuring the trap receiver host.
•NetFlow version 9 must be explicitly configured; otherwise, version 5 is used by default.
•Apply the flow monitor to the interface that connects to the network you want to monitor (G0/1).

A.Configure SNMP community strings, enable link-status traps, set trap destination, configure NetFlow export version 9, and apply flow monitor to interface(s) carrying 10.10.10.0/24 traffic.

B.Configure SNMP community strings, enable link-status traps, set trap destination, and configure NetFlow export version 5. Apply flow monitor to all interfaces.

C.Configure SNMP community strings, enable all SNMP traps, set trap destination, and configure NetFlow export version 9. Apply flow monitor to interface with IP 10.10.10.0/24.

D.Configure SNMP community strings, enable link-status traps, set trap destination, and configure NetFlow export version 9. Do not apply any flow monitor; NetFlow automatically monitors all traffic.

AnswerA

solution

! R1
snmp-server community monitorRO RO
snmp-server community controlRW RW
snmp-server enable traps snmp linkdown linkup
snmp-server host 203.0.113.100 version 2c monitorRO
ip flow-export version 9
flow record NETFLOW-RECORD
 match ipv4 source address
 match ipv4 destination address
 match ipv4 protocol
 match transport source-port
 match transport destination-port
 collect counter bytes
 collect counter packets
 collect timestamp sys-uptime
 exit
flow exporter EXPORTER-TO-SERVER
 destination 203.0.113.100
 transport udp 2055
 source Loopback0
 exit
flow monitor MONITOR-10NET
 record NETFLOW-RECORD
 exporter EXPORTER-TO-SERVER
 cache timeout active 300
 exit
interface GigabitEthernet0/1
 ip flow monitor MONITOR-10NET input
 ip flow monitor MONITOR-10NET output
 exit

Why this answer

The solution correctly configures SNMP v2c with the required read-only and read-write community strings, enables only link-status traps, and sets the trap destination. For NetFlow, it uses Flexible NetFlow by defining a flow record, an exporter, and a monitor. Importantly, the export version (9) must be configured under the flow exporter, not with the legacy global `ip flow-export version 9` command.

The flow monitor is applied to GigabitEthernet0/1, which carries traffic from the 10.10.10.0/24 network. Verification can be done with `show snmp` to confirm communities and trap receivers, and `show flow monitor name MONITOR-10NET cache` or `show ip cache flow` to view exported flow records.

Exam trap

Common mistakes include mixing legacy and Flexible NetFlow commands (e.g., using the global `ip flow-export version` instead of setting it under the flow exporter), forgetting to apply the flow monitor to an interface, and enabling all SNMP traps rather than only link-status traps.

Why the other options are wrong

The question explicitly requires NetFlow version 9, and traffic monitoring must be limited to the 10.10.10.0/24 network.

Enabling all traps is unnecessary and may cause unwanted overhead; the flow monitor must be applied to the correct interface(s) based on traffic flow, not the network address.

NetFlow requires a flow monitor to be applied to an interface to capture traffic; it does not automatically monitor all traffic.

Practice this question →

157

MCQhard

Why is a northbound API valuable to orchestration tools in a controller-based network?

A.It gives orchestration tools a defined software interface to interact with the controller.

B.It replaces the need for all physical network devices.

C.It is a cabling standard for data center uplinks.

D.It makes security controls unnecessary.

AnswerA

A northbound API exposes the controller's capabilities through a defined, programmatic interface, so orchestration tools can configure and query devices without vendor-specific CLI scripting. This abstraction is what makes automated, controller-driven provisioning feasible across the fabric.

Why this answer

A northbound API is valuable because it gives orchestration tools a defined way to request data and trigger changes on the controller programmatically. In plain language, the tool can interact with the controller through software rather than relying on manual device-by-device operations. That makes higher-level automation and service coordination possible.

The controller is the platform, and the northbound API is the application-facing interface into it. The correct answer is the one focused on orchestration and software-driven interaction.

Exam trap

A frequent exam trap is mistaking the northbound API for a physical network element or a cabling standard, such as assuming it replaces physical devices or relates to data center uplinks. Another common error is believing that northbound APIs eliminate the need for security controls, ignoring that software interfaces still require authentication and authorization mechanisms. These misconceptions stem from confusing the software abstraction layer with hardware or security concepts.

Understanding that northbound APIs are purely software interfaces designed for orchestration tools to interact programmatically with the controller helps avoid these pitfalls.

Why the other options are wrong

Option B is incorrect because northbound APIs do not replace physical network devices; forwarding hardware remains essential for actual data transmission and network operation.

Option C is incorrect since northbound APIs are software interfaces, not physical cabling standards, and have no relation to data center uplink cabling specifications.

Option D is incorrect because northbound APIs still require security measures such as authentication and authorization; they do not eliminate the need for security controls.

Practice this question →

158

MCQeasy

Which data format is most commonly used in REST APIs because it is lightweight and easy for applications to parse?

A.YANG

B.JSON

C.STP

D.TFTP

AnswerB

JSON is the standard data-interchange format for REST APIs because it is lightweight, human-readable, and natively supported by JavaScript, making it trivial to parse in browsers and servers. It represents structured data as key-value pairs and arrays, mirroring the object literal syntax of many programming languages, and is transmitted with the Content-Type: application/json header. Its low overhead and easy mapping to language objects make it the default choice for most modern web APIs.

Why this answer

JSON is widely used with REST because it is compact, human-readable, and easy for software to parse. It is common in controller APIs and automation workflows.

Exam trap

A common exam trap is selecting YANG as the data format for REST APIs because candidates recognize YANG as related to network automation. However, YANG is a data modeling language that defines the structure of data but does not represent the actual data format used in REST API communication. Confusing YANG with JSON leads to incorrect answers.

Similarly, confusing protocols like STP or TFTP with data formats can mislead candidates. The key is to remember that JSON is the actual data format used in REST APIs due to its lightweight and easy-to-parse nature.

Why the other options are wrong

YANG is a data modeling language used to define the structure of network data but is not the actual data format used in REST API communication, making it an incorrect choice.

STP (Spanning Tree Protocol) is a Layer 2 protocol for preventing loops in Ethernet networks and has no relation to data formatting in REST APIs, so it is incorrect.

TFTP is a simple protocol used for file transfers, such as IOS images, and is not a data format used in REST APIs, making it an invalid choice.

Practice this question →

159

PBQhard

You are connected to R1 via the console. SNMP v2c community strings (public RO, private RW) are already configured. The network has a management server at 10.1.1.100 and a NetFlow collector at 10.1.1.200. Configure SNMP traps to the management server for link status changes. Also configure NetFlow on interface GigabitEthernet0/0 to export version 9 to the collector, with a source interface of Loopback0 (10.255.255.1/32).

Network Topology

Hints

•SNMP traps require both a host command and enabling specific trap types.
•NetFlow export needs destination, version, and source interface, plus flow ingress on the interface.
•Use 'show running-config | section snmp|flow' to verify your changes.

A.snmp-server host 10.1.1.100 version 2c public snmp-server enable traps snmp linkdown linkup ip flow-export destination 10.1.1.200 2055 ip flow-export version 9 ip flow-export source Loopback0 interface GigabitEthernet0/0 ip flow ingress

B.snmp-server host 10.1.1.200 version 2c private snmp-server enable traps ip flow-export destination 10.1.1.100 2055 version 9 ip flow-export source Loopback0 interface GigabitEthernet0/0 ip flow egress

C.snmp-server host 10.1.1.100 version 2c private snmp-server enable traps ip flow-export destination 10.1.1.200 2055 version 9 ip flow-export source Loopback0 interface GigabitEthernet0/0 ip flow ingress

D.snmp-server host 10.1.1.100 version 2c public snmp-server enable traps snmp linkdown linkup ip flow-export destination 10.1.1.200 2055 version 5 ip flow-export source Loopback0 interface GigabitEthernet0/0 ip flow ingress

AnswerA

solution

! R1
snmp-server host 10.1.1.100 version 2c public
snmp-server enable traps snmp linkdown linkup
ip flow-export destination 10.1.1.200 2055
ip flow-export version 9
ip flow-export source Loopback0
interface GigabitEthernet0/0
ip flow ingress

Why this answer

The current configuration has SNMP community strings but lacks trap destinations and NetFlow export. To fix, you must configure snmp-server host 10.1.1.100 version 2c public to send traps, and snmp-server enable traps snmp linkdown linkup is required to send link status changes. For NetFlow, you need ip flow-export destination 10.1.1.200 2055 and then ip flow-export version 9 to set the export version.

Also configure ip flow-export source Loopback0 and apply ip flow ingress on GigabitEthernet0/0. Verification commands confirm the settings.

Exam trap

Pay close attention to the IP addresses: the management server (10.1.1.100) is for SNMP traps, and the collector (10.1.1.200) is for NetFlow. Also, remember that SNMP traps use the read-only community, and NetFlow version must match the requirement (version 9).

Why the other options are wrong

The specific factual error: The SNMP trap destination and NetFlow export destination are swapped, and the flow direction is egress instead of ingress.

The specific factual error: SNMP traps should use the read-only community string 'public', not the read-write 'private'.

The specific factual error: NetFlow export version is set to 5, but the requirement is version 9.

Practice this question →

160

PBQhard

You are connected to R1. Use RESTCONF to retrieve all operational interface statistics from the ietf-interfaces YANG module, then modify the description of GigabitEthernet0/1 to 'Link to R2 via RESTCONF' using a PATCH request. The device is reachable at 203.0.113.1 with port 443, username 'admin', password 'cisco123'. Identify the error that would occur if you used a PATCH with Content-Type: application/json instead of application/yang-data+json.

Network Topology

Hints

•RESTCONF base URI is always /restconf.
•Use the YANG module 'ietf-interfaces' for operational state and configuration.
•The correct media type for RESTCONF is application/yang-data+json, not generic application/json.

A.The server returns a 415 Unsupported Media Type error because RESTCONF requires the Content-Type header to be application/yang-data+json.

B.The server returns a 400 Bad Request error because the JSON payload is malformed when using application/json.

C.The server returns a 404 Not Found error because the URI is incorrect when using application/json.

D.The server returns a 204 No Content response but ignores the description change because application/json is not supported.

AnswerA

solution

! R1
GET https://203.0.113.1/restconf/data/ietf-interfaces:interfaces-state/interface
Accept: application/yang-data+json
PATCH https://203.0.113.1/restconf/data/ietf-interfaces:interfaces/interface=GigabitEthernet0/1
Content-Type: application/yang-data+json
{"ietf-interfaces:interface": [{"name": "GigabitEthernet0/1", "description": "Link to R2 via RESTCONF"}]}

Why this answer

The correct base URI for RESTCONF is https://203.0.113.1/restconf. To retrieve operational interface statistics, use GET with the path /data/ietf-interfaces:interfaces-state/interface. For the PATCH to modify the description, the URI must target /data/ietf-interfaces:interfaces/interface=GigabitEthernet0/1 with a JSON payload containing the 'description' leaf.

The required Content-Type and Accept headers must be 'application/yang-data+json'. Using 'application/json' will result in a 415 Unsupported Media Type error because RESTCONF requires the specific YANG media type.

Exam trap

The exam tests your knowledge of RESTCONF's strict media type requirements. Many candidates assume that application/json is acceptable because it is common in REST APIs, but RESTCONF specifically requires 'application/yang-data+json'. Remember that using any other media type results in a 415 error.

Why the other options are wrong

The specific factual error is that a 400 Bad Request is not triggered by an incorrect Content-Type; it is triggered by malformed syntax or invalid data.

The specific factual error is that the Content-Type header does not affect resource discovery; it only affects how the server interprets the payload.

The specific factual error is that an unsupported media type results in a client error (4xx), not a success response (2xx).

Practice this question →

161

MCQmedium

Which pairing is correct?

A.JSON — data modeling language used to define network schemas such as YANG modules

B.YANG — lightweight interchange format built from curly braces and arrays

C.RESTCONF — protocol that can use YANG-defined data models over HTTP-based access

D.NETCONF — spanning-tree enhancement for rapid convergence

AnswerC

RESTCONF is an IETF-standard protocol (RFC 8040) that exposes YANG-defined data models through a RESTful API over HTTP/HTTPS. It uses HTTP methods like GET, POST, PUT, PATCH, and DELETE to access configuration and state data, making it ideal for programmatic network automation and integration with web-based tooling. The pairing is correct because RESTCONF specifically bridges YANG models with HTTP-based access.

Why this answer

RESTCONF is an HTTP-based API approach that commonly uses YANG-defined data models. JSON is a data-interchange format, YANG is the data modeling language, and NETCONF is a network management protocol rather than an STP feature.

Exam trap

A frequent exam trap is confusing JSON with YANG or NETCONF with spanning-tree enhancements. JSON is a data format, not a modeling language, so pairing it with YANG modules is incorrect. Similarly, NETCONF is often mistakenly thought to be related to spanning-tree protocols, but it is actually a network configuration protocol.

Candidates might also confuse YANG’s role with JSON’s syntax or RESTCONF’s protocol function. This confusion arises because these technologies often work together but serve distinct purposes. Understanding each technology’s specific role prevents selecting incorrect answers based on superficial similarities.

Why the other options are wrong

Option A incorrectly pairs JSON with YANG modules as a data modeling language. JSON is a data interchange format used to represent data but does not define schemas or models. YANG is the actual modeling language used to define network data structures, so this pairing is false.

Option B wrongly describes YANG as a lightweight interchange format built from curly braces and arrays, which actually describes JSON syntax. YANG is a modeling language that defines network data hierarchies and constraints, not a data format with JSON-like syntax.

Option D falsely claims NETCONF is a spanning-tree enhancement for rapid convergence. NETCONF is a network configuration protocol using XML over SSH and has no relation to spanning-tree protocols or their convergence mechanisms, making this option incorrect.

Practice this question →

162

MCQmedium

Why is HTTPS usually preferred over HTTP when accessing a controller API?

A.Because HTTPS provides encrypted transport for API traffic.

B.Because HTTPS automatically replaces authentication.

C.Because HTTPS is the only format that can carry JSON.

D.Because HTTP cannot carry controller data at all.

AnswerA

HTTPS is preferred because it wraps API traffic in Transport Layer Security (TLS), encrypting the payload and headers so that sensitive data such as authentication tokens, controller commands, and responses cannot be read or modified by an eavesdropper. The encryption also provides integrity checking, preventing man-in-the-middle tampering. This transport-level confidentiality and integrity is the primary security advantage HTTPS has over plaintext HTTP.

Why this answer

HTTPS is preferred because it protects the communication with encryption while it crosses the network. In practical terms, controller APIs often carry tokens, credentials, device state, or configuration information that should not be exposed in clear text. HTTPS helps protect those requests and responses in transit.

This does not make HTTPS the same thing as JSON, nor does it remove the need for authentication. It is simply the more secure transport choice for sensitive API communication.

Exam trap

Avoid assuming that HTTPS improves speed or handles authentication. Focus on its role in securing data in transit.

Why the other options are wrong

This option is incorrect because HTTPS does not replace authentication; it enhances security by encrypting the transport layer, but authentication mechanisms still need to be implemented separately.

This option is incorrect because both HTTPS and HTTP can carry JSON data; JSON is a data format independent of the transport protocol used. Thus, HTTPS is not the only format capable of transmitting JSON.

This option is wrong because HTTP can indeed carry controller data; it is a fundamental protocol for transmitting data over the web. Both HTTP and HTTPS can be used to send and receive data, including JSON payloads, between clients and APIs.

Practice this question →