mediumMultiple Choice
200-901 Practice Question: Needs to automate the deployment of QoS policies…
A network engineer needs to automate the deployment of QoS policies across multiple campus switches using Cisco DNA Center. The engineer decides to use the Cisco DNA Center Intent API to create a policy tag and bind it to a group of devices. After sending the PUT request to /dna/intent/api/v1/policy-tag, the API returns a 202 Accepted status. However, the engineer notices that the policy is not being applied consistently across all devices. What is the most likely reason?
⚠ Common exam trap
Cisco often tests the distinction between synchronous (2xx success) and asynchronous (202 Accepted) responses, and the trap here is that candidates assume a 202 Accepted means the operation completed successfully, when in fact it only means the request was accepted for processing.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The request was asynchronous, and the engineer did not check the task status for completion.
The 202 Accepted status indicates that the request was accepted for asynchronous processing, not that it has completed. Cisco DNA Center Intent API uses asynchronous tasks for operations like policy tag binding, and the engineer must poll the task status endpoint to verify completion and success. Without checking the task status, the engineer cannot know if the policy was applied consistently across all devices, as some tasks may have failed or are still in progress.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The payload was not in JSON format, causing a silent failure.
Why it's wrong here
Malformed JSON yields a 400 Bad Request, not 202 Accepted, so the payload parsed and was queued. It is tempting because silent failures do occur with schema mismatches, but Cisco DNA Center validates JSON structure before accepting, so the inconsistency arises from asynchronous task completion across devices.
- ✗
The API token expired before the request was processed.
Why it's wrong here
A 202 Accepted confirms the token authenticated the request; the token cannot expire mid-processing to cause partial application. It is tempting because expired credentials do cause 401 errors, but here the asynchronous job was queued successfully, so the inconsistency stems from device reachability or tag-binding scope instead.
- ✓
The request was asynchronous, and the engineer did not check the task status for completion.
Why this is correct
The 202 Accepted response confirms the Intent API processed the request asynchronously, returning a task ID rather than applying the policy immediately. Without polling that task status, the engineer cannot confirm completion, so binding may still be pending on some devices.
- ✗
The engineer used an incorrect API endpoint for policy tags.
Why it's wrong here
A 202 Accepted means the request was queued and validated, so an incorrect endpoint would have returned 404 or 400 instead; inconsistent application points to asynchronous task failure or device reachability, not the URL. Tempting because endpoint errors are a common automation fault, and it would be correct if the API had rejected the path outright.
Go deeper
Related to this question
About these practice questions
One of 975 original 200-901 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.