Question 590 of 1,748
Threat Detection and Incident ResponsehardMultiple ChoiceObjective-mapped

Troubleshooting: CloudWatch Metric Filter Pattern Not Triggering for CreateAccessKey

This SCS-C02 practice question tests your understanding of threat detection and incident response. 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. A key principle to apply: cloudWatch Logs Metric Filter. 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.

A security engineer is configuring AWS CloudWatch Logs to monitor for suspicious activity. They want to create a metric filter that detects when an IAM user calls the `iam:CreateAccessKey` API. The engineer writes the following filter pattern: `{ ($.eventName = "CreateAccessKey") }`. After testing, the filter does not trigger. 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 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

The metric filter is not associated with the correct log group.

The filter pattern `{ ($.eventName = "CreateAccessKey") }` is syntactically correct and will match any CloudTrail event with eventName CreateAccessKey, regardless of service. The most likely reason the filter does not trigger is that the metric filter is not associated with the correct log group, or the log group does not contain CloudTrail events from IAM. A missing eventSource field does not prevent the filter from working; it would simply match events from any service, which could cause false positives, but not a failure to trigger.

Key principle: CloudWatch Logs Metric Filter

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 filter pattern syntax is incorrect; it should use square brackets.

    Why it's wrong here

    The filter pattern uses correct curly braces and syntax; square brackets are not required.

  • The metric filter is not associated with the correct log group.

    Why this is correct

    Correct. If the metric filter is not associated with the correct log group (or the log group lacks IAM CreateAccessKey events), it will not trigger.

    Clue confirmation

    The clue word "most likely" in the question point toward this answer.

    Related concept

    CloudWatch Logs Metric Filter

  • CloudWatch Logs does not support metric filters for CloudTrail logs.

    Why it's wrong here

    CloudWatch Logs fully supports metric filters for CloudTrail logs.

  • The filter pattern does not include the eventSource field, so it might match events from other services.

    Why it's wrong here

    Missing eventSource does not prevent the filter from triggering; it only broadens the match scope. This is not the likely reason for no trigger.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Candidates often focus on filter pattern syntax or missing fields when the filter doesn't trigger, but the most common cause is misconfiguration of the metric filter's association to the log group. Always verify the log group contains the expected CloudTrail events and that the metric filter is correctly linked.

Detailed technical explanation

How to think about this question

CloudWatch Logs metric filters evaluate log events against a pattern using JSON property notation. When filtering CloudTrail logs, the `eventSource` field (e.g., `iam.amazonaws.com`) is critical to isolate events from a specific service; without it, a pattern like `{ ($.eventName = "CreateAccessKey") }` will match any log event with that eventName, regardless of source. In practice, if the log group contains logs from multiple services (e.g., via a central CloudTrail trail), the filter might match events from services like `organizations.amazonaws.com` that also use `CreateAccessKey`, leading to incorrect metric counts or no match if the expected IAM events are not present.

KKey Concepts to Remember

  • CloudWatch Logs Metric Filter
  • CloudTrail Logs

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

CloudWatch Logs Metric Filter

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.

Review cloudWatch Logs Metric Filter, then practise related SCS-C02 questions on the same topic to reinforce the concept.

Related practice questions

Related SCS-C02 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 SCS-C02 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 SCS-C02 question test?

Threat Detection and Incident Response — This question tests Threat Detection and Incident Response — CloudWatch Logs Metric Filter.

What is the correct answer to this question?

The correct answer is: The metric filter is not associated with the correct log group. — The filter pattern `{ ($.eventName = "CreateAccessKey") }` is syntactically correct and will match any CloudTrail event with eventName CreateAccessKey, regardless of service. The most likely reason the filter does not trigger is that the metric filter is not associated with the correct log group, or the log group does not contain CloudTrail events from IAM. A missing eventSource field does not prevent the filter from working; it would simply match events from any service, which could cause false positives, but not a failure to trigger.

What should I do if I get this SCS-C02 question wrong?

Review cloudWatch Logs Metric Filter, then practise related SCS-C02 questions on the same topic to reinforce the concept.

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?

CloudWatch Logs Metric Filter

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 SCS-C02 practice questions

Last reviewed: Jul 4, 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 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.