Amazon Web Services DOP-C02 Exam With Confidence Using Practice Dumps

To add an automated test in AWS CodePipeline that checks the HTTP response code of a deployed application, the most straightforward and operationally efficient method is to create an AWS Lambda function that makes an HTTP request to the application URL, checks the response code, and then reports success or failure back to CodePipeline.

The Lambda function can be invoked as an action in the pipeline stage.

If the response code is not 200 OK, the Lambda function can return a failure, causing the pipeline stage to fail and halt further execution.

Option A’s CloudWatch synthetic canary monitors are useful for ongoing monitoring but are not natively integrated as CodePipeline actions to control pipeline flow.

Option C incorrectly uses CodeDeploy action for testing, which is not designed for this purpose.

Option D introduces unnecessary complexity by deploying API Gateway and Device Farm, which is not required for a simple HTTP status check. Therefore, option B provides a clean, simple, and fully automated way to enforce HTTP response validation within the pipeline.

Reference from AWS Official Documentation:

AWS CodePipeline Custom Actions: " You can create Lambda invoke actions in your pipeline stages to run custom validation or testing functions. " (AWS CodePipeline User Guide - Lambda Actions)

AWS Lambda Function for Health Checks: " Lambda functions can be used to perform health checks or API response validations and report results back to invoking services. " (AWS Lambda Developer Guide)

S3 cross-Region replication (CRR) automatically replicates data between buckets across different AWS Regions. To enable CRR, you need to add a replication configuration to your source bucket that specifies the destination bucket, the IAM role, and the encryption type (optional). You also need to grant permissions to the IAM role to perform replication actions on both the source and destination buckets. Additionally, you can choose the destination storage class and enable additional replication options such as S3 Replication Time Control (S3 RTC) or S3 Batch Replication.

The requirements demand very low data loss (RPO < 1 minute) and fast recovery (RTO < 10 minutes) across Regions . Snapshot/backup-based approaches (B, D) generally cannot meet an RPO under 1 minute (and restoring snapshots/backups typically pushes RTO higher than 10 minutes for many real-world DB sizes and restore times).

Option A is the only choice that is explicitly built around near-real-time replication to another Region (cross-Region replica) and an operational pattern to promote the standby and update Route 53 to redirect applications quickly during failover.

Multi-AZ addresses in-Region high availability , while the cross-Region replica + promotion addresses cross-Region DR with low RPO and acceptable RTO when automated.

Why the others don’t meet the stated RPO/RTO:

B : Copying snapshots every 5 minutes immediately violates RPO < 1 minute .

C : DMS replication could potentially be low-latency, but the option only mentions notifications (no automated failover/redirect) and does not provide the clearest/most direct managed HA+DR pattern for the required RTO < 10 minutes .

D : “Cross-Region backups every 30 seconds ” is not a standard practical backup cadence for AWS Backup with RDS, and restore-based DR still tends to miss the RTO/RPO targets compared with replica promotion.