8. Compare Common API Styles (REST, RPC, Synchronous, and Asynchronous) 200-901 Practice Questions (Page 4)

Questions 16–20

1. 16expert · medium

   A network device vendor provides an API that uses URLs like '/api/v1/interfaces' and supports GET, POST, PUT, DELETE. However, the API also requires clients to include a session token in every request, and the server stores the session state to track which user is authenticated. A developer claims this is a REST API. Is this claim correct?

   • AYes, because the session token is included in every request, making it stateless.
   • BYes, because it uses resource-based URLs and HTTP methods.
   • CNo, because REST APIs cannot use session tokens at all.
   • DNo, because REST requires statelessness, and the server maintaining session state violates that constraint.
   Reveal Solution Discussion Select an answer first
2. 17expert · medium

   A network team is designing a REST API for managing device configurations. They need to support partial updates to a configuration resource without replacing the entire configuration. Which HTTP method should they use?

   • APOST
   • BPATCH
   • CPUT
   • DGET
   Reveal Solution Discussion Select an answer first
4. 18expert · medium

   A network automation engineer is designing a script that must configure a series of devices in a specific order, where each device's configuration depends on the successful configuration of the previous device. The script must also handle errors immediately if a device fails. Which API interaction model is most appropriate?

   • AUse synchronous API calls, because the script must wait for each device's response before proceeding to the next.
   • BUse a mix of synchronous and asynchronous calls, using synchronous for the first device and asynchronous for the rest.
   • CUse asynchronous API calls with callbacks, because callbacks allow the script to continue and handle each response as it arrives.
   • DUse asynchronous API calls with polling, because polling allows the script to check the status of each device periodically.
   Reveal Solution Discussion Select an answer first
5. 19foundation · easy

   Which characteristic is typical of an RPC-style API?

   • ARelying on hypermedia links to navigate between related resources
   • BUsing only the HTTP POST method for all operations
   • CUsing a single endpoint and sending a method name and parameters in the request body
   • DExposing resources with URLs and using HTTP methods like GET and POST
   Reveal Solution Discussion Select an answer first
6. 20application · medium

   A developer is designing an API for a network device inventory system. The API will be used by multiple clients, and the developer wants to leverage standard HTTP caching and status codes. Which API style should the developer choose?

   • AREST API with a single endpoint and custom action parameters
   • BRPC API using XML-RPC with a single endpoint for all actions
   • CREST API with resource-based URLs and HTTP methods
   • DRPC API using JSON-RPC with method names like getInventory
   Reveal Solution Discussion Select an answer first