The correct answer is that the `aws:SourceIp` condition key does not apply to API calls made through the AWS Management Console because the console uses AWS-owned IP addresses, not the user’s actual source IP. When a user interacts with the console, the console makes API calls on their behalf from AWS service endpoints, so the `IpAddress` condition never matches the corporate network range (10.0.0.0/8). This means the Allow effect never triggers, but because the console’s requests originate from AWS IPs, the condition is effectively bypassed—users can still perform EC2 actions from outside the corporate network, often due to other permissive policies or the console’s inherent behavior. On the SCS-C02 exam, this tests your understanding of IAM condition key limitations, a common trap where engineers mistakenly apply `aws:SourceIp` to console-based access without realizing it only works for direct API or CLI calls. Memory tip: “Console calls from AWS IPs, not your IPs—SourceIp won’t clip.”
SCS-C02 Infrastructure Security Practice Question
This SCS-C02 practice question tests your understanding of infrastructure 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.
Refer to the exhibit. A security engineer finds the above IAM policy attached to an IAM group. The policy is intended to allow all EC2 actions only from the corporate network (10.0.0.0/8). However, users report that they can perform EC2 actions from outside the corporate network. What is the MOST likely reason?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The aws:SourceIp condition key does not apply to API calls made through the AWS Management Console; the console uses AWS IP addresses.
Option C is correct because the `aws:SourceIp` condition key does not evaluate the source IP of requests made through the AWS Management Console. When a user signs in to the console, the console makes API calls on their behalf using AWS service endpoints, which have AWS-owned IP addresses, not the user's corporate IP. Therefore, the condition `IpAddress` fails, and the policy denies console-based EC2 actions from the corporate network, but the policy actually allows all EC2 actions (since the default effect is Allow) when the condition is not met? Wait—the policy has an Allow effect with a condition; if the condition is not met, the Allow does not apply, but there is no explicit Deny, so other policies or the default implicit Deny would block the action. However, the question states users can perform EC2 actions from outside the corporate network, meaning the policy is not blocking them. The most likely reason is that the console uses AWS IP addresses, so the condition never matches, and the Allow never applies, but users are still able to perform actions because they are using the console? Actually, the console uses AWS IPs, so the condition `IpAddress` would not match, and the Allow would not apply, leading to implicit Deny—but users report they can perform actions. This indicates that the policy is not the only one; perhaps there is another policy allowing EC2 actions without conditions (Option A). But the question asks for the MOST likely reason given the exhibit and the intent. The trap is that the `aws:SourceIp` condition does not work for console-based API calls because the console uses AWS IP addresses, so the condition is effectively ignored for console users, allowing them to bypass the intended restriction. This is a well-known limitation documented by AWS.
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.
✗
The IAM group has an additional policy that allows all EC2 actions without conditions.
Why it's wrong here
Incorrect: While possible, the most likely reason is the console IP issue, not additional policies.
✗
The policy allows access to all EC2 actions, but the condition only applies to the ec2:* actions, which includes all EC2 actions.
Why it's wrong here
Incorrect: The condition does apply to the allowed actions.
✓
The aws:SourceIp condition key does not apply to API calls made through the AWS Management Console; the console uses AWS IP addresses.
Why this is correct
Correct: Console API calls originate from AWS IPs, not the user's client IP, so the condition is ineffective.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
The policy should use a NotIpAddress condition instead of IpAddress.
Why it's wrong here
Incorrect: Using NotIpAddress would deny the specified range, which is not the issue.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume `aws:SourceIp` works universally for all API calls, but AWS explicitly documents that it does not apply to requests made through the AWS Management Console because the console uses AWS service IPs, not the user's client IP.
Detailed technical explanation
How to think about this question
The `aws:SourceIp` condition key evaluates the IP address of the principal making the API call, but for AWS Management Console requests, the console acts as a proxy, and the source IP seen by the service is an AWS internal IP (from the console's infrastructure). This is documented in the AWS IAM documentation under 'Using IP address conditions.' In practice, to restrict console access to a corporate network, you must use a different approach, such as an SCP or a network-level firewall like a VPN or AWS Client VPN, because IAM conditions cannot reliably restrict console access based on the user's client IP.
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 company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
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.
Infrastructure Security — This question tests Infrastructure Security — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The aws:SourceIp condition key does not apply to API calls made through the AWS Management Console; the console uses AWS IP addresses. — Option C is correct because the `aws:SourceIp` condition key does not evaluate the source IP of requests made through the AWS Management Console. When a user signs in to the console, the console makes API calls on their behalf using AWS service endpoints, which have AWS-owned IP addresses, not the user's corporate IP. Therefore, the condition `IpAddress` fails, and the policy denies console-based EC2 actions from the corporate network, but the policy actually allows all EC2 actions (since the default effect is Allow) when the condition is not met? Wait—the policy has an Allow effect with a condition; if the condition is not met, the Allow does not apply, but there is no explicit Deny, so other policies or the default implicit Deny would block the action. However, the question states users can perform EC2 actions from outside the corporate network, meaning the policy is not blocking them. The most likely reason is that the console uses AWS IP addresses, so the condition never matches, and the Allow never applies, but users are still able to perform actions because they are using the console? Actually, the console uses AWS IPs, so the condition `IpAddress` would not match, and the Allow would not apply, leading to implicit Deny—but users report they can perform actions. This indicates that the policy is not the only one; perhaps there is another policy allowing EC2 actions without conditions (Option A). But the question asks for the MOST likely reason given the exhibit and the intent. The trap is that the `aws:SourceIp` condition does not work for console-based API calls because the console uses AWS IP addresses, so the condition is effectively ignored for console users, allowing them to bypass the intended restriction. This is a well-known limitation documented by AWS.
What should I do if I get this SCS-C02 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: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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 →
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.
This SCS-C02 practice question is part of Courseiva's free Amazon Web Services 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 SCS-C02 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.