DOP-C02 domain - 14% of the exam

Incident and Event Response

Incident and Event Response is 14% of the DOP-C02 exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

43
Practice questions
5
Objectives
25
Medium
18
Hard

Where people go wrong

  • Treating an alert as a remediation

    The wrong answers stop at telling a person: an SNS notification, a GuardDuty alert, or a metric alarm that routes to a human. The scenario asks for a fix with no operator, and an alert only surfaces the problem quickly while an engineer still has to act. The correct answers attach an action to the trigger: Config automatic remediation, an EventBridge rule invoking Lambda, or a Logs subscription filter invoking Lambda under a least-privilege role.

    See it in a sample question
  • Using a schedule where an event must trigger the response

    Several wrong options poll on a timer: a scheduled rule scanning CloudTrail, a State Manager association applying a desired state, or a recurring association checking logs. Each adds delay between the change and the fix, which breaks a requirement tied to the event itself. State Manager enforces configuration on a cadence. EventBridge rules, Config remediation and log subscription filters react when the change, finding or log line occurs.

    See it in a sample question
  • Reaching for the wrong telemetry source

    Each wrong option picks a telemetry source that cannot hold the evidence asked for. VPC Flow Logs carry no caller identity or API action, CloudTrail records API calls but no ACCEPT or REJECT decision for a packet, and X-Ray sees instrumented application calls but not the network layer or bytes per destination. CloudTrail attributes a change through userIdentity, eventTime and sourceIPAddress, and a Logs Insights query over Flow Logs reads ACCEPT or REJECT per flow and sums bytes by dstAddr.

    See it in a sample question
  • Treating deletion safeguards as rollback controls

    CloudFormation questions offer termination protection and DeletionPolicy settings as if they governed rollback. Termination protection only blocks deleting the whole stack, and DeletionPolicy decides what survives a deletion; neither preserves failed resources, unsticks UPDATE_ROLLBACK_FAILED, or reverts an unhealthy update. DisableRollback keeps failed resources for inspection, ContinueUpdateRollback recovers a stuck stack, and rollback triggers tied to CloudWatch alarms revert automatically.

    See it in a sample question
  • Pointing every consumer at one queue when each needs every event

    When several independent consumers must each receive every event, the wrong answers point all of them at one Amazon SQS queue, call each consumer in turn, or list every consumer as a separate rule target. A shared queue hands each message to one consumer, so consumers compete for events. Synchronous calls tie the producer to the slowest consumer, and separate targets mean editing the rule for each new consumer. An SNS topic delivers each event to every subscriber, and an SQS queue subscribed to the topic buffers events for a fixed-rate worker.

    See it in a sample question

Objectives in this domain

What to study

The official documents this domain's practice questions cite most.

Sample questions from this domain

Free sampleIncident and Event Responsemedium

A team responds to GuardDuty findings of the type that an EC2 instance is communicating with a known command-and-control host. On such a finding they must automatically isolate the instance by attaching a quarantine security group and capture a forensic snapshot, with the response running consistently for every matching finding and no operator in the loop. The logic involves several conditional AWS API calls that must run on receipt of the finding event. Which design BEST automates this response?

  • ACreate an "Amazon EventBridge" rule that matches the GuardDuty finding and invokes an "AWS Lambda" function granted a least-privilege role to attach the quarantine security group and create the forensic snapshot. Correct
  • BEnable "AWS Config" with a managed rule and attach automatic remediation so that the instance is moved to a quarantine security group whenever the rule reports it as non-compliant.
  • CConfigure a "Systems Manager State Manager" association that periodically checks instances against the GuardDuty console and quarantines any that have an active command-and-control finding.
  • DForward the GuardDuty finding to an "Amazon SNS" topic so a security engineer is notified and then attaches the quarantine security group and takes the snapshot manually.
