Question 1mediummultiple choice
Full question →mediummultiple choiceObjective-mapped
An automation script needs to send a bearer token when calling a controller REST API over HTTPS. Where is that token most commonly included?
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
In the HTTP Authorization header
That is the standard way bearer tokens are presented.
B
Distractor review
In the Ethernet trailer
Tokens are an application-layer concept, not a Layer 2 trailer field.
C
Distractor review
In the DNS response section
DNS is unrelated to REST API authorization.
D
Distractor review
In the TCP checksum field
Transport checksums do not carry application tokens.
Common exam trap
Common exam trap: answer the scenario, not the keyword
A frequent exam trap is selecting options that place bearer tokens in lower-layer protocol fields such as the Ethernet trailer or TCP checksum field. These fields operate at Layer 2 and Layer 4 respectively and do not carry application-layer authentication data. Another tempting mistake is thinking DNS responses can include bearer tokens, but DNS is unrelated to REST API authentication. Candidates may incorrectly assume tokens are embedded in transport or network layer fields, but bearer tokens are strictly an HTTP header concept. Misunderstanding this layering principle leads to incorrect answers and confusion about how REST API security works in Cisco automation contexts.
Technical deep dive
How to think about this question
Bearer tokens are a form of access token used in REST API authentication to prove the identity of the client making the request. These tokens are typically generated by an authentication server and must be included in each API request to authorize access to protected resources. The HTTP Authorization header is the standardized method for transmitting bearer tokens, using the syntax 'Authorization: Bearer <token>'. This header is part of the HTTP protocol, which REST APIs use as their transport layer, making it the logical and secure place to include authentication credentials. The decision to place bearer tokens in the HTTP Authorization header follows the REST architectural style and HTTP standards. This approach separates authentication data from the message body and URL parameters, reducing the risk of token leakage through logs or caches. Cisco network automation scripts that interact with controller REST APIs must adhere to this standard to ensure successful authentication and authorization. Using HTTPS encrypts the entire HTTP message, including headers, protecting the bearer token from interception during transmission. A common exam trap is confusing bearer token placement with lower-layer protocol fields like Ethernet trailers or TCP checksum fields, which do not carry application-layer data. Another mistake is assuming DNS responses can carry authentication tokens, which they cannot since DNS is unrelated to REST API security. Practically, placing tokens outside the Authorization header leads to failed authentication and potential security risks. Understanding this distinction is critical for Cisco automation tasks and passing the CCNA exam questions on REST API security fundamentals.
KKey Concepts to Remember
- Bearer tokens are included in the HTTP Authorization header to authenticate REST API requests securely over HTTPS.
- The HTTP Authorization header uses the format 'Authorization: Bearer <token>' to clearly indicate the token type and value.
- Tokens are application-layer credentials and must not be placed in lower-layer fields like Ethernet trailers or TCP checksum fields.
- DNS responses do not carry authentication tokens because DNS operates at the application layer but is unrelated to REST API security.
- REST APIs rely on HTTP headers for passing authentication tokens to maintain separation of concerns and secure communication.
- Including bearer tokens in the HTTP Authorization header ensures compatibility with standard REST API authentication mechanisms.
- Automation scripts interacting with network controllers must use the Authorization header to properly authenticate API calls.
- Misplacing bearer tokens in non-HTTP fields can cause authentication failures and security vulnerabilities in network automation.
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.
CCNA subnetting practice questions
Practise IPv4 subnetting, CIDR, masks, host ranges and subnet selection.
CCNA OSPF practice questions
Practise OSPF neighbours, router IDs, metrics, areas and routing-table interpretation.
CCNA VLAN practice questions
Practise VLANs, access ports, trunks, allowed VLANs and switching scenarios.
CCNA STP practice questions
Practise spanning tree, root bridge election, port roles and STP troubleshooting.
CCNA EtherChannel practice questions
Practise LACP, PAgP, port-channel behaviour and bundle requirements.
CCNA ACL practice questions
Practise standard and extended ACLs, permit/deny logic and traffic filtering.
CCNA NAT practice questions
Practise static NAT, dynamic NAT, PAT and inside/outside address translation.
CCNA DHCP practice questions
Practise DHCP scopes, relay, leases and troubleshooting.
CCNA show ip route practice questions
Practise routing-table output, longest-prefix match, AD and route selection.
CCNA show interfaces trunk practice questions
Practise trunk verification and VLAN forwarding across switches.
CCNA wireless security practice questions
Practise WLAN security, authentication and wireless architecture concepts.
CCNA IPv6 practice questions
Practise IPv6 addressing, routes, neighbour discovery and common IPv6 exam traps.
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.
Question 1
A router learns the same prefix from both OSPF and EIGRP. Which route is installed by default?
Question 2
A router shows this output: R1#show ip ospf neighbor Neighbor ID Pri State Dead Time Address Interface 10.1.1.2 1 FULL/DR 00:00:34 192.168.12.2 GigabitEthernet0/0 10.1.1.3 1 2WAY/DROTHER 00:00:39 192.168.12.3 GigabitEthernet0/0 Which statement is correct?
Question 3
What is the OSPF metric called?
Question 4
A non-root switch has two uplinks toward the root bridge. One path has a lower total STP cost than the other. What role will the lower-cost uplink have?
Question 5
A router interface applies this ACL inbound: 10 deny tcp any any eq 80 20 permit ip any any A user reports that web browsing to a server by IP address fails, but ping works. Which statement best explains the behavior?
Question 6
A router learns route 198.51.100.0/24 from OSPF with AD 110 and also has a static route to the same prefix configured with AD 150. Which route is installed?
FAQ
Questions learners often ask
What does this 200-301 question test?
Bearer tokens are included in the HTTP Authorization header to authenticate REST API requests securely over HTTPS.
What is the correct answer to this question?
The correct answer is: In the HTTP Authorization header — Bearer tokens are typically sent in the HTTP Authorization header. Query parameters or request bodies may carry credentials in some custom APIs, but the normal REST pattern is an Authorization header such as 'Authorization: Bearer <token>'.
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.