SCS-C02 Security Logging and Monitoring Practice Question
A security team uses Amazon Macie to discover sensitive data in S3. They have configured Macie to run automated sensitive data discovery jobs. After reviewing the findings, they notice that some S3 objects containing personally identifiable information (PII) are not being flagged. What is the most likely cause?
⚠ Common exam trap
Candidates often assume encryption (SSE-S3) or cross-region issues block Macie, but Macie is designed to handle both seamlessly, and the real limitation is the scope of its pattern-matching identifiers.
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 PII is in a format that Macie's managed data identifiers do not recognize, and no custom data identifier is configured.
Macie uses managed data identifiers to detect PII based on predefined patterns. If the PII in the S3 objects is in a format that does not match any of these managed identifiers (e.g., a non-standard date format or a custom ID number), and no custom data identifier has been configured to recognize that specific pattern, Macie will not flag the objects. This is the most likely cause given that the security team has already configured automated discovery jobs and other common issues like permissions or encryption are not preventing scanning.
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 Macie service-linked role does not have permissions to read the objects.
Why it's wrong here
This is incorrect because Macie automatically creates the AWS service-linked role AWSServiceRoleForAmazonMacie, which grants it read-only access to S3 objects and associated metadata for scanning. The service-linked role is pre-provisioned with the necessary permissions, so a lack of role permissions would not prevent Macie from reading the objects. If the role were missing or misconfigured, Macie would display an access error, but that is not the scenario described here.
- ✗
The S3 bucket is in a different AWS Region than the Macie job.
Why it's wrong here
This is incorrect because Macie is a regional service, but it can analyze S3 buckets in any AWS Region where Macie is enabled. You can create a Macie job that scans buckets across multiple regions, and the job's region does not need to match the bucket's region. Therefore, a bucket being in a different region than the Macie job does not cause Macie to miss detecting PII.
- ✗
The S3 objects are encrypted with SSE-S3.
Why it's wrong here
This is incorrect because Macie can inspect objects encrypted with SSE-S3 (Amazon S3-managed keys) because S3 transparently decrypts the object content for Macie's read operations. The service has access to the plaintext after S3 handles decryption, so encryption with SSE-S3 does not interfere with Macie's ability to discover sensitive data. Thus, encryption is not the reason Macie failed to detect the PII.
- ✓
The PII is in a format that Macie's managed data identifiers do not recognize, and no custom data identifier is configured.
Why this is correct
This is correct because Macie relies on managed data identifiers that recognize common PII patterns, such as US Social Security numbers and credit card numbers. If the PII is in a proprietary or less common format that these built-in identifiers do not match, Macie will not flag it. Since no custom data identifier was created to define that specific format, Macie has no way to detect the sensitive data, so the data goes undiscovered.
Quick reference
AWS S3 Storage Class Comparison
| Storage Class | Min Duration | Retrieval | Use Case |
|---|---|---|---|
| S3 Standard | None | Immediate | Frequently accessed data |
| S3 Standard-IA | 30 days | Immediate | Infrequent access, rapid retrieval |
| S3 One Zone-IA | 30 days | Immediate | Non-critical infrequent data |
| S3 Intelligent-Tiering | None | Immediate–hours | Unknown or changing access patterns |
| S3 Glacier Instant | 90 days | Milliseconds | Archive with instant retrieval |
| S3 Glacier Flexible | 90 days | Minutes–hours | Archive, flexible retrieval |
| S3 Glacier Deep Archive | 180 days | Hours | Long-term compliance archive |
Go deeper
Related to this question
About these practice questions
This SCS-C02 question is part of Courseiva's 376-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.