Launching an RDS instance in AWS - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Configuration

intermediate

Identify the correct AWS CLI command to launch a MySQL RDS instance

Which AWS CLI command will successfully launch a MySQL RDS instance named mydbinstance with 20GB storage in the us-east-1 region?

A aws rds create-db-instance --db-instance-identifier mydbinstance --db-instance-class db.t3.micro --engine mysql --allocated-storage 20 --region us-east-1

B aws rds launch-db-instance --db-instance-identifier mydbinstance --db-instance-class db.t3.micro --engine mysql --allocated-storage 20 --region us-east-1

C aws rds create-db-instance --db-instance-identifier mydbinstance --db-instance-class db.t3.micro --engine postgres --allocated-storage 20 --region us-east-1

D aws rds create-db-instance --db-instance-identifier mydbinstance --db-instance-class db.t3.micro --engine mysql --allocated-storage 5 --region us-east-1

💡 Hint

Check the AWS CLI command syntax for creating an RDS instance and verify the engine and storage size.

Option A uses the correct AWS CLI command 'create-db-instance' with the MySQL engine and 20GB storage. Option A uses a non-existent command 'launch-db-instance'. Option A uses the wrong engine 'postgres'. Option A uses insufficient storage (5GB) which is below the minimum for MySQL RDS.

❓ Architecture

intermediate

Choosing the best subnet configuration for a highly available RDS instance

You want to launch an RDS instance that remains available even if one Availability Zone fails. Which subnet configuration should you choose?

A Launch the RDS instance in multiple public subnets in the same Availability Zone.

B Launch the RDS instance in a single public subnet in one Availability Zone.

C Launch the RDS instance in multiple private subnets across different Availability Zones using a DB subnet group.

D Launch the RDS instance in a single private subnet with a NAT gateway.

💡 Hint

Think about how AWS achieves high availability for RDS instances.

Option C is correct because RDS uses a DB subnet group with subnets in multiple Availability Zones to enable Multi-AZ deployments for high availability. Options B and C use a single subnet or AZ, which is not highly available. Option C uses multiple subnets but in the same AZ, so it does not protect against AZ failure.

❓ security

advanced

Securing RDS instance access with least privilege

You want to restrict access to your RDS instance so only your application servers in a specific security group can connect. Which configuration achieves this?

A Set the RDS instance's security group to allow inbound traffic on port 3306 from the application servers' security group.

B Set the RDS instance's security group to allow inbound traffic on port 3306 from 0.0.0.0/0.

C Set the RDS instance's security group to allow inbound traffic on port 3306 from the internet gateway.

D Set the RDS instance's security group to allow inbound traffic on port 3306 from the VPC CIDR block.

💡 Hint

Consider the principle of least privilege and how security groups reference each other.

Option A restricts access to only the application servers by referencing their security group, following least privilege. Option A allows access from anywhere, which is insecure. Option A incorrectly references the internet gateway, which is not a source IP. Option A allows access from the entire VPC, which is broader than needed.

❓ service_behavior

advanced

Understanding RDS Multi-AZ failover behavior

What happens to your RDS instance endpoint during a Multi-AZ failover event?

A The endpoint becomes unavailable until you restart the RDS instance.

B The endpoint DNS automatically points to the standby instance in the other Availability Zone with minimal downtime.

C You must manually update the endpoint to point to the new primary instance after failover.

D The endpoint IP address changes but DNS remains the same, causing connection failures.

💡 Hint

Think about how AWS manages failover to minimize impact on applications.

Option B is correct because AWS RDS automatically updates the DNS endpoint to point to the new primary instance during failover, minimizing downtime. Option B is incorrect because manual intervention is not required. Option B is wrong as the endpoint remains available after failover. Option B is incorrect because the DNS name remains the same and AWS manages IP changes transparently.

✅ Best Practice

expert

Optimizing cost and performance for a production RDS instance

You have a production RDS instance with steady traffic. You want to optimize for cost without sacrificing availability or performance. Which combination of configurations is best?

A Use a Single-AZ deployment with a db.m6g.large instance class and provisioned IOPS storage with autoscaling.

B Use a Single-AZ deployment with a db.t3.micro instance class and magnetic storage.

C Use a Multi-AZ deployment with a db.r5.2xlarge instance class and provisioned IOPS storage without autoscaling.

D Use a Multi-AZ deployment with a db.m6g.large instance class and enable storage autoscaling with General Purpose SSD (gp3).

💡 Hint

Balance availability, instance type, and storage type for cost and performance.

Option D balances cost and performance by using a cost-efficient ARM-based instance (m6g), Multi-AZ for availability, and gp3 storage with autoscaling for performance and cost control. Option D sacrifices availability and performance. Option D uses an expensive instance and storage without autoscaling, increasing cost. Option D sacrifices availability by using Single-AZ.

