The correct answer is to embed the version in the URI, such as /v1/resource, because this approach makes the API version explicit and immediately visible to any client, eliminating the need for special header handling or query parameter parsing. By placing the version directly in the URI path, you ensure backward compatibility since older endpoints remain accessible under their original URLs, a practice widely adopted by major APIs like GitHub and Twilio. On the Cisco DevNet Associate 200-901 exam, this question tests your understanding of RESTful design principles and the trade-offs between URI, header, and query parameter versioning; a common trap is assuming custom headers are more RESTful, but the exam emphasizes simplicity and discoverability. Remember the memory tip: “Version in the path, never the wrath” — keeping the version in the URI avoids client-side complexity and aligns with industry standards for straightforward API evolution.
200-901 Software Development and Design Practice Question
This 200-901 practice question tests your understanding of software development and design. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A developer is designing a REST API that will be used by multiple client applications. The API must support versioning to ensure backward compatibility. Which approach should the developer use to implement API versioning?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Embed the version in the URI, e.g., /v1/resource
Embedding the version in the URI (e.g., /v1/resource) is the most common and straightforward approach for REST API versioning. It makes the version explicit in the URL, allowing clients to directly target a specific version without requiring special header handling or query parameter parsing. This method is widely adopted in industry APIs (e.g., GitHub, Twilio) and ensures backward compatibility by keeping older endpoints accessible under their original URI path.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Embed the version in the URI, e.g., /v1/resource
Why this is correct
Correct: URI versioning is straightforward and widely adopted.
Related concept
Read the scenario before looking for a memorised answer.
✗
Use different HTTP methods for different versions
Why it's wrong here
Incorrect: HTTP methods are not designed for versioning.
✗
Pass the version as a query parameter, e.g., ?version=1
Why it's wrong here
Incorrect: Query parameters can be cached and may cause issues with proxies.
✗
Use a custom HTTP header to specify the version
Why it's wrong here
Incorrect: Custom headers are less discoverable and may not be supported by all clients.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the misconception that query parameters or custom headers are more 'RESTful' or flexible, but the exam expects URI-based versioning as the simplest and most compatible approach for backward compatibility.
Detailed technical explanation
How to think about this question
URI-based versioning leverages the fact that URLs are unique identifiers for resources; changing the version prefix effectively creates a new resource path, which can be independently cached, routed, and documented. Under the hood, web servers or API gateways can use URL rewriting or reverse proxy rules (e.g., Nginx location blocks) to route /v1/resource to a specific backend service, while /v2/resource goes to another, enabling seamless blue-green deployments. A real-world scenario where this matters is when a mobile app is still using an older API version; the server can keep /v1/resource active indefinitely while newer clients use /v2/resource.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Software Development and Design — This question tests Software Development and Design — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Embed the version in the URI, e.g., /v1/resource — Embedding the version in the URI (e.g., /v1/resource) is the most common and straightforward approach for REST API versioning. It makes the version explicit in the URL, allowing clients to directly target a specific version without requiring special header handling or query parameter parsing. This method is widely adopted in industry APIs (e.g., GitHub, Twilio) and ensures backward compatibility by keeping older endpoints accessible under their original URI path.
What should I do if I get this 200-901 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This 200-901 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 200-901 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.