Quick Answer
The answer is to validate and sanitize all input and implement rate limiting. Input validation prevents injection attacks like SQLi or XSS by ensuring only expected data reaches the API, while rate limiting controls request frequency to block brute-force and denial-of-service attempts. On the CCSP exam, these two controls are frequently paired because they address distinct layers of the API attack surface: one protects data integrity and the other preserves availability. A common trap is choosing encryption alone, which secures data in transit but does not prevent abuse or malformed payloads. Remember the mnemonic “V.R.”—Validate input, then Rate-limit—to recall that you must first clean the data, then throttle the flow.
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.
Which TWO of the following are common best practices for securing cloud application APIs? (Choose two.)
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "best"
Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
Implement rate limiting
Rate limiting prevents DDoS and brute force.
Validate and sanitize all input
Input validation prevents injection attacks.
Disable HTTPS to reduce latency
Why wrong: HTTPS is essential for confidentiality and integrity.
Return detailed error messages for debugging
Why wrong: Detailed errors can aid attackers.
Allow all origins with CORS
Why wrong: CORS should be restricted to trusted origins.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Implement rate limiting
Rate limiting is a critical best practice for securing cloud application APIs because it prevents abuse by limiting the number of requests a client can make within a specific time window. This mitigates brute-force attacks, denial-of-service (DoS) attacks, and resource exhaustion. By enforcing rate limits, the API maintains availability and protects backend services from being overwhelmed.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Implement rate limiting
Why this is correct
Rate limiting prevents DDoS and brute force.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
Validate and sanitize all input
Why this is correct
Input validation prevents injection attacks.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
Disable HTTPS to reduce latency
Why it's wrong here
HTTPS is essential for confidentiality and integrity.
Return detailed error messages for debugging
Why it's wrong here
Detailed errors can aid attackers.
Allow all origins with CORS
Why it's wrong here
CORS should be restricted to trusted origins.
Common exam traps
ISC2 often tests the misconception that disabling HTTPS improves performance for cloud APIs, but the correct priority is always encryption for data in transit, even at the cost of slight latency.
Detailed technical explanation
Rate limiting is often implemented using token bucket or leaky bucket algorithms, with headers like X-RateLimit-Limit and Retry-After to communicate limits to clients. In cloud environments, rate limiting can be applied at the API gateway (e.g., AWS API Gateway, Azure API Management) or via web application firewalls (WAFs) to enforce policies per API key or IP address. A real-world scenario is GitHub's API rate limiting, which restricts unauthenticated requests to 60 per hour to prevent scraping and ensure fair usage.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A security analyst at a medium-sized enterprise encounters this scenario during an investigation or architecture review. The correct answer reflects best practice for the specific threat or control described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Security exam questions test whether you can match controls to threats in context — not just recall definitions.
What to study next
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
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise CCSP questions linked to Cloud Application Security.
Practise CCSP questions linked to Cloud Security Operations.
Practise CCSP questions linked to Legal, Risk and Compliance.
Practise CCSP questions linked to Cloud Concepts, Architecture and Design.
Practise CCSP questions linked to Cloud Platform and Infrastructure Security.
Practise CCSP questions linked to Cloud Data Security.
Practise CCSP questions linked to CCSP fundamentals.
Practise CCSP questions linked to CCSP scenario.
Practise CCSP questions linked to CCSP troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Cloud Application Security — This question tests Cloud Application Security — Read the scenario before looking for a memorised answer..
The correct answer is: Implement rate limiting — Rate limiting is a critical best practice for securing cloud application APIs because it prevents abuse by limiting the number of requests a client can make within a specific time window. This mitigates brute-force attacks, denial-of-service (DoS) attacks, and resource exhaustion. By enforcing rate limits, the API maintains availability and protects backend services from being overwhelmed.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Yes — watch for: "best". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
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.