MY AWS RDS FAQ EXAM QUESTIONS

PDF Download

MY AWS RDS FAQ EXAM QUESTIONS

Actual Qs and Ans Expert-Verified Explanation

This Exam contains:

-Guarantee passing score -72 Questions and Answers -format set of multiple-choice -Expert-Verified Explanation

Question 1: What are the benefits of a Multi-AZ deployment?

Answer:

Enhanced DB durability and availability. Another implied benefit of running your DB instance as a Multi-AZ deployment is that DB instance failover is automatic and requires no administration. You are not required to monitor DB instance events and initiate manual DB instance recovery.

Question 2: How do I connect to an RDS DB instance in VPC?

Answer:

DB Instances deployed within a VPC can be accessed by EC2 instances deployed in the same VPC. If these instances are deployed in a public subnet with associated EIPs, you can access the EC2 instances via the internet. DB instances deployed within a VPC can be access from the Internet or from EC2 Instances outside the VPC via VPN or bastion hosts that you can launch in your public subnet. You can also setup a VPN Gateway that extends your corporate network into your VPC, and allows access to the RDS DB instances in that VPC.Question 3: Does RDS provide guidelines for deprecating engine versions that are currently supported?

Answer:

Major version releases are supported for at least 3 years after they are initially supported by RDS and minor versions are supported for at least 1 year.In some cases, we may deprecate specific major or minor versions sooner, such as when there are security issues. In this case, RDS will automatically upgrade your database engine to address the issue.

Question 4: Can I move my existing DB instances inside my VPC to outside VPC?

Answer:

Migration of DB instances from inside to outside VPC is not supported.Question 5: What precautions should I take to ensure that my DB instances in VPC are accessible by my application?

Answer:

You are responsible for modifying routing tables and networking ACLs in your VPC to ensure that your DB instance is reachable from your client instances in the VPC. For Multi-AZ deployments, after a failover, your client EC2 instance and RDS DB instance may be in different AZs. You should configure your networking ACLs to ensure that cross-AZ communication is possible.Question 6: What is a backup window and why do I need it? Is my RDS DB available during this time?

Answer:

The preferred backup window time is the user-defined period of time that your DB instance is backed up. AWS uses these periodic backups in conjunction with your transaction logs to enable restoring your database to any second within your retention period. During the backup window I/O may be briefly suspended (typically less than a few seconds) and elevated latency may occur. For Multi-AZ deployments this does not happen because the back up done on the standby database.

Question 7: What is an RDS Reserved Instance (RI)?

Answer:

RDS RI's can be purchased in one and three year terms at a significant discount. There are three purchasing options: all-upfront, partial-upfront, or no up-front. An RDS RI is a reserved DB instance.Question 8: How do I control if and when the engine version of my DB instance is upgraded to new supported versions?

Answer:

You can manually upgrade your DB to the most current minor version via the console or API. You can also choose the enable Auto Minor Version Upgrade so that this is done automatically. Scheduled upgrades on RDS will be communicated at least 30 days in advance. DB engine upgrades require downtime, even in multi-AZ deployments. Major upgrades will not occur automatically.For Oracle and SQL Server on RDS, if a minor upgrade required a change to a different edition it may not happen automatically (even if auto upgrade is enabled). The determination on whether to allow automatic upgrades will be made on a case-by-case basis.

Question 9: How do I scale the compute resources and/or storage resources associated with my RDS database?

Answer:

Memory and CPU can be modified by changing your instance class. Storage can be modified by changing you storage allocation. When you change your DB size you can choose to have changes applied during your maintenance window or immediately.You can Cloudwatch to track your compute and storage resource utilization for no additional charge.SQL server does not support increases your storage allocation at this time. This is a feature that will be available in the future.Question 10: What happens to my snapshots and RDS DB backups if I delete my DB instance?

Answer:

Automated backups are deleted when the DB instance is deleted.When deleting your instance you will be given the option to create one final snapshot. This snapshot and all other manual snapshots will persist even after the DB has been deleted and can be used to restore the DB at a later time.Question 11: What is the difference between automatic backups and manual snapshots in RDS?

Answer:

Automatic Backups: RDS automatically takes a daily complete snapshot of you database during the backup window. This snapshot can be stored from 7-35 days (depending on how you configure it). RDS also automatically captures transaction logs. This allows for a point-in-time recovery of your database.Manual Snapshots: Snapshots are initiated by the user and are retained until deleted. You can use them to restore your DB.Snapshots can be copied. Also, when you restore a DB from a snapshot it starts a new DB instance with a new endpoint. You can create multiple DBs from the same instance.

Question 12: How will I be charged for my use of RDS?

Answer:

DB Instance Hours, Storage (GB per month), I/O requests per month, Provisioned IOPS per month, Backup Storage, and Data Transfer

Question 13: When would I want to consider using an RDS Read Replica?

Answer:

Common reasons include: scaling beyond the compute or I/O capacity of a single DB instance for read-heavy database workloads, serving read traffic while the source DB instance is unavailable, and business reporting or data warehousing scenarios

Question 14: What do "primary" and "standby" mean in the context of a Multi-AZ deployment?

Answer:

The "primary" DB serves writes and reads. RDS provisions and maintains a "standby" DB behind the scenes, which is an up-to-date replica of the primary. The standby is "promoted" in failover scenarios.After failover, the standby becomes the primary and accepts your DB operations. You do not interact with the standby at any point prior to promotion.Question 15: What events would cause RDS to initiate a failover to the standby replica?

Answer:

RDS detects and automatically recovers from the most common failure scenarios for Multi-AZ deployments so that you can resume database operations as quickly as possible. RDS automatically

performs failover in the event of:

1) Loss of availability in primary AZ, 2) Loss of network connectivity to primary, 3) Compute unit failure on primary, 4) Storage failure on primary. When operation such as DB scaling or system upgrades are initiated for Multi-AZ deployments, for enhanced availability, they are applied first on the standby prior to an automatic failover. RDS deployments don't failover automatically in response to DB operations such as long running queries, deadlocks, or database corruption errors.

Question 16: What is Amazon RDS Provisioned IOPS (SSD) storage?

Answer:

RDS Provisioned IOPS (SSD) storage is suitable for high performance I/O workloads, it is designed to deliver fast, predictable, and consistent I/O performance. You specify the IOPS rate when provisioning the DB instance and RDS provisions that rate for the lifetime of the instance. This storage is optimized for OLTP workloads.Question 17: Can I encrypt connections between my application and my DB instance using SSL?

Answer:

Yes, this option is currently supported for the MySQL, MariaDB, SQL Server, PostgreSQL, and Oracle engines. RDS generates an SSL certificate for each DB instance. Once an encrypted connection is established, data transferred between the DB instance and your application will be encrypted during the transfer. Be aware that SSL encryption is a compute-intensive operation and will increase the latency of your database connection.