API versioning for services in Microservices - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the API version in the URL path.

Microservices

GET /api/[1]/users

Drag options to blanks, or click blank then click option'

Aversion1

Bapi1

Cv1

Dservice1

Attempts:

3 left

💡 Hint

Common Mistakes

Using long or unclear version names in the URL path.

Not including the version in the URL at all.

The standard way to version REST APIs is to include the version in the URL path, such as /api/v1/.

2fill in blank

medium

Complete the code to specify the API version using a custom HTTP header.

Microservices

X-API-Version: [1]

Drag options to blanks, or click blank then click option'

Aservice_v1

Bversion1

Capi_version_1

Dv1

Attempts:

3 left

💡 Hint

Common Mistakes

Using long descriptive strings in headers.

Confusing header names with version values.

When using headers for versioning, a short version string like v1 is common and clear.

3fill in blank

hard

Fix the error in the versioning strategy by choosing the correct versioning method.

Microservices

API versioning is done by [1] the API endpoint URL.

Drag options to blanks, or click blank then click option'

Aembedding

Bignoring

Chiding

Dremoving

Attempts:

3 left

💡 Hint

Common Mistakes

Not including version info in the API URL.

Removing version info from requests.

Embedding the version in the URL is a clear and scalable way to version APIs.

4fill in blank

hard

Fill both blanks to complete the API versioning strategy using query parameters.

Microservices

GET /users?[1]=[2]

Drag options to blanks, or click blank then click option'

Aversion

Bv

C1

Dapi

Attempts:

3 left

💡 Hint

Common Mistakes

Using unclear parameter names.

Using complex version values.

Using a query parameter like version=1 is a common way to version APIs via query strings.

5fill in blank

hard

Fill all three blanks to complete the code for content negotiation versioning using the Accept header.

Microservices

Accept: application/[1].v[2]+[3]

Drag options to blanks, or click blank then click option'

Ajson

B2

Cxml

Djsonapi

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing media types incorrectly.

Using invalid version formats.

Content negotiation uses the Accept header with media types like application/json.v2+jsonapi to specify version and format.