hardMultiple Choice
200-901 Practice Question: Refer to the exhibit
Exhibit
Refer to the exhibit.
```json
{
"errorMessage": "Invalid auth token",
"statusCode": 401,
"details": "Token has expired"
}
```Refer to the exhibit. A developer receives this response from Cisco DNA Center API. What is the most likely cause and solution?
⚠ Common exam trap
Cisco often tests the distinction between HTTP 401 (authentication failure) and 403 (authorization failure) — candidates confuse these two status codes, especially when the question involves API tokens.
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 token is expired; generate a new one using /dna/system/api/v1/auth/token.
The HTTP 401 Unauthorized response indicates that the request lacks valid authentication credentials. In Cisco DNA Center API, tokens are short-lived (default 1 hour) and must be refreshed via POST /dna/system/api/v1/auth/token. The error is not about the endpoint, body syntax, or RBAC permissions — it specifically means the token used is expired or invalid.
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 token is expired; generate a new one using /dna/system/api/v1/auth/token.
Why this is correct
A 401 response from Cisco DNA Center indicates the authentication token has expired, since tokens are time-limited. Regenerating one via the /dna/system/api/v1/auth/token endpoint restores access, satisfying the requirement to re-authenticate before retrying the API call.
- ✗
The API path is incorrect; verify the endpoint URL.
Why it's wrong here
An incorrect path yields HTTP 404 with a resource-not-found body, while the exhibit indicates the request never authenticated. Verifying the endpoint URL is the right step when the API returns 404 or a routing error, not an authentication failure.
- ✗
The request body is malformed; check JSON syntax.
Why it's wrong here
A malformed JSON body returns HTTP 400 with a parse error naming the offending token or line, whereas the exhibit shows a 401/403-style authentication failure. JSON validation is the right check when the API rejects a syntactically invalid payload, not when credentials are refused.
- ✗
The user does not have permission; request admin to grant access.
Why it's wrong here
Permission errors surface as HTTP 403 with an authorisation message, not the credential-rejection status in the exhibit; a valid token lacking a role would show that. Requesting admin access is correct when an authenticated user is denied a specific API operation.
Quick reference
Access Control Model Comparison
| Model | Acronym | Who Controls Access? | Best For |
|---|---|---|---|
| Discretionary Access Control | DAC | Resource owner | Small teams, file shares |
| Mandatory Access Control | MAC | System / security labels | Classified govt / military |
| Role-Based Access Control | RBAC | Administrator (via roles) | Enterprise environments |
| Attribute-Based Access Control | ABAC | Policy engine (user + resource attributes) | Fine-grained, dynamic policies |
| Rule-Based Access Control | RuBAC | System rules / ACLs | Firewall rules, network ACLs |
Go deeper
Related to this question
About these practice questions
Courseiva writes every 200-901 question from scratch — 975 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. 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.