12 real REST Principles questions from the REST API bank, as asked in Indian campus drives and tech interviews. Every question has a verified answer and an AI-tutor explanation on placd — free to start.
1. What is Statelessness?
Junior
A.the constraint that decouples the user interface concerns from data storage so each can evolve independently
B.the constraint that resources are manipulated through a standardized, consistent set of methods and representations across the API
C.the constraint where responses embed hypermedia links that tell the client which actions and transitions are available next
D.the constraint that each request must carry all information needed to be understood, with no client session stored on the server between calls
2. Which term means: "the constraint that each request must carry all information needed to be understood, with no client session stored on the server between calls"?
A.Statelessness — the constraint that decouples the user interface concerns from data storage so each can evolve independently
B.Statelessness — the constraint where responses embed hypermedia links that tell the client which actions and transitions are available next
C.Statelessness — the constraint that each request must carry all information needed to be understood, with no client session stored on the server between calls
D.Statelessness — the constraint that resources are manipulated through a standardized, consistent set of methods and representations across the API
5. Which term means: "the constraint that resources are manipulated through a standardized, consistent set of methods and representations across the API"?
A.Uniform Interface — the constraint that decouples the user interface concerns from data storage so each can evolve independently
B.Uniform Interface — the constraint where responses embed hypermedia links that tell the client which actions and transitions are available next
C.Uniform Interface — the constraint that each request must carry all information needed to be understood, with no client session stored on the server between calls
D.Uniform Interface — the constraint that resources are manipulated through a standardized, consistent set of methods and representations across the API
A.HATEOAS — the constraint that resources are manipulated through a standardized, consistent set of methods and representations across the API
B.HATEOAS — the constraint where responses embed hypermedia links that tell the client which actions and transitions are available next
C.HATEOAS — the constraint that decouples the user interface concerns from data storage so each can evolve independently
D.HATEOAS — the constraint that each request must carry all information needed to be understood, with no client session stored on the server between calls
A.Client-Server Separation — the constraint that resources are manipulated through a standardized, consistent set of methods and representations across the API
B.Client-Server Separation — the constraint that decouples the user interface concerns from data storage so each can evolve independently
C.Client-Server Separation — the constraint where responses embed hypermedia links that tell the client which actions and transitions are available next
D.Client-Server Separation — the constraint that each request must carry all information needed to be understood, with no client session stored on the server between calls
Answers, AI explanations, and a scored voice mock interview
Sign up free to check your answers with explanations, ask the AI tutor anything on any question, and take one full AI mock interview — scored like a real panel.