DOP-C02 Question #194: Real Exam Question with Answer & Explanation

Question

A DevOps engineer is planning to deploy a Ruby-based application to production. The application needs to interact with an Amazon RDS for MySQL database and should have automatic scaling and high availability. The stored data in the database is critical and should persist regardless of the state of the application stack. The DevOps engineer needs to set up an automated deployment strategy for the application with automatic rollbacks. The solution also must alert the application team when a deployment fails. Which combination of steps will meet these requirements? (Choose three.)

Options

• ADeploy the application on AWS Elastic Beanstalk. Deploy an Amazon RDS for MySQL DB
• BDeploy the application on AWS Elastic Beanstalk. Deploy a separate Amazon RDS for MySQL
• CConfigure a notification email address that alerts the application team in the AWS Elastic
• DConfigure an Amazon EventBridge rule to monitor AWS Health events. Use an Amazon Simple
• EUse the immutable deployment method to deploy new application versions.
• FUse the rolling deployment method to deploy new application versions.

Explanation

Explanation

Why B, C, and E are correct:

B is correct because deploying RDS outside of Elastic Beanstalk's environment ensures the database persists independently - if the Beanstalk environment is terminated or rolled back, the data remains intact. C is correct because Elastic Beanstalk has a built-in notification configuration that sends email alerts for environment events, including deployment failures, satisfying the alerting requirement without additional complexity. E is correct because the immutable deployment method launches entirely new instances for each deployment, enabling automatic rollback by simply terminating the new instances if the health check fails, making it the safest strategy for production.

Why the distractors are wrong:

• A is wrong because coupling the RDS instance inside the Elastic Beanstalk environment means the database could be deleted if the environment is torn down, violating the data persistence requirement.
• D is wrong because while EventBridge + SNS can work, it adds unnecessary complexity when Elastic Beanstalk already provides built-in email notification support natively.
• F is wrong because the rolling deployment method updates instances in batches, and rollbacks are slower and more complex - immutable is the better choice for automated rollbacks.

💡 Memory Tip

Think "Outside, Built-in, Immutable" - keep RDS outside Beanstalk, use built-in notifications, and use immutable deployments for safe rollbacks.

No community discussion yet for this question.