- A
API keys in URLs are often logged in plaintext in server logs and browser history.
Logging exposes the key to anyone with log access.
- B
API keys in query strings are not encrypted, even with HTTPS.
Why wrong: HTTPS encrypts the entire request, but URL can appear in logs before encryption is applied.
- C
API keys provide weak authentication because they are not tied to a user session.
Why wrong: The main issue is exposure, not strength.
- D
API keys are not valid for use in query strings; they require a certificate.
Why wrong: They can be used in query strings, but it's insecure.
CCSP Cloud Application Security Practice Question
This CCSP practice question tests your understanding of cloud application security. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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 cloud security engineer is reviewing the authentication mechanism for a web application. The application currently uses API keys transmitted in the URL query string. What is the primary security concern with this approach?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"primary"Why it matters: Asks for the main purpose or function, not a secondary benefit. Eliminate answers that describe side-effects or partial functions.
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 keys in URLs are often logged in plaintext in server logs and browser history.
The primary security concern with transmitting API keys in URL query strings is that URLs are frequently logged in plaintext by web servers, proxies, and browsers. This means the API key can be inadvertently exposed in server access logs, browser history, and referrer headers, making it accessible to anyone with access to those logs. Even with HTTPS encrypting the data in transit, the URL itself is often logged before decryption or after encryption at the termination point, so the key remains visible in log files.
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 keys in URLs are often logged in plaintext in server logs and browser history.
Why this is correct
Logging exposes the key to anyone with log access.
Clue confirmation
The clue word "primary" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
API keys in query strings are not encrypted, even with HTTPS.
Why it's wrong here
HTTPS encrypts the entire request, but URL can appear in logs before encryption is applied.
- ✗
API keys provide weak authentication because they are not tied to a user session.
Why it's wrong here
The main issue is exposure, not strength.
- ✗
API keys are not valid for use in query strings; they require a certificate.
Why it's wrong here
They can be used in query strings, but it's insecure.
Common exam traps
Common exam trap: answer the scenario, not the keyword
ISC2 often tests the misconception that HTTPS fully protects the URL from all exposure, but the trap here is that while HTTPS encrypts data in transit, it does not prevent logging, caching, or referrer leakage of the URL.
Detailed technical explanation
How to think about this question
Under the hood, when a request is made over HTTPS, the TLS layer encrypts the entire HTTP message, including the URL path and query string. However, many web servers and load balancers log the full URL before encryption (at the client side) or after decryption (at the server side), and browser history stores the URL in plaintext. Additionally, the HTTP Referer header may leak the API key when the page makes subsequent requests to other origins. RFC 3986 defines URI syntax, and security best practices (e.g., OWASP ASVS) explicitly warn against placing secrets in URLs due to these logging and caching risks.
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 developer is choosing between AES-256 (symmetric) and RSA-2048 (asymmetric) for encrypting a large file that will be sent to a partner. Symmetric encryption is fast but requires key exchange; asymmetric is slower but solves the key distribution problem. A hybrid approach — encrypt the file with AES, encrypt the AES key with RSA — is standard. Questions like this test whether you understand when each approach applies.
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.
- →
Cloud Application Security — study guide chapter
Learn the concepts, then practise the questions
- →
Cloud Application Security practice questions
Targeted practice on this topic area only
- →
All CCSP questions
504 questions across all exam domains
- →
Certified Cloud Security Professional CCSP study guide
Full concept coverage aligned to exam objectives
- →
CCSP practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related CCSP practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Cloud Application Security practice questions
Practise CCSP questions linked to Cloud Application Security.
Cloud Security Operations practice questions
Practise CCSP questions linked to Cloud Security Operations.
Legal, Risk and Compliance practice questions
Practise CCSP questions linked to Legal, Risk and Compliance.
Cloud Concepts, Architecture and Design practice questions
Practise CCSP questions linked to Cloud Concepts, Architecture and Design.
Cloud Platform and Infrastructure Security practice questions
Practise CCSP questions linked to Cloud Platform and Infrastructure Security.
Cloud Data Security practice questions
Practise CCSP questions linked to Cloud Data Security.
CCSP fundamentals practice questions
Practise CCSP questions linked to CCSP fundamentals.
CCSP scenario practice questions
Practise CCSP questions linked to CCSP scenario.
CCSP troubleshooting practice questions
Practise CCSP questions linked to CCSP troubleshooting.
Practice this exam
Start a free CCSP 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 CCSP question test?
Cloud Application Security — This question tests Cloud Application Security — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: API keys in URLs are often logged in plaintext in server logs and browser history. — The primary security concern with transmitting API keys in URL query strings is that URLs are frequently logged in plaintext by web servers, proxies, and browsers. This means the API key can be inadvertently exposed in server access logs, browser history, and referrer headers, making it accessible to anyone with access to those logs. Even with HTTPS encrypting the data in transit, the URL itself is often logged before decryption or after encryption at the termination point, so the key remains visible in log files.
What should I do if I get this CCSP question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "primary". Asks for the main purpose or function, not a secondary benefit. Eliminate answers that describe side-effects or partial functions.
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 →
Last reviewed: Jun 30, 2026
This CCSP practice question is part of Courseiva's free ISC2 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 CCSP exam.
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.
Sign in to join the discussion.