Answer-first summary for fast verification
Answer: Configure storage Auto Scaling on the RDS for Oracle instance., Configure the Auto Scaling group to use the average CPU as the scaling metric.
## Explanation **Correct Answers: A and D** ### Why A is correct: - The RDS for Oracle instance is running out of storage due to increasing traffic - RDS supports **Storage Auto Scaling** which automatically increases storage when needed - This solves the storage capacity issue without manual intervention - Storage Auto Scaling monitors actual storage consumption and automatically scales storage when certain thresholds are met ### Why D is correct: - The EC2 instances are becoming overloaded due to increasing traffic - The Auto Scaling group currently has no scaling metrics configured - Using **average CPU utilization** as a scaling metric allows the Auto Scaling group to automatically add instances when CPU usage is high and remove instances when CPU usage is low - This provides automatic scaling for compute resources based on actual workload ### Why other options are incorrect: **B (Migrate to Aurora):** - While Aurora does have auto-scaling storage capabilities, migrating from Oracle to Aurora is a major undertaking - The application uses Oracle-specific PL/SQL functions which may not be compatible with Aurora - This is not the most efficient solution when RDS for Oracle already supports Storage Auto Scaling **C (Configure alarm):** - Configuring an alarm only provides notification but doesn't automatically solve the storage problem - An alarm requires manual intervention to increase storage - The question asks for automatic scaling solutions **E (Use average free memory):** - While memory can be a valid metric, CPU utilization is generally more reliable for web application scaling - The problem states EC2 instances are "overloaded" which typically indicates high CPU usage - Memory metrics might not accurately reflect the actual compute load ### Key AWS Concepts: 1. **RDS Storage Auto Scaling**: Automatically scales storage capacity based on actual usage 2. **Auto Scaling Group Metrics**: CloudWatch metrics like CPUUtilization can trigger scaling policies 3. **Scaling Policies**: Define when to add/remove instances based on metric thresholds 4. **Target Tracking Scaling**: Simplifies scaling by maintaining a target metric value (e.g., 70% CPU utilization)
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
A company has a multi-tier application deployed on several Amazon EC2 instances in an Auto Scaling group. An Amazon RDS for Oracle instance is the application's data layer that uses Oracle-specific PL/SQL functions. Traffic to the application has been steadily increasing. This is causing the EC2 instances to become overloaded and the RDS instance to run out of storage. The Auto Scaling group does not have any scaling metrics and defines the minimum healthy instance count only. The company predicts that traffic will continue to increase at a steady but unpredictable rate before leveling off.
What should a solutions architect do to ensure the system can automatically scale for the increased traffic? (Choose two.)
A
Configure storage Auto Scaling on the RDS for Oracle instance.
B
Migrate the database to Amazon Aurora to use Auto Scaling storage.
C
Configure an alarm on the RDS for Oracle instance for low free storage space.
D
Configure the Auto Scaling group to use the average CPU as the scaling metric.
E
Configure the Auto Scaling group to use the average free memory as the scaling metric.