RDS pricing considerations in AWS - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding RDS Pricing Components

Which of the following factors directly affects the cost of running an Amazon RDS instance?

A The programming language used to develop the application

B The size of the database instance and the amount of storage allocated

C The number of users accessing the database simultaneously

D The color scheme of the AWS Management Console

💡 Hint

Think about what AWS charges for when you run a database.

AWS charges based on the resources you use, like instance size and storage. User count or app design does not directly affect pricing.

❓ service_behavior

intermediate

Impact of Backup Retention on RDS Cost

What happens to your RDS monthly bill if you increase the backup retention period from 7 days to 35 days?

A The cost increases because more backup storage is used

B The cost decreases because backups are compressed

C The cost stays the same regardless of backup retention

D The cost increases only if you enable Multi-AZ

💡 Hint

Think about how storing more backups affects storage usage.

Longer backup retention means more backup data stored, increasing storage costs.

❓ Architecture

advanced

Choosing RDS Deployment for Cost Efficiency

You want to minimize costs but need high availability for your database. Which RDS deployment option balances cost and availability best?

A Single-AZ deployment with automated backups enabled

B Read replica in a different region only

C Multi-AZ deployment with synchronous replication

D Multi-AZ deployment with asynchronous replication

💡 Hint

High availability usually costs more. Consider the standard RDS option for failover.

Multi-AZ deployment provides high availability with automatic failover using synchronous replication, costing more than Single-AZ but best balance for HA without cross-region expense.

❓ security

advanced

Cost Impact of Enabling Encryption on RDS

What is the effect on RDS pricing when you enable encryption at rest for your database?

A Encryption adds a fixed monthly fee

B Encryption doubles the storage cost

C Encryption requires a larger instance size, increasing cost

D There is no additional charge for encryption at rest

💡 Hint

Think about AWS's policy on encryption charges.

AWS does not charge extra for encryption at rest on RDS; costs come from storage and instance usage only.

✅ Best Practice

expert

Optimizing RDS Cost with Reserved Instances

You plan to run an RDS instance continuously for 3 years. Which purchasing option will minimize your total cost?

A 3-year reserved instance with all upfront payment

B Spot instance pricing for RDS

C 1-year reserved instance with no upfront payment

D On-demand instance pricing with no commitment

💡 Hint

Consider long-term commitments and upfront payments.

3-year reserved instances with upfront payment offer the biggest discount for continuous use.

Practice

1. Which factor directly affects the hourly cost of an AWS RDS instance?

easy

A. The number of tables in the database

B. The instance size (e.g., db.t3.medium vs db.m5.large)

C. The number of users connected

D. The database engine version

Solution

1. Step 1: Understand RDS pricing components

   RDS pricing depends on instance size, storage, backups, and deployment options, not on users or tables.

2. Step 2: Identify the factor affecting hourly cost

   The instance size determines the compute capacity and directly affects the hourly price.

3. Final Answer:

   The instance size (e.g., db.t3.medium vs db.m5.large) -> Option B

4. Quick Check:

   Instance size = hourly cost [OK]

Hint: Instance size controls hourly cost, not users or tables [OK]

Common Mistakes:

• Confusing number of users with cost
• Thinking database engine version affects hourly price
• Assuming number of tables changes cost

2. Which storage type option is valid when configuring AWS RDS storage?

easy

A. Magnetic

B. NVMe

C. SSD General Purpose (gp3)

D. Tape Drive

Solution

1. Step 1: Review valid RDS storage types

   AWS RDS supports SSD General Purpose (gp2/gp3), Provisioned IOPS SSD, and Magnetic (deprecated).

2. Step 2: Identify the valid current option

   SSD General Purpose (gp3) is a valid and recommended storage type for RDS.

3. Final Answer:

   SSD General Purpose (gp3) -> Option C

4. Quick Check:

   gp3 is valid RDS storage [OK]

Hint: Choose gp3 for modern RDS SSD storage [OK]

Common Mistakes:

• Selecting deprecated or unsupported storage types
• Confusing tape or NVMe with RDS storage
• Assuming Magnetic is still recommended

3. Given an RDS instance with 100 GB of gp3 storage and 7 days backup retention, which factor will increase the monthly cost the most?

medium

A. Switching database engine from MySQL to PostgreSQL

B. Increasing backup retention from 7 to 35 days

C. Changing instance type from db.t3.medium to db.t3.small

D. Increasing storage from 100 GB to 200 GB

Solution

1. Step 1: Analyze cost impact of backup retention

   Backup storage beyond allocated free backup size adds cost, but increasing retention from 7 to 35 days may add moderate cost.

2. Step 2: Analyze cost impact of storage increase

   Doubling storage from 100 GB to 200 GB doubles storage cost, which is a significant monthly cost increase.

3. Step 3: Analyze instance type and engine changes

   Changing to smaller instance reduces cost; engine change does not affect pricing directly.

4. Final Answer:

   Increasing storage from 100 GB to 200 GB -> Option D

5. Quick Check:

   Storage size increase = biggest cost rise [OK]

Hint: Storage size impacts monthly cost more than backup days [OK]

Common Mistakes:

• Assuming backup retention always costs more
• Thinking smaller instance increases cost
• Believing engine type changes price

4. You configured an RDS instance with Multi-AZ deployment but forgot to enable automated backups. What pricing issue will occur?

medium

A. You will be charged for Multi-AZ but no backup storage cost

B. You will be charged for backup storage even if backups are disabled

C. You will not be charged for Multi-AZ deployment

D. You will be charged for backup storage only if manual snapshots exist

Solution

1. Step 1: Understand Multi-AZ pricing

   Multi-AZ doubles instance cost because a standby instance runs in another zone.

2. Step 2: Understand backup storage pricing

   Automated backups must be enabled to incur backup storage charges; if disabled, no backup storage cost applies.

3. Final Answer:

   You will be charged for Multi-AZ but no backup storage cost -> Option A

4. Quick Check:

   Multi-AZ charges apply; backups disabled means no backup cost [OK]

Hint: Multi-AZ costs apply even if backups are off [OK]

Common Mistakes:

• Assuming backup storage cost applies without backups enabled
• Thinking Multi-AZ is free
• Confusing manual snapshots with automated backups

5. You want to minimize AWS RDS costs for a development environment that requires low latency and high availability. Which combination is best?

hard

A. Use a small instance with Multi-AZ deployment and gp3 storage

B. Use a medium instance with Multi-AZ deployment and Magnetic storage

C. Use a small instance with Single-AZ deployment and gp3 storage

D. Use a large instance with Single-AZ deployment and gp3 storage

Solution

1. Step 1: Identify cost and availability needs

   Low latency and high availability require Multi-AZ deployment and sufficient instance size.

2. Step 2: Evaluate storage and instance size

   gp3 storage is cost-effective and performant; small instance reduces cost while Multi-AZ ensures availability.

3. Step 3: Compare options

   Use a small instance with Multi-AZ deployment and gp3 storage balances cost (small instance), availability (Multi-AZ), and performance (gp3 storage).

4. Final Answer:

   Use a small instance with Multi-AZ deployment and gp3 storage -> Option A

5. Quick Check:

   Small + Multi-AZ + gp3 = cost-effective high availability [OK]

Hint: Multi-AZ + small instance + gp3 balances cost and availability [OK]

Common Mistakes:

• Choosing Magnetic storage which is slower and deprecated
• Ignoring Multi-AZ for high availability
• Picking large instance unnecessarily increasing cost