SOA-C03 Exam Dumps and Practice Questions

Amazon S3 event notifications are the native mechanism for invoking processing when objects are uploaded to an S3 bucket. The CloudOps engineer can configure the bucket to send ObjectCreated events to an AWS Lambda function, and the Lambda function can process each new log file by using the bucket name and object key from the event payload. This is serverless, event-driven, and has the least operational overhead. CodePipeline is intended for software delivery workflows, not generic log-file processing. Step Functions is useful for orchestrating multi-step workflows, but polling or waiting for S3 uploads is unnecessary here. EventBridge can receive some S3 events, but the direct S3 event notification to Lambda is simpler and more targeted for this requirement.

EC2 Image Builder is a managed service that automates the creation, testing, vulnerability scanning, and distribution of AMIs. It supports scheduled image pipelines, which makes it ideal for weekly application updates.

Image Builder integrates with Amazon Inspector to perform vulnerability scans during image creation, fulfilling the security requirement. Custom image recipes define application dependencies and installation steps, ensuring consistency across deployments.

Manual AMI creation, cron-based scripts, or direct API calls require ongoing maintenance and do not natively support vulnerability scanning.

Therefore, EC2 Image Builder is the most operationally efficient solution.

AWS Systems Manager Run Command includes a built-in rate control feature that allows administrators to control the maximum number of concurrent executions across target instances. This directly addresses the requirement to limit downloads to 30 at a time without custom orchestration or additional services.

By targeting instances using tags, the solution automatically scales as new instances are added, which aligns with future growth expectations. Rate control ensures controlled concurrency and protects the private repository from overload.

Option A is manual and does not scale operationally. Option B introduces unnecessary complexity with Lambda and concurrency management that does not map cleanly to instance execution concurrency. Option D significantly increases architectural complexity without added value.

Run Command with rate control is the simplest, most native, and most scalable solution.

A Route 53 private hosted zone answers DNS queries only for VPCs that are associated with that hosted zone. Creating the VPC and adding records to the private hosted zone is not enough; the private hosted zone must be associated with the VPC where resolution is needed. Once associated, resources in that VPC can resolve the private DNS names according to the record sets in the hosted zone, assuming normal VPC DNS settings are enabled. Security group rules, network ACL rules, and route table entries are not the required configuration step for associating Route 53 private DNS. Route 53 Resolver is provided by AWS inside the VPC and does not require routing to an external endpoint for this use case. Therefore, the missing step is the private hosted zone-to-VPC association.

AWS Organizations service control policies (SCPs) are designed to enforce permission guardrails across accounts. SCPs define the maximum available permissions for IAM principals in member accounts, regardless of the permissions granted by IAM policies. Because the requirement is to prevent EC2 instance launches without a required tag and to apply the restriction only to accounts within a specific organizational unit, SCPs are the correct control mechanism.

By creating an SCP that denies the ec2:RunInstances action when the CostCenter-Project tag is missing, the CloudOps engineer ensures that no EC2 instance can be launched without the required tag. Attaching the SCP directly to the application OU limits the scope of enforcement to only the accounts that belong to that OU, which satisfies the requirement precisely.

IAM-based solutions such as user groups or roles cannot enforce controls across multiple accounts consistently and can be bypassed by users with sufficient permissions. Attaching the SCP to the root OU would incorrectly apply the restriction to all accounts in the organization, which violates the requirement.

Therefore, attaching a tag-enforcing SCP to the application OU is the correct and least operationally complex solution.