Question 1

What is Amazon RDS, and how does it differ from traditional database hosting?

Accepted Answer

Amazon RDS (Relational Database Service) is a fully managed service that automates database provisioning, patching, backups, and scaling in the cloud. Unlike traditional database hosting where you manage the OS, storage, and replication yourself, RDS handles all infrastructure level tasks so you can focus on schema design and application logic. Key differences from self managed databases: Automated backups with configurable retention (up to 35 days) One click Multi AZ failover for high availability Push button scaling for compute and storage without downtime Automated patching during configurable maintenance windows

Question 2

Which database engines does Amazon RDS support?

Accepted Answer

Amazon RDS supports six major relational database engines, giving you flexibility to use the engine your team already knows. Supported engines: Amazon Aurora (MySQL and PostgreSQL compatible, AWS native) MySQL MariaDB PostgreSQL Oracle Microsoft SQL Server Aurora is the only AWS built engine and offers up to 5x throughput over standard MySQL and 3x over standard PostgreSQL on RDS.

Question 3

How do you create a new RDS instance using the AWS Management Console?

Accepted Answer

Creating an RDS instance via the console involves selecting your engine, sizing, and network configuration. The wizard guides you through all required settings before launching the instance. Steps: Navigate to the RDS Dashboard and click Create database Choose a creation method ( Standard or Easy create ) and select your database engine Pick an instance class (e.g., db.t3.medium ) and allocate storage Configure VPC , subnet group , and security groups for network access Set the master username and password Configure backup retention , Multi AZ , and encryption options, then click Create database

Question 4

What are the steps to enable Multi-AZ deployments in RDS?

Accepted Answer

Multi AZ deployment creates a synchronous standby replica of your primary DB instance in a different Availability Zone . In a failover event, RDS automatically promotes the standby with no manual intervention and typically completes within 60 120 seconds. To enable it: During instance creation, select Multi AZ deployment under the Availability & durability section For an existing instance, click Modify , change the Multi AZ setting to Yes , and apply the change You can also enable it via the CLI:

Question 5

Describe the process of backing up an RDS instance.

Accepted Answer

RDS provides two complementary backup mechanisms: automated backups and manual snapshots . Automated backups occur daily during your configured backup window and enable point in time recovery to any second within your retention period (1 35 days). Automated backups store transaction logs every 5 minutes, enabling recovery to any point within the retention period Manual snapshots are user initiated and persist until you explicitly delete them Both backup types are stored in Amazon S3 and are region specific by default To create a manual snapshot via CLI:

Question 6

How can you monitor the performance of an RDS instance?

Accepted Answer

Amazon RDS offers three tiers of monitoring to help you identify and resolve performance bottlenecks. Each tier provides progressively deeper visibility into your database behavior. Amazon CloudWatch tracks instance level metrics such as CPU utilization, free memory, read/write IOPS, and network throughput at 1 minute granularity Enhanced Monitoring provides real time OS level metrics (per process CPU, memory, file system usage) at up to 1 second granularity Performance Insights visualizes database load by wait events, SQL statements, hosts, and users, making it easy to spot the exact queries causing bottlenecks You can also enable slow query logs and general logs for engine level diagnostics.

Question 7

What is the purpose of parameter groups in RDS?

Accepted Answer

Parameter groups are named collections of database engine configuration values that control runtime behavior of your RDS instances. Instead of modifying config files directly, you create a custom parameter group, adjust settings, and associate it with one or more instances. DB parameter groups apply engine level settings (e.g., max connections , innodb buffer pool size for MySQL) Changes to dynamic parameters take effect immediately; static parameters require a reboot The default parameter group is read only, so you must create a custom group to change any settings Example of modifying a parameter:

Question 8

Explain the concept of read replicas in RDS and their use cases.

Accepted Answer

Read replicas are asynchronously replicated, read only copies of your primary RDS instance. They offload read traffic from the primary database, improving overall throughput for read heavy workloads. Key use cases: Read scaling distribute SELECT queries across multiple replicas to reduce load on the primary Analytics and reporting run expensive queries on a replica without impacting production writes Cross region disaster recovery create replicas in other AWS regions for geographic redundancy Migration promote a cross region replica to a standalone instance for region migration You can create up to 5 read replicas per source instance (15 for Aurora). Replication lag is typically under a second but varies with write volume.

AWS RDS