This SCS-C02 practice question tests your understanding of security logging and monitoring. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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.
Network Topology
Refer to the exhibit. A security engineer ran this AWS CLI command to find when a specific CreateKeyPair API call was made. The command returns no results, even though the engineer knows the call was made. 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.
Network Topology
A
The time range is too narrow.
Why wrong: The time range covers the entire month.
B
The command did not specify a region, so it defaults to us-east-1, but the call was made in a different region.
Why wrong: Region mismatch could cause missing results, but the syntax error is more likely.
C
The event name should be 'CreateKeypair' (lowercase p).
Why wrong: Event names are case-sensitive but the correct name is CreateKeyPair.
D
The --lookup-attributes parameter has incorrect syntax.
The comma should be a space or the syntax is wrong.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The --lookup-attributes parameter has incorrect syntax.
Option D is correct because the `--lookup-attributes` parameter requires a JSON structure with an `AttributeKey` and `AttributeValue`. The provided syntax `--lookup-attributes EventName=CreateKeyPair` is invalid; the correct format is `--lookup-attributes AttributeKey=EventName,AttributeValue=CreateKeyPair`. This malformed parameter causes the AWS CLI to fail silently or return no results, even though the API call exists.
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 time range is too narrow.
Why it's wrong here
The time range covers the entire month.
✗
The command did not specify a region, so it defaults to us-east-1, but the call was made in a different region.
Why it's wrong here
Region mismatch could cause missing results, but the syntax error is more likely.
✗
The event name should be 'CreateKeypair' (lowercase p).
Why it's wrong here
Event names are case-sensitive but the correct name is CreateKeyPair.
✓
The --lookup-attributes parameter has incorrect syntax.
Why this is correct
The comma should be a space or the syntax is wrong.
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.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume the `--lookup-attributes` parameter accepts simple key=value syntax like other AWS CLI commands, but CloudTrail requires a specific `AttributeKey` and `AttributeValue` pair, and failing to use this correct structure silently returns no results instead of an error.
Detailed technical explanation
How to think about this question
The `lookup-events` API uses the `LookupAttribute` structure where `AttributeKey` must be one of the predefined keys (e.g., EventName, ResourceName, ResourceType) and `AttributeValue` is the corresponding value. The AWS CLI parses `--lookup-attributes` as a list of key-value pairs, but the incorrect syntax `EventName=CreateKeyPair` is interpreted as a single string, not a structured attribute, leading to a validation failure that returns no results. In real-world scenarios, this often happens when engineers copy command examples from documentation without noticing the required JSON-like format.
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 cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
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.
Security Logging and Monitoring — This question tests Security Logging and Monitoring — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The --lookup-attributes parameter has incorrect syntax. — Option D is correct because the `--lookup-attributes` parameter requires a JSON structure with an `AttributeKey` and `AttributeValue`. The provided syntax `--lookup-attributes EventName=CreateKeyPair` is invalid; the correct format is `--lookup-attributes AttributeKey=EventName,AttributeValue=CreateKeyPair`. This malformed parameter causes the AWS CLI to fail silently or return no results, even though the API call exists.
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.