What is an architectural constraint to which a true RESTful API web service must adhere?

IT Questions BankCategory: CCNAWhat is an architectural constraint to which a true RESTful API web service must adhere?

Question:
What is an architectural constraint to which a true RESTful API web service must adhere?

  • It operates as a cloud service.
  • It runs as client/server model.
  • It must support the XML data format.
  • It uses HTTPS to transport data.

Explanation: Conforming to the constraints of the REST architecture is generally referred to as being “RESTful”. An API can be considered “RESTful” if it has the following features:

  • Client/server - The client handles the front end and the server handles the back end.
  • Stateless - No client data is stored on the server between requests. The session state is stored on the client.

Cacheable - Clients can cache responses locally to improve performance.

Exam with this question: CCNA 200-301 Certification Practice Exam Answers
Exam with this question: CCNA 3 v7 Module 14 Quiz - Network Automation
Exam with this question: 4.9.3 Module 4: Understanding and Using APIs Quiz

What is an architectural constraint to which a true RESTful API web service must adhere?

  • It operates in a stateless way.
  • It uses HTTPS to transport data.
  • It must operate along with a DNS server.
  • It operates as a cloud service.

Exam with this question: DevNet Associate (v1.0) – Module 4 Exam Answers

What is an architectural constraint to which a true RESTful API web service must adhere?

  • It must support XML-RPC and JSON-RPC.
  • It allows resource caching.
  • It should be behind a firewall.
  • It operates as a cloud service.

Exam with this question: DevNet Associate Course Final Exam Answers

Explanation: These are the REST constraints:

  • -Client/server
  • -Stateless
  • -Cache
  • -Uniform interface
  • -Layered system
  • -Code on demand

Subscribe
Notify of
guest

0 Comments
Inline Feedbacks
View all comments