Question 71 of 504
Cloud Application SecurityeasyMultiple ChoiceObjective-mapped

Quick Answer

The correct answer is to use parameterized SQL queries. This security control prevents SQL injection by separating SQL logic from user-supplied data through placeholders, ensuring that any input, even if malicious, is treated strictly as data rather than executable code. On the Certified Cloud Security Professional CCSP exam, this concept tests your understanding of secure coding practices within cloud application security, often appearing in scenario-based questions where a log entry reveals an injection attempt. A common trap is to confuse input validation or stored procedures as sufficient alternatives, but parameterized queries are the definitive defense because they eliminate the possibility of syntax manipulation at the database layer. Remember the memory tip: “Placeholders prevent payloads”—when you see user input in a query, think of the placeholder as a shield that never lets the input touch the SQL command structure.

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.

Exhibit

Refer to the exhibit.

```
[ERROR] 2025-03-01 12:34:56,789 - myapp - CRITICAL - SQL Injection detected on endpoint /api/login
Input: ' OR '1'='1
```

Refer to the exhibit. A log entry shows a suspected SQL injection attack. Which security control would have prevented this attack?

Question 1easymultiple choice
Full question →

Exhibit

Refer to the exhibit.

```
[ERROR] 2025-03-01 12:34:56,789 - myapp - CRITICAL - SQL Injection detected on endpoint /api/login
Input: ' OR '1'='1
```

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

Use parameterized SQL queries

Option D is correct because SQL injection attacks exploit unsanitized user input that is concatenated into SQL queries. Parameterized queries (also known as prepared statements) separate SQL logic from data by using placeholders, ensuring that user input is always treated as data, not executable code. This prevents an attacker from injecting malicious SQL commands, regardless of the input content.

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.

  • Encrypt the database connection

    Why it's wrong here

    Encryption protects data in transit, not from injection.

  • Implement rate limiting on the login endpoint

    Why it's wrong here

    Rate limiting slows brute force, not injection.

  • Enforce strong password policies

    Why it's wrong here

    Password policies do not affect SQL injection.

  • Use parameterized SQL queries

    Why this is correct

    Parameterized queries prevent injection by treating input as data.

    Related concept

    Read the scenario before looking for a memorised answer.

Common exam traps

Common exam trap: answer the scenario, not the keyword

ISC2 often tests the distinction between network-layer controls (like encryption) and application-layer controls (like input validation), and the trap here is that candidates confuse encryption of the connection with prevention of injection, thinking encrypted traffic cannot carry malicious payloads.

Detailed technical explanation

How to think about this question

Under the hood, parameterized queries work by sending the SQL statement template and the parameters separately to the database server, which compiles the template once and binds the parameters later. This ensures that even if a parameter contains characters like single quotes or semicolons, they are treated as literal string data, not as SQL syntax. In a real-world scenario, a developer might mistakenly use string concatenation with user input in a dynamic query builder, and only a code review or static analysis tool would catch the flaw before deployment.

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 security team runs a vulnerability scan on a web application and discovers an unpatched SQL injection flaw. The team prioritises remediation by CVSS score — critical flaws are patched within 24 hours, high within 7 days. Questions like this test whether you understand vulnerability management processes, scanning tools, and remediation prioritisation.

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 CCSP 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 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: Use parameterized SQL queries — Option D is correct because SQL injection attacks exploit unsanitized user input that is concatenated into SQL queries. Parameterized queries (also known as prepared statements) separate SQL logic from data by using placeholders, ensuring that user input is always treated as data, not executable code. This prevents an attacker from injecting malicious SQL commands, regardless of the input content.

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.

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

Same concept, more angles

1 more ways this is tested on CCSP

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. A financial services company uses a multi-region cloud deployment for its trading application. The application consists of a web frontend, a REST API, and a relational database. Recently, a penetration test revealed that an attacker could perform a time-based blind SQL injection through the API's search functionality. The injection allows the attacker to enumerate database contents by observing response times. The development team was already aware of the issue but had prioritized other features. The security team now demands immediate remediation. The application is critical and cannot be taken offline. Which of the following is the most effective immediate action to mitigate the risk without modifying the application code?

hard
  • A.Deploy a Web Application Firewall (WAF) with a rule to block SQL injection patterns
  • B.Implement rate limiting on the API endpoint
  • C.Enable DDoS protection on the cloud load balancer
  • D.Enable transparent data encryption (TDE) on the database

Why A: A WAF can inspect incoming HTTP requests and block those matching SQL injection patterns (e.g., SQL keywords, special characters) without modifying application code. Since the vulnerability is a time-based blind SQL injection, a WAF with a dedicated SQL injection rule set can immediately stop the attack vector by filtering malicious payloads at the edge, providing a virtual patch while the code fix is developed. This is the only option that directly addresses the injection vector without requiring code changes or downtime.

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 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.