Match a specific GuardDuty finding with an EventBridge rule that invokes a least-privilege Lambda function to isolate and snapshot the affected instance. GuardDuty publishes findings to EventBridge, where a rule can match a precise finding type and target a Lambda function; the function assumes a least-privilege role to make the conditional EC2 calls that attach a quarantine security group and create a forensic snapshot, providing a consistent event-driven containment response without human involvement, which is the right fit when the trigger is a threat finding rather than a configuration state.

Why A is correct: EventBridge can pattern-match the specific GuardDuty finding and invoke a Lambda function that performs the conditional API calls to isolate the instance and snapshot it, giving consistent automated incident response under a scoped role with no operator needed.

Why B is wrong: Config remediation reacts to resource configuration drift, but a GuardDuty threat finding is not a configuration-compliance state, so a Config rule would not be evaluated by the finding and could not drive this response.

Why C is wrong: State Manager applies a desired configuration on a schedule and cannot consume GuardDuty findings, so the response would lag behind the threat and would not be driven by the finding event the scenario requires.

Why D is wrong: An SNS notification surfaces the threat promptly, which is appealing, but it leaves the containment to a human, so it fails the requirement for an automated, operator-free response on every matching finding.

Free sampleIncident and Event Responsehard

An Amazon S3 bucket holding production data was made publicly readable for roughly twenty minutes before an engineer reverted it. The security team must determine, after the fact, exactly who or what changed the bucket configuration, when the change was made, and from which source IP address, so they can complete a root-cause report. The account has AWS CloudTrail enabled with a multi-Region trail delivering management events to an S3 bucket, and they have not yet enabled any other diagnostic service. Which approach MOST directly answers who made the change?

  • AEnable Amazon S3 server access logging on the bucket now and review the delivered access log records to find the principal and source address that altered the bucket configuration during the exposure window.
  • BRun a CloudWatch Logs Insights query over the application log group for the time window to find the entry that recorded the bucket being made public, then read the user field from that log line.
  • CQuery the AWS CloudTrail event history or the delivered trail logs for the PutBucketAcl and PutBucketPolicy events on that bucket, reading the userIdentity, eventTime and sourceIPAddress fields to attribute the change. Correct
  • DAnalyse VPC Flow Logs for the period to find the source IP that connected to the S3 endpoint, then map that address back to the engineer or service that reconfigured the bucket during the exposure.
Use AWS CloudTrail management events to attribute a configuration change to a principal, time and source IP after the fact. AWS CloudTrail logs management API calls including S3 bucket configuration changes, recording userIdentity, eventTime and sourceIPAddress for each event. Because the trail was already capturing these events, querying CloudTrail is the direct way to attribute a past change to a specific principal, time and origin for a root-cause report.

Why A is wrong: S3 server access logs capture object-level request activity going forward and would not be populated for a change that already happened, nor do they record bucket-configuration API calls with caller identity.

Why B is wrong: Application logs only contain what the application chose to write and would not capture an out-of-band configuration change made through the console or API, so the responsible principal is not recorded there.

Why C is correct: CloudTrail records management API calls such as PutBucketAcl with the userIdentity, eventTime and sourceIPAddress, so querying those events for the bucket attributes the change to a principal, time and origin exactly as required.

Why D is wrong: VPC Flow Logs show network connections by IP but carry no caller identity or API action, so they cannot reveal who altered the bucket policy, only that some traffic to an endpoint occurred.

Free sampleIncident and Event Responsehard

An engineer runs an AWS CloudFormation stack update that fails when a new Amazon RDS instance cannot be created because of an invalid parameter group. CloudFormation begins rolling the stack back, but the engineer needs to inspect the half-created resources to understand exactly why the database failed before the rollback deletes them. On the next attempt they want the failed resources preserved so they can examine them rather than being torn down automatically. Which approach MOST directly gives them that ability while keeping the failed stack debuggable?

  • AEnable termination protection on the stack before retrying, so CloudFormation cannot delete the stack and therefore leaves every failed resource in place for the engineer to inspect after the update fails again.
  • BAdd a DeletionPolicy of Retain to every resource in the template, so when the update fails CloudFormation keeps all resources and the engineer can examine the database that could not be created.
  • CRetry the update with rollback disabled by passing the DisableRollback option (or OnFailure set to DO_NOTHING) on the stack operation, so the failed resources stay in place for inspection before a manual delete. Correct
  • DConfigure a rollback trigger with a CloudWatch alarm on the stack, so the alarm holds the rollback open long enough for the engineer to capture the failed RDS instance details during the monitoring period.
Disable rollback on a CloudFormation operation to preserve partially created resources for troubleshooting instead of letting the automatic rollback delete them. When a CloudFormation create or update fails, the default behaviour rolls the stack back and removes the failed resources. Disabling rollback for the operation leaves the stack in CREATE_FAILED or UPDATE_FAILED with its resources intact, which is the supported way to inspect why a resource such as an RDS instance could not be created.

Why A is wrong: Termination protection only blocks deletion of the whole stack, not the per-resource rollback during a failed update, so the half-created database is still removed and remains unavailable for inspection.

Why B is wrong: DeletionPolicy Retain governs what survives a stack or resource deletion, not the automatic rollback of a failed create, and it cannot preserve a resource that never finished creating in the first place.

Why C is correct: Disabling rollback on the operation leaves the stack in the failed state with its partially created resources intact, letting the engineer inspect the database problem before they manually clean up or retry.

Why D is wrong: Rollback triggers decide whether to roll back based on alarms during an update, they do not pause or preserve a rollback in progress, so the failed database is still deleted before it can be examined.

Free sampleIncident and Event Responsemedium

An operations team uses an EventBridge rule to notify responders when a critical alarm fires. They need the same event to fan out to several independent consumers at once: an email distribution list, an existing SQS-backed ticketing worker, and an HTTPS endpoint owned by a partner. They want one durable publish step that delivers to all current and future subscribers without editing the rule each time a consumer is added. Which target should the rule use?

  • AAdd three separate targets to the EventBridge rule, one for email through Lambda, one for the SQS ticketing queue, and one for an API destination to the partner endpoint, updating the rule whenever a consumer changes.
  • BTarget a single Amazon SQS queue from the rule and have each consumer poll that queue, so the email sender, the ticketing worker, and the partner integration all read from the same queue of alarm events.
  • CTarget an Amazon SNS topic from the rule and subscribe the email address, the SQS ticketing queue, and the partner HTTPS endpoint to the topic, so new subscribers are added on the topic without changing the rule. Correct
  • DTarget a Lambda function from the rule that, for each alarm event, calls the email service, writes to the SQS ticketing queue, and posts to the partner endpoint, editing the function when a consumer is added.
Use an SNS topic as the EventBridge rule target to fan one event out to many independent subscribers that can be added without editing the rule. Amazon SNS implements a publish-subscribe model where a single published message is delivered to every subscription, and supported subscription types include email, SQS queues, and HTTPS endpoints; targeting one SNS topic from the EventBridge rule means each alarm event fans out to all current subscribers, and adding a consumer is a topic subscription change that leaves the rule untouched.

Why A is wrong: Multiple direct targets do reach all three consumers, but every new or changed consumer means editing the rule, which the requirement to add subscribers without touching the rule explicitly excludes.

Why B is wrong: A single SQS queue gives each message to only one consumer that receives it, so the consumers would compete for events rather than all receiving them, breaking the required fan-out to every subscriber.

Why C is correct: An SNS topic as the single rule target fans each event to all of its subscriptions, including email, an SQS queue, and an HTTPS endpoint, and new consumers are added as subscriptions on the topic, so the rule never needs editing.

Why D is wrong: A dispatcher function can reach all three consumers, but it centralises delivery logic that must be edited and redeployed for every new consumer, which is the maintenance the subscribe-without-changes requirement avoids.

Other domains in this exam

See also the DOP-C02 cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by Amazon Web Services. Original, blueprint-aligned practice material only.