mediummulti selectObjective-mapped

A script authenticates to a controller API and receives a token that it presents in later requests. Which two statements about that token-based workflow are correct?

Question 1mediummulti select
Full question →

A script authenticates to a controller API and receives a token that it presents in later requests. Which two statements about that token-based workflow are correct?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Best answer

The token is often sent in an HTTP header in subsequent requests

Bearer or session tokens are commonly carried in headers.

B

Best answer

The token proves identity for that authenticated session or request set

It represents successful authentication and is then used for authorized API access.

C

Distractor review

The token changes the API from REST to SNMP

Authentication method does not change the management protocol.

D

Distractor review

The token must be stored in the router startup-config

API tokens are generally handled by applications, not router configs.

Common exam trap

Common exam trap: answer the scenario, not the keyword

A common exam trap is assuming that the presence of a token changes the network management protocol from REST to SNMP or another protocol. This is incorrect because token-based authentication is a security mechanism layered on top of the existing API protocol and does not alter it. Another trap is believing that tokens must be stored in the router’s startup-config, which is false since tokens are ephemeral credentials managed by client applications, not static device configurations. Misunderstanding these points can lead to selecting incorrect answers about token workflows in automation scenarios.

Technical deep dive

How to think about this question

Token-based authentication is a common method used in network automation and programmability to secure API interactions. After a client script authenticates to a controller API, the server issues a token that represents the authenticated session. This token is then included in subsequent API requests to prove the client's identity without resending credentials. This approach improves security and efficiency by limiting exposure of sensitive login information. In the context of Cisco network automation, the token is typically sent in an HTTP header, such as the Authorization header with a Bearer token scheme. This standard practice aligns with RESTful API design, where tokens act as temporary credentials that authorize access to network resources. The token validates that the client has already completed authentication and is permitted to perform specific API operations during that session. A common exam trap is confusing the token-based authentication method with changes to the underlying network management protocol. The token does not alter the API protocol itself (e.g., REST remains REST, not SNMP). Additionally, tokens are handled dynamically by client applications and are not stored in device configurations like the router startup-config. Understanding these distinctions is critical for correctly answering CCNA questions on automation and programmability.

KKey Concepts to Remember

  • A token issued after authentication acts as proof of identity for subsequent API requests during the same session.
  • Tokens are commonly included in HTTP headers, such as the Authorization header, to authenticate REST API calls.
  • Token-based authentication improves security by avoiding repeated transmission of user credentials in API requests.
  • The use of tokens does not change the underlying network management protocol, which remains REST in this context.
  • Tokens are managed by client applications and should not be stored in router startup-config files.
  • A valid token enables authorized access to network controller APIs without re-authenticating for each request.
  • Tokens typically have limited lifetimes and scopes, requiring renewal or re-authentication after expiration.
  • Automation scripts must securely handle tokens to prevent unauthorized access to network devices and controllers.

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.

Related practice questions

Related 200-301 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this 200-301 question test?

A token issued after authentication acts as proof of identity for subsequent API requests during the same session.

What is the correct answer to this question?

The correct answer is: The token is often sent in an HTTP header in subsequent requests — After authentication, many APIs issue a token that the client includes in later HTTP requests. That token acts as proof that the client already authenticated successfully.

What should I do if I get this 200-301 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.