What is the main issue causing the policy to not restrict access properly?
medium
A. The Action "s3:*" is invalid syntax
B. The Effect should be Deny instead of Allow
C. The Resource ARN is missing the bucket objects path
D. The Version date is incorrect
Solution
Step 1: Check the Resource ARN format
The ARN "arn:aws:s3:::example-bucket" refers only to the bucket itself, not the objects inside it.
Step 2: Understand access scope
To allow or restrict access to objects, the ARN must include "/*" to cover all objects, e.g., "arn:aws:s3:::example-bucket/*".
Final Answer:
The Resource ARN is missing the bucket objects path -> Option C
Quick Check:
Bucket ARN needs /* for objects [OK]
Hint: Bucket ARN must include /* to cover objects [OK]
Common Mistakes:
Using Allow instead of Deny incorrectly
Assuming s3:* is invalid
Ignoring the need for object path in ARN
5. You want to design a secure AWS environment that automatically detects unusual activity and isolates affected resources. Which combination of AWS services best supports this Security Pillar principle?
hard
A. AWS CloudTrail, Amazon GuardDuty, AWS Systems Manager
B. AWS Config, Amazon S3, AWS Lambda
C. Amazon EC2, AWS IAM, AWS CloudFormation
D. AWS Trusted Advisor, Amazon RDS, AWS SNS
Solution
Step 1: Identify services for detecting unusual activity
Amazon GuardDuty analyzes logs and detects suspicious behavior automatically.
Step 2: Identify services for logging and managing resources
AWS CloudTrail records API activity for auditing, and AWS Systems Manager helps isolate and manage affected resources.
Step 3: Evaluate other options
Other options lack the combination of detection, logging, and automated management needed for this security goal.
Final Answer:
AWS CloudTrail, Amazon GuardDuty, AWS Systems Manager -> Option A