Question 20 of 504
Cloud Application SecurityhardMultiple SelectObjective-mapped

Quick Answer

The answer is disabling unused URL schemes and whitelisting outbound destinations. These two methods directly counter SSRF by limiting an attacker’s ability to manipulate server-side requests. Disabling schemes like file:// and dict:// removes dangerous protocols that could read local files or interact with internal services, while whitelisting ensures the application only connects to pre-approved external hosts, preventing redirection to internal IPs or cloud metadata endpoints. On the Certified Cloud Security Professional CCSP exam, this question tests your grasp of cloud-specific SSRF defenses, often appearing in the Cloud Platform and Infrastructure Security domain. A common trap is assuming input validation alone suffices—attackers easily bypass filters with encoding or redirects. Remember the mnemonic “D.W.”: Disable unused schemes, Whitelist destinations—two locks on the same door.

CCSP Cloud Application Security Practice Question

This CCSP practice question tests your understanding of cloud application security. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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 effective methods to protect against server-side request forgery (SSRF) in a cloud application? (Choose two.)

Question 1hardmulti select
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

Whitelist allowed outbound destinations

Option B is correct because whitelisting allowed outbound destinations is a primary defense against SSRF. By explicitly permitting only trusted external hosts (e.g., specific API endpoints or internal services), the application cannot be tricked into making requests to arbitrary internal or external targets, even if an attacker controls the URL parameter.

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.

  • Use SSL inspection to check for malicious payloads

    Why it's wrong here

    SSL inspection does not prevent SSRF.

  • Whitelist allowed outbound destinations

    Why this is correct

    Whitelisting prevents requests to internal or malicious hosts.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Block all outbound network traffic from the application

    Why it's wrong here

    Blocking all outbound may break functionality.

  • Disable unused URL schemes such as file:// and dict://

    Why this is correct

    Disabling uncommon schemes reduces attack surface.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Sanitize all user input for URL parameters

    Why it's wrong here

    Input validation can be bypassed; defense in depth needed.

Common exam traps

Common exam trap: answer the scenario, not the keyword

ISC2 often tests the misconception that input sanitization alone is sufficient for SSRF protection, when in reality the attack exploits the server's trust in the destination, not the input format, making whitelisting and scheme restrictions the effective controls.

Detailed technical explanation

How to think about this question

SSRF exploits occur when an application fetches a remote resource based on user-supplied URLs without validating the target. Whitelisting leverages network-layer controls (e.g., security groups, egress firewalls, or proxy rules) to restrict outbound connections to only known, safe hosts. Disabling unused URL schemes (e.g., file://, dict://, gopher://) prevents attackers from accessing local files or internal services via non-HTTP protocols, which is a common SSRF vector in cloud environments where metadata services (e.g., AWS 169.254.169.254) are targeted.

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

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: Whitelist allowed outbound destinations — Option B is correct because whitelisting allowed outbound destinations is a primary defense against SSRF. By explicitly permitting only trusted external hosts (e.g., specific API endpoints or internal services), the application cannot be tricked into making requests to arbitrary internal or external targets, even if an attacker controls the URL parameter.

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

Keep practising

More CCSP practice questions

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.