Question 351 of 500
AI Implementation and OperationseasyMultiple ChoiceObjective-mapped

Quick Answer

The correct answer is to use an API key or bearer token in the HTTP header, as this is the standard mechanism for authenticating and authorizing client applications invoking a REST API. These tokens, such as OAuth 2.0 access tokens, are passed in the Authorization header, allowing the server to verify the client’s identity and permissions before processing requests containing sensitive customer data. On the CompTIA AI+ AI0-001 exam, this concept tests your understanding of securing AI REST API endpoints against unauthorized access, often appearing in scenario-based questions where a model handles PII or financial data. A common trap is confusing authentication with encryption—remember that tokens prove identity, while HTTPS protects data in transit. For a quick memory tip, think “Header, not body”: tokens always ride in the HTTP header, never in the URL or request body.

AI0-001 AI Implementation and Operations Practice Question

This AI0-001 practice question tests your understanding of ai implementation and operations. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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 company deploys an AI model via a REST API that handles sensitive customer data. To secure the endpoint, the security team requires that only authenticated and authorized applications can invoke the API. Which mechanism should be implemented?

Question 1easymultiple choice
Full question →

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

API key or bearer token in the HTTP header

Option A is correct because API keys or bearer tokens (e.g., OAuth 2.0 access tokens) are the standard mechanism for authenticating and authorizing client applications when invoking a REST API. These tokens are passed in the HTTP Authorization header, allowing the server to verify the client's identity and permissions before processing requests containing sensitive customer data.

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.

  • API key or bearer token in the HTTP header

    Why this is correct

    API keys/tokens authenticate the caller and are standard for API security.

    Related concept

    Read the scenario before looking for a memorised answer.

  • TLS encryption for the connection

    Why it's wrong here

    TLS encrypts data, but does not authenticate the client.

  • Input sanitization to prevent injection

    Why it's wrong here

    Input sanitization prevents code injection, not authentication.

  • IP whitelisting

    Why it's wrong here

    IP whitelisting allows any request from a trusted IP, but does not authenticate individual applications.

Common exam traps

Common exam trap: answer the scenario, not the keyword

CompTIA often tests the distinction between transport-layer security (TLS) and application-layer authentication, so candidates mistakenly choose TLS because it 'secures' the endpoint, but it does not verify who is calling the API.

Detailed technical explanation

How to think about this question

Bearer tokens are defined in RFC 6750 and are typically issued by an OAuth 2.0 authorization server after the client application authenticates (e.g., using client credentials grant). The token is a cryptographically signed string (often a JWT) that contains claims about the client's identity and scopes, which the API gateway or service validates by checking the signature and expiry. In production, tokens should be short-lived and rotated, and the API should reject requests without a valid token in the Authorization header.

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 junior network technician can log in to a core router but cannot reach the enable prompt or configuration mode. The AAA server is authenticating the login — but the authorisation policy only grants privilege level 1, not 15. Authentication (who you are) is working; authorisation (what you can do) is not.

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.

Related practice questions

Related AI0-001 practice-question pages

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

Practice this exam

Start a free AI0-001 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this AI0-001 question test?

AI Implementation and Operations — This question tests AI Implementation and Operations — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: API key or bearer token in the HTTP header — Option A is correct because API keys or bearer tokens (e.g., OAuth 2.0 access tokens) are the standard mechanism for authenticating and authorizing client applications when invoking a REST API. These tokens are passed in the HTTP Authorization header, allowing the server to verify the client's identity and permissions before processing requests containing sensitive customer data.

What should I do if I get this AI0-001 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 →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 30, 2026

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.

Loading comments…

Sign in to join the discussion.

This AI0-001 practice question is part of Courseiva's free CompTIA 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 AI0-001 exam.