1.
`Partial`
2.
`dependent`
3.
`associative`
4.
`linked`
Q 1 / 61
1.
`/companies/{id} and/company`
2.
`/company/{id} and/companies`
3.
`/companies/{id} and/companies`
4.
`/company/{id} and/company`
Q 2 / 61
1.
`data in the token`
2.
`Ownership`
3.
`a permission`
4.
`and integer`
Q 3 / 61
1.
`Uniform Interface`
2.
`Client-Server`
3.
`Stateless`
4.
`Chacheable`
Q 4 / 61
1.
`HTTP`
2.
`REST`
3.
`OPTIONS`
4.
`CORS`
Q 5 / 61
1.
`notify other systems of an event`
2.
`catch error faster`
3.
`improve error logging`
4.
`log additional data`
Q 6 / 61
1.
`to add new technologies to an organization's infrastructure.`
2.
`to share features and functionality with other system.`
3.
`to move infrastructure to the cloud.`
4.
`to appease the latest digital transformation effort.`
Q 7 / 61
1.
`bash`
2.
`curl`
3.
`ssh`
4.
`powerShell`
Q 8 / 61
1.
`OpenAPI (Swagger)`
2.
`WADL`
3.
`WSDL`
4.
`OAuth`
Q 9 / 61
1.
`SUBMIT`
2.
`WRITE`
3.
`POST`
4.
`CREATE`
Q 10 / 61
1.
`Mobile app work better.`
2.
`It improves uptime.`
3.
`It offers better security.`
4.
`It reduce load on servers.`
Q 11 / 61
1.
`409 Conflict`
2.
`400 Bad Request`
3.
`406 Not Acceptable`
4.
`405 Method Not Allowed`
Q 12 / 61
1.
`an identify layer on top of OAuth 2.0`
2.
`the new name for SAML 3.0`
3.
`a modern replacement for API keys`
4.
`an SSO competitor for OAuth 2.0`
Q 13 / 61
1.
`flexible querying/responses`
2.
`more stable APIs`
3.
`compatible with more gateways`
4.
`more secure by default`
Q 14 / 61
1.
`Stateless`
2.
`Client-Server`
3.
`Uniform Interface`
4.
`Cacheable`
Q 15 / 61
1.
`It identifies the user ID.`
2.
`It identifies the client application or SDK.`
3.
`It identifies if the API should expect a user authentication.`
4.
`It identifies if the API should accept microservice traffic.`
Q 16 / 61
1.
`application/json`
2.
`application/json_version2`
3.
`text/html`
4.
`application/vnd.myapp.v2+json`
Q 17 / 61
1.
`A token is encrypted.`
2.
`A token is encoded.`
3.
`A token is scoped to the use case.`
4.
`A token can be shared between systems.`
Q 18 / 61
1.
`stateless architecture`
2.
`idempotency`
3.
`a uniform interface`
4.
`cacheability`
Q 19 / 61
1.
`API proxy`
2.
`API gateway`
3.
`OpenAPI`
4.
`OAuth authorization server`
Q 20 / 61
1.
`transport over SSL`
2.
`encrypted payload`
3.
`a signature`
4.
`encoded payload`
Q 21 / 61
1.
`token`
2.
`scope`
3.
`claim`
4.
`back channel`
Q 22 / 61
1.
`ID token`
2.
`refresh token`
3.
`access token`
4.
`auth code token`
Q 23 / 61
1.
`no-proxy`
2.
`client-only`
3.
`restricted`
4.
`private`
Q 24 / 61
1.
`Authorization Code Grant`
2.
`Client Credentials Grant`
3.
`Implicit Grant`
4.
`Authentication Grant`
Q 25 / 61
1.
`It varies from API to API.`
2.
`admin`
3.
`write`
4.
`read-write`
Q 26 / 61
1.
`_embedded`
2.
`resources`
3.
`subresources`
4.
`_links`
Q 27 / 61
1.
`tracking downloads`
2.
`Accept headers`
3.
`user agents`
4.
`polling users`
Q 28 / 61
1.
`Layered System`
2.
`Stateless`
3.
`Client-Server`
4.
`Cacheable`
Q 29 / 61
1.
`your tech stack`
2.
`reasoning for your naming schema`
3.
`your mission statement`
4.
`sample code`
Q 30 / 61
1.
`Response Time`
2.
`Time to First Hello World`
3.
`TTL`
4.
`Uptime`
Q 31 / 61
1.
`GET /user/{id}`
2.
`GET /users/{id}`
3.
`GET /user?id={id}`
4.
`GET /users?id={id}`
Q 32 / 61
1.
`to describe relationships between resources or actions`
2.
`to describe subresources related to the current one`
3.
`to link two resources together`
4.
`to describe a resource and its purpose`
Q 33 / 61
1.
Java, Javascript, and .NET
2.
and you can support
3.
PHP, Python, and Go
4.
the languages that your target users use
Q 34 / 61
1.
`resources`
2.
`_embedded`
3.
`subresources`
4.
`_links`
Q 35 / 61
1.
an authorization framework for granted delegated access
2.
an approach to single sign-on for APIs
3.
a method for API authentication
4.
HTTP Basic Authentication 2.0
Q 36 / 61
1.
JSON
2.
HTTP
3.
common use cases
4.
your tech stack
Q 37 / 61
1.
to share user profile information
2.
to update an API configuration
3.
to keep a web session active
4.
to retrieve an access token
Q 38 / 61
1.
how long it takes for a developer to do something with your API
2.
how long it takes to start a new programming language
3.
how long it takes to install your SDK
4.
how long it takes to read your documentation
Q 39 / 61
1.
Cache-State: none
2.
Expires:-1
3.
Cache-Control: no-cache
4.
Cache-Control: no-store
Q 40 / 61
1.
`API gateway`
2.
`API logging `
3.
`a layered system `
4.
`API proxy`
Q 41 / 61
1.
`common knowledge`
2.
`URLs`
3.
`no versioning`
4.
`the Accept header`
Q 42 / 61
1.
`URL parameter`
2.
`Authorization header`
3.
`Base64 encoding`
4.
`Basic Auth`
Q 43 / 61
1.
`client`
2.
`not specified`
3.
`authorization server`
4.
`resource server`
Q 44 / 61
1.
`inbound traffic`
2.
`north-south traffic `
3.
`internal traffic `
4.
`east-west traffic`
Q 45 / 61
1.
`Add .json to the URL.`
2.
`APIs do not use XML.`
3.
`Use the Content-Type header.`
4.
`Use the Accept header.`
Q 46 / 61
1.
`403`
2.
`404`
3.
`401`
4.
`405`
Q 47 / 61
1.
`HTTP verbs`
2.
`JSON payloads`
3.
`HTTP response codes`
4.
`rate limiting/throttling`
Q 48 / 61
1.
`red team testing`
2.
`white box testing`
3.
`blue box testing`
4.
`black box testing`
Q 49 / 61
1.
`PUT`
2.
`POST`
3.
`GET`
4.
`OPTIONS`
Q 50 / 61
1.
`Expires: 1 minute`
2.
`Cache-Control: max-age=60`
3.
`Expires: 1 January 2020`
4.
`Cache-Expires: max-age=60`
Q 51 / 61
1.
`hypermedia`
2.
`link relations`
3.
`parsing`
4.
`browsing`
Q 52 / 61
1.
`200`
2.
`201`
3.
`204`
4.
`202`
Q 53 / 61
1.
AWS Lambda
2.
downloading open-source software
3.
Serverless
4.
JavaScript on a webpage
Q 54 / 61
1.
/companies/employees/{companyId}/{employeeId}
2.
/company/{companyId}/employees/{employeeId}
3.
/companies/{companyId}/employees/{employeeId}
4.
/companies/{companyId}/employee/{employeeId}
Q 55 / 61
1.
Stateless
2.
Cacheable
3.
Layered System
4.
Uniform Interface
Q 56 / 61
1.
FLUSH
2.
DELETE
3.
CLEAR
4.
DESTROY
Q 57 / 61
1.
DELETE
2.
GET
3.
PUT
4.
POST
Q 58 / 61
1.
Uniform Interface
2.
Cacheable
3.
Stateless
4.
Client-Server
Q 59 / 61
1.
Check you JSON structure.
2.
Check the API uptime status.
3.
Slow down your requests.
4.
Check you API key.
Q 60 / 61
1.
date-based filtering
2.
next/previous cursors
3.
page size and filters
4.
database IDs
Q 61 / 61