Practice

1. What is the main purpose of launching an Amazon RDS instance?

easy

A. To set up a virtual private network

B. To manually configure hardware for a database

C. To create a managed cloud database quickly

D. To write application code for database access

Solution

1. Step 1: Understand RDS service purpose

   Amazon RDS is a managed service that simplifies database setup and management.

2. Step 2: Identify the main benefit

   It allows quick creation of cloud databases without manual hardware setup.

3. Final Answer:

   To create a managed cloud database quickly -> Option C

4. Quick Check:

   RDS = managed cloud database creation [OK]

Hint: RDS means managed database, not manual hardware setup [OK]

Common Mistakes:

• Confusing RDS with manual server setup
• Thinking RDS is for network configuration
• Assuming RDS is for writing application code

2. Which of the following is a required parameter when launching an RDS instance using AWS Console?

easy

A. Database engine type (e.g., MySQL, PostgreSQL)

B. Operating system version of the server

C. IP address of the client machine

D. Number of application users

Solution

1. Step 1: Identify launch parameters for RDS

   When launching RDS, you must choose the database engine type like MySQL or PostgreSQL.

2. Step 2: Exclude unrelated parameters

   Operating system, client IP, or app users are not required inputs for RDS launch.

3. Final Answer:

   Database engine type (e.g., MySQL, PostgreSQL) -> Option A

4. Quick Check:

   Engine type is mandatory for RDS launch [OK]

Hint: Pick the database engine type, not unrelated details [OK]

Common Mistakes:

• Confusing OS version with database engine
• Providing client IP instead of DB settings
• Thinking user count is a launch parameter

3. Consider this AWS CLI command snippet to launch an RDS instance:

aws rds create-db-instance --db-instance-identifier mydb --db-instance-class db.t3.micro --engine mysql --master-username admin --master-user-password Pass1234 --allocated-storage 20

What will be the allocated storage size of the created RDS instance?

medium

A. Not specified, default used

B. 10 GB

C. 100 GB

D. 20 GB

Solution

1. Step 1: Locate storage parameter in command

   The parameter --allocated-storage 20 sets storage size to 20 GB.

2. Step 2: Confirm no other storage size overrides

   No other storage size is specified, so 20 GB is used.

3. Final Answer:

   20 GB -> Option D

4. Quick Check:

   Allocated storage = 20 GB [OK]

Hint: Look for --allocated-storage value in command [OK]

Common Mistakes:

• Assuming default storage without checking parameter
• Confusing instance class with storage size
• Ignoring the explicit storage size given

4. You tried launching an RDS instance but got an error: "InvalidParameterCombination: Storage size must be at least 20 GB for db.t3.micro". Your command was:

aws rds create-db-instance --db-instance-identifier testdb --db-instance-class db.t3.micro --engine postgres --master-username admin --master-user-password Pass1234 --allocated-storage 10

What is the cause of the error?

medium

A. Allocated storage size is below the minimum for the instance class

B. Master username is invalid

C. Engine type postgres is not supported

D. DB instance identifier is missing

Solution

1. Step 1: Analyze error message details

   The error says storage must be at least 20 GB for db.t3.micro, but 10 GB was given.

2. Step 2: Check command parameters

   The command uses --allocated-storage 10, which is too small for this instance class.

3. Final Answer:

   Allocated storage size is below the minimum for the instance class -> Option A

4. Quick Check:

   Storage size too small causes error [OK]

Hint: Check minimum storage size for instance class [OK]

Common Mistakes:

• Ignoring minimum storage requirements
• Blaming username or engine type incorrectly
• Missing required parameters in command

5. You want to launch an RDS instance with automatic backups enabled and a backup retention period of 7 days. Which configuration option should you set during launch to achieve this?

hard

A. Set MultiAZ to true

B. Set BackupRetentionPeriod to 7 and enable automatic backups

C. Set StorageEncrypted to true

D. Set PubliclyAccessible to true

Solution

1. Step 1: Identify backup settings for RDS

   Automatic backups require enabling backups and setting the retention period.

2. Step 2: Match configuration options

   BackupRetentionPeriod controls how many days backups are kept; enabling backups is necessary.

3. Step 3: Exclude unrelated options

   MultiAZ is for high availability, StorageEncrypted for encryption, and PubliclyAccessible for network access.

4. Final Answer:

   Set BackupRetentionPeriod to 7 and enable automatic backups -> Option B

5. Quick Check:

   BackupRetentionPeriod = 7 enables 7-day backups [OK]

Hint: BackupRetentionPeriod sets days for automatic backups [OK]

Common Mistakes:

• Confusing backup with MultiAZ or encryption settings
• Not enabling backups explicitly
• Setting unrelated network options