You have an API with versions /v1 and /v2. Version 2 changes the user object by renaming 'username' to 'user_name'. How can you design the API to avoid breaking clients using /v1?

hard📝 Application Q8 of 15

Rest API - Versioning Strategies

ARename the field in /v1 and /v2 simultaneously

BKeep /v1 unchanged and implement the rename only in /v2

CRemove /v1 and force all clients to use /v2

DUse a query parameter to switch field names dynamically

Step-by-Step Solution

Solution:

Step 1: Understand version isolation for field changes
Changing field names in a new version should not affect old versions to avoid breaking clients.
Step 2: Apply change only in new version
Keep /v1 with 'username' and rename to 'user_name' only in /v2 to maintain compatibility.
Final Answer:
Keep /v1 unchanged and implement the rename only in /v2 -> Option B
Quick Check:
Change fields only in new version = B [OK]

Quick Trick: Apply breaking changes only in new API versions [OK]

Common Mistakes:

Changing old versions simultaneously
Removing old versions abruptly
Using query parameters for field renaming

Master "Versioning Strategies" in Rest API

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

More Rest API Quizzes

You have an API with versions /v1 and /v2. Version 2 changes the user object by renaming 'username' to 'user_name'. How can you design the API to avoid breaking clients using /v1?

Step 1: Understand version isolation for field changes

Step 2: Apply change only in new version

Final Answer:

Quick Check:

Want More Practice?