Amazon Web Services DOP-C02 Practice Test Questions Answers

ALB supports weighted target groups for traffic splitting between versions without DNS-level changes. By attaching multiple target groups (old & beta) to the same ALB listener rule with weights (90/10), partial traffic testing can occur seamlessly. This is the recommended least-change method per Application Load Balancer advanced request routing documentation.

When the CodeUri property points directly to a static S3 object path, AWS CloudFormation detects no template changes between deployments because the S3 URI remains identical even after you upload updated code to the same key. The solution is to reference local source code so that SAM or CloudFormation can compute a content hash, upload the artifact with a unique S3 key, and update the template, creating a detectable change. Option C works because sam deploy with a local CodeUri path automatically packages the function, uploads it to S3 with a hash-derived key, and deploys the updated stack. Option E works for the same reason: aws cloudformation package computes the hash, uploads the artifact, and produces a packaged template that aws cloudformation deploy can then apply. Options A and B do not resolve the root cause and are not designed for SAM Lambda packaging.

================

The “fan-out” batch build type in AWS CodeBuild allows running multiple builds in parallel for different subsets of tests, reducing overall test execution time. CodeBuild then aggregates the results into a single consolidated report. This approach is detailed in the AWS documentation under “Batch builds and parallel execution with CodeBuild.”

Amazon Redshift supports audit logging which can be configured to log user activity, including queries and user changes. The logs can be delivered to an S3 bucket (Option B), which is the standard location for Redshift audit logs.

While Redshift can send some logs to CloudWatch, the native audit logging is typically routed to S3. Creating a CloudWatch dashboard with a log widget (Option D) allows visualization of user activities from logs ingested into CloudWatch Logs or through custom processing.

Option A is invalid because CloudTrail does not capture Redshift query logs directly. Option C incorrectly assumes Redshift audit logs can be delivered directly to CloudWatch. Option E adds complexity by requiring Lambda and Athena unnecessarily when direct visualization in CloudWatch is simpler.

 Use AWS Step Functions to Orchestrate Processing:

AWS Step Functions allow you to build distributed applications by combining AWS Lambda functions or other AWS services into workflows.

Decoupling the processing into Step Functions tasks enables you to retry individual steps without reprocessing the entire record.

 Architectural Steps:

Create a web application to pass records to AWS Step Functions:

The web application can be a simple frontend that receives input and triggers the Step Functions workflow.

Define a Step Functions state machine:

Each step in the state machine represents a processing stage. If a step fails, Step Functions can retry the step based on defined conditions.

Use AWS Lambda functions:

Lambda functions can be used to handle each processing step. These functions can be stateless and handle specific tasks, reducing the complexity of error handling and reprocessing logic.

 Operational Efficiency:

Using Step Functions and Lambda improves operational efficiency by providing built-in error handling, retries, and state management.

This architecture scales automatically and isolates failures to individual steps, ensuring only failed steps are retried.