API essentials check

Loading learning content…

Question 1 of 19What is a primary purpose of an API contract?

Define how callers interact with capabilities without depending on internal implementationExpose all internal database details directly to clientsRemove the need for server-side application logic

Question 2 of 19Which combination can be part of an HTTP request?

Method, URL, headers, and optional bodyOnly an HTTP status codeOnly a database table and primary key

Question 3 of 19Which endpoint is more consistent with resource-oriented RESTful design?

GET /api/projects/42GET /api/getProjectById/42GET /api/selectFromProjects

Question 4 of 19Which HTTP method commonly represents a partial update to an existing resource?

PATCHGETDELETE

Question 5 of 19Which status code commonly represents successful creation of a resource?

201 Created404 Not Found500 Internal Server Error

Question 6 of 19Which status code commonly indicates that the caller is authenticated but does not have permission for the requested operation?

403 Forbidden201 Created301 Moved Permanently

Question 7 of 19Which value is most naturally represented as a query parameter?

A sort order for a collection requestThe primary identity in /users/42A private database password

Question 8 of 19Why must an API validate request data even when the frontend already validates it?

Clients are outside the server trust boundary and can bypass frontend validationServer validation makes frontend validation unnecessary for user experienceValidation is required so CSS can render correctly

Question 9 of 19Where should authorization for a protected API operation ultimately be enforced?

On the trusted server handling the operationOnly by hiding the frontend buttonInside a CSS selector

Question 10 of 19What is a useful property of API error responses?

A consistent structure that clients can handle predictablyAlways expose the complete server stack trace publiclyUse a different response format for every error

Question 11 of 19Why should large API collections usually be paginated?

To avoid transferring and processing an unnecessarily large result in one requestTo prevent clients from filtering resultsTo remove resource identifiers from responses

Question 12 of 19Which HTTP header commonly communicates response caching policy?

Cache-ControlContent-TypeAuthorization

Question 13 of 19Why can API versioning become necessary?

A required contract change would otherwise break existing clientsEvery source-code commit requires a new API versionChanging a button color requires a new API version

Question 14 of 19What does a GraphQL schema define?

The types, fields, and operations exposed by the APIThe visual layout of the frontendThe browser's complete cache implementation

Question 15 of 19What is a key characteristic of a GraphQL query?

The client explicitly selects which fields should be returnedEvery request must return every field in the databaseQueries operate without any schema

Question 16 of 19Why are GraphQL variables useful?

They separate dynamic input values from reusable query textThey replace the GraphQL schemaThey disable GraphQL type validation

Question 17 of 19What is a GraphQL mutation intended to represent?

An operation that changes server-side stateA frontend animation stateA static HTML document

Question 18 of 19What is a GraphQL resolver responsible for?

Providing the server-side value or behavior for a schema fieldRendering CSS styles in the browserDefining the HTTP protocol itself

Question 19 of 19Which statement accurately compares REST and GraphQL?

REST commonly uses resource-oriented endpoints, while GraphQL exposes a typed queryable graph; each has different tradeoffsGraphQL is always better for every applicationREST cannot use HTTP methods or status codes

Choose one answer for every question, then check your answers.