SOA-C03 - Security and Compliance - Section 4.5

Configure and remediate findings from AWS Security Hub, Amazon GuardDuty, AWS Config, Amazon Inspector and Amazon Macie, and enforce a data classification scheme.

Configure AWS Security Hub to aggregate findings from Amazon GuardDuty threat detection, AWS Config rule compliance, Amazon Inspector vulnerability assessments, and Amazon Macie sensitive data discovery. Apply a data classification scheme and use automated remediation actions to resolve high-severity findings without manual intervention.

AWS Security HubAmazon GuardDutyAWS ConfigAmazon Inspector

Practice question for this objective

Free sampleSecurity and Compliancemedium

A compliance team must enforce a data classification scheme over hundreds of Amazon S3 buckets: objects containing sensitive personal data such as credit card and passport numbers must be discovered automatically, and each finding must drive a hands-off response that tags and restricts the affected bucket within minutes, using managed services with the least custom plumbing. Which two actions together meet this requirement? (Select TWO.)

  • ARun an Amazon GuardDuty malware and threat analysis over the buckets so it classifies which objects hold sensitive personal data and reports them as findings.
  • BConfigure an Amazon Macie sensitive data discovery job with managed data identifiers to scan the buckets and raise a finding for each object holding the personal data types. Correct
  • CDeploy an AWS Config managed rule that evaluates each bucket's configuration and marks buckets non-compliant when they contain sensitive personal data.
  • DEnable an Amazon Inspector continuous scan on the EC2 instances and ECR images near the buckets so its findings list any objects storing regulated personal data.
  • ECreate an Amazon EventBridge rule that matches the Macie findings and targets an AWS Systems Manager Automation runbook to tag and restrict access to the affected bucket. Correct
Amazon Macie discovery jobs classify sensitive S3 object content, and routing those findings through EventBridge to a Systems Manager runbook enforces the classification response automatically. Enforcing a data classification scheme needs a service that reads object content, which is Macie: its discovery jobs use managed data identifiers to find credit card and passport data and raise findings. Those findings are emitted to EventBridge, so an EventBridge rule targeting a Systems Manager Automation runbook can tag and lock down each affected bucket with no custom polling. GuardDuty analyses activity for threats, AWS Config evaluates configuration rather than content, and Inspector scans for software vulnerabilities, so none of them can classify the data the scheme governs.

Why A is wrong: GuardDuty detects threats from account and network activity and seems applicable, but it does not inspect object content for personal data, so it cannot perform the classification required.

Why B is correct: Macie discovery jobs with managed data identifiers inspect S3 object content and raise findings for credit card and passport data, delivering the automated classification half of the scheme.

Why C is wrong: AWS Config evaluates resource configuration rather than object content and looks compliance-aware, but it cannot read the data inside objects, so it never identifies sensitive records.

Why D is wrong: Inspector scans compute and container images for software vulnerabilities and seems security-relevant, but it never inspects S3 object content for classified data of any kind.

Why E is correct: Macie publishes findings to EventBridge, and an EventBridge rule invoking a Systems Manager Automation runbook applies the tag and access restriction within minutes, delivering the hands-off response half.

See more SOA-C03 practice questions, answers explained.

More in this domain

Back to all Security and Compliance objectives, or the SOA-C03 cert hub.

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