Chapter 4 - DATABASES: Amazon RDS, Amazon Aurora, Amazon DynamoDB, Elasticache, Amazon DocumentDB Flashcards
How can you increase the high availability of Amazon RDS?
- Create periodic snapshot of main DB Instance in another AZ
- Use RDS Multi-AZ deployment
- Use RDS Read Replicas
- Create two similar DB instances in separate AZ and do periodic synchronization
- Create periodic snapshot of main DB Instance in another AZ
- Use RDS Multi-AZ deployment
- Use RDS Read Replicas
- Create two similar DB instances in separate AZ and do periodic synchronization
How Amazon RDS provides high availability? Choose 2.
- Amazon RDS provides high availability through Multi-AZ deployment
- Amazon RDS provides high availability through Read Replicas
- In a Multi-AZ deployment automatically provisions and maintains a synchronous standby replica in a different Availability Zone.
- In a Multi-AZ deployment automatically provisions and maintains an asynchronous standby read replica in a different Availability Zone.
- Amazon RDS provides high availability through Multi-AZ deployment
- Amazon RDS provides high availability through Read Replicas
- In a Multi-AZ deployment automatically provisions and maintains a synchronous standby replica in a different Availability Zone.
- In a Multi-AZ deployment automatically provisions and maintains an asynchronous standby read replica in a different Availability Zone.
Which database engines are supported by Amazon RDS?
- MySQL, MariaDB, PostgreSQL, Oracle, Microsoft SQL Server
- MySQL, MariaDB, PostgreSQL, Oracle, Microsoft SQL Server, Amazon Aurora
- MySQL, PostgreSQL, Oracle, Microsoft SQL Server, Amazon Aurora
- MySQL, MariaDB, Oracle, Microsoft SQL Server, Amazon Aurora
- MySQL, MariaDB, PostgreSQL, Oracle, Microsoft SQL Server
- MySQL, MariaDB, PostgreSQL, Oracle, Microsoft SQL Server, Amazon Aurora
- MySQL, PostgreSQL, Oracle, Microsoft SQL Server, Amazon Aurora
- MySQL, MariaDB, Oracle, Microsoft SQL Server, Amazon Aurora
Which AWS database service will you choose for Online Transaction Processing (OLTP)?
- Amazon RDS
- Amazon Redshift
- Amazon Glacier
- Amazon DynamoDB
- Amazon RDS
- Amazon Redshift
- Amazon Glacier
- Amazon DynamoDB
What are three types of instance classes supported by Amazon RDS?
- Standard
- Memory Optimized
- Burstable Performance
- Performance Optimized
- Standard
- Memory Optimized
- Burstable Performance
- Performance Optimized
Which automated monitoring tools you can use to watch Amazon RDS and report when something is wrong? Choose 4.
- Amazon RDS Events
- Database log files
- Amazon Inspector
- Amazon RDS Enhanced Monitoring
- Amazon CloudWatch
- Amazon RDS Events
- Database log files
- Amazon Inspector
- Amazon RDS Enhanced Monitoring
- Amazon CloudWatch
What does Amazon RDS manages on user’s behalf? Choose 2.
- Provisioning the infrastructure capacity requested to installing the database software.
- Once database is up and running, Amazon RDS automates common administrative tasks such as performing backups and patching the software that powers your database
- Managing the database settings that are specific to your application.
- Automatic performance tuning to optimize your database for your application’s workflow.
- Provisioning the infrastructure capacity requested to installing the database software.
- Once database is up and running, Amazon RDS automates common administrative tasks such as performing backups and patching the software that powers your database
- Managing the database settings that are specific to your application.
- Automatic performance tuning to optimize your database for your application’s workflow.
What are the steps taken by RDS when you modify DB instance in a Single-AZ deployment to be a Multi-AZ deployment (for engines other than SQL Server or Amazon Aurora)? Choose 2.
- Step 1. Amazon RDS takes a snapshot of the primary DB instance from your deployment and then restores the snapshot into another Availability Zone.
- Step 1. Amazon RDS creates a fresh DB instance with similar configuration as primary DB instance and then copies data from primary to secondary.
- Step2. Amazon RDS then sets up asynchronous replication between your primary DB instance and the new instance.
- Step2. Amazon RDS then sets up synchronous replication between your primary DB instance and the new instance.
- Step 1. Amazon RDS takes a snapshot of the primary DB instance from your deployment and then restores the snapshot into another Availability Zone.
- Step 1. Amazon RDS creates a fresh DB instance with similar configuration as primary DB instance and then copies data from primary to secondary.
- Step2. Amazon RDS then sets up asynchronous replication between your primary DB instance and the new instance.
- Step2. Amazon RDS then sets up synchronous replication between your primary DB instance and the new instance.
What are the possible scenarios in case of RDS Multi-AZ deployment when primary DB instance switches over automatically to the standby replica? Choose 3.
- An Availability Zone outage or when the primary DB instance fails.
- The DB instance’s server type is changed or the operating system of the DB instance is undergoing software patching.
- A manual failover of the DB instance was initiated using Reboot with failover or when an Availability Zone outage or when the primary DB instance fails.
- When server performance is deteriorating.
- An Availability Zone outage or when the primary DB instance fails.
- The DB instance’s server type is changed or the operating system of the DB instance is undergoing software patching.
- A manual failover of the DB instance was initiated using Reboot with failover or when an Availability Zone outage or when the primary DB instance fails.
- When server performance is deteriorating.
You are an IT administrator of a company which has a SaaS product developed using AWS platform. You have enabled multi-AZ deployment for the product RDS database. Few days after the release you get an alert from DB event notification on your mobile phone that your primary Amazon RDS instance has failed. What should you do ensure that your production environment is available to users by ensuring a fast seamless failover to secondary instance?
- Update the DB connection string used by application server to secondary database instance.
- Create a new primary instance by making a copy from the secondary instance.
- No need to do anything, Amazon RDS handles failovers automatically so you can resume database operations as quickly as possible without administrative intervention.
- Update the DNS record of the DB instance to point to the standby DB instance.
- Update the DB connection string used by application server to secondary database instance.
- Create a new primary instance by making a copy from the secondary instance.
- No need to do anything, Amazon RDS handles failovers automatically so you can resume database operations as quickly as possible without administrative intervention.
- Update the DNS record of the DB instance to point to the standby DB instance.
Which database engines supported by Amazon RDS have multi-AZ?
- MySQL, MariaDB, PostgreSQL, Oracle, Microsoft SQL Server
- MySQL, MariaDB, PostgreSQL, Oracle, Microsoft SQL Server, Amazon Aurora
- MySQL, PostgreSQL, Oracle, Microsoft SQL Server, Amazon Aurora
- MySQL, MariaDB, Oracle, Microsoft SQL Server, Amazon Aurora
- MySQL, MariaDB, PostgreSQL, Oracle, Microsoft SQL Server
- MySQL, MariaDB, PostgreSQL, Oracle, Microsoft SQL Server, Amazon Aurora
- MySQL, PostgreSQL, Oracle, Microsoft SQL Server, Amazon Aurora
- MySQL, MariaDB, Oracle, Microsoft SQL Server, Amazon Aurora
You are an IT administrator of a company which has a SaaS product developed using AWS platform. You have enabled multi-AZ deployment for the product RDS database. You know that AWS automatically failovers to secondary instance when primary instance fails. Before going to production you want to simulate and test this failover. What is the simplest way to test?
- You have to wait for the new software patch to download for the DB instance.
- Initiate the snapshot creation of primary instance which will make AWS switch to secondary.
- Reboot the primary instance.
- Delete the primary instance.
- You have to wait for the new software patch to download for the DB instance.
- Initiate the snapshot creation of primary instance which will make AWS switch to secondary.
- Reboot the primary instance.
- Delete the primary instance.
What are the features provided by Amazon RDS Multi-AZ deployments? Choose 2.
- Enhanced availability
- Enhanced Durability
- Enhanced performance
- Network latency reduction
- Enhanced availability
- Enhanced Durability
- Enhanced performance
- Network latency reduction
What is the differences between Single-AZ and Multi-AZ deployment during backup activity? Choose 3.
- In Single-AZ deployments, I/O activity is suspended on your primary during backup.
- In Multi-AZ deployments, I/O activity is not suspended on your primary during backup, because the backup is taken from the standby.
- In Multi-AZ deployments, I/O activity is suspended on your primary during backup.
- There will be elevated latencies for a few minutes during backups for Multi-AZ deployments.
- In Single-AZ deployments, I/O activity is suspended on your primary during backup.
- In Multi-AZ deployments, I/O activity is not suspended on your primary during backup, because the backup is taken from the standby.
- In Multi-AZ deployments, I/O activity is suspended on your primary during backup.
- There will be elevated latencies for a few minutes during backups for Multi-AZ deployments.
How is instance failure handled in Amazon Aurora deployment? Choose 2.
- Amazon Aurora uses RDS Multi-AZ technology to automate failover to one of up to 15 Amazon Aurora Replicas created in any of three Availability Zones.
- Amazon Aurora Multi-AZ deployment feature has to be enabled specifically to automate failover to one of up to 15 Amazon Aurora Replicas created in any of three Availability Zones.
- If no Amazon Aurora Replicas have been provisioned, in the case of a failure, you have to manually create a new Amazon Aurora DB instance.
- f no Amazon Aurora Replicas have been provisioned, in the case of a failure, Amazon RDS will attempt to create a new Amazon Aurora DB instance for you automatically.
- Amazon Aurora uses RDS Multi-AZ technology to automate failover to one of up to 15 Amazon Aurora Replicas created in any of three Availability Zones.
- Amazon Aurora Multi-AZ deployment feature has to be enabled specifically to automate failover to one of up to 15 Amazon Aurora Replicas created in any of three Availability Zones.
- If no Amazon Aurora Replicas have been provisioned, in the case of a failure, you have to manually create a new Amazon Aurora DB instance.
- If no Amazon Aurora Replicas have been provisioned, in the case of a failure, Amazon RDS will attempt to create a new Amazon Aurora DB instance for you automatically.
How Amazon Aurora MySQL provides Fault-Tolerant and Self-Healing Storage? Choose 3.
- Each 10GB chunk of your database volume is replicated six ways, across three Availability Zones.
- Transparently handles the loss of up to two copies of data without affecting database write availability and up to three copies without affecting read availability.
- Data blocks and disks are continuously scanned for errors and replaced automatically.
- Each 10GB chunk of your database volume is replicated three ways, across three Availability Zones.
- Each 10GB chunk of your database volume is replicated six ways, across three Availability Zones.
- Transparently handles the loss of up to two copies of data without affecting database write availability and up to three copies without affecting read availability.
- Data blocks and disks are continuously scanned for errors and replaced automatically.
- Each 10GB chunk of your database volume is replicated three ways, across three Availability Zones.
You are designing an application whose storage needs is very hard to predict. You don’t want to continuously monitor and increase the storage size of your RDBMS database. You want to use MySQL DB. Cost, availability and reliability is also your consideration. Which Amazon service you will use? Choose 2.
- MySQL installed on EC2
- RDS with MySQL
- Aurora with MySQL
- Serverless Aurora
- MySQL installed on EC2
- RDS with MySQL
- Aurora with MySQL
- Serverless Aurora
What is the maximum retention value you can set in RDS?
- 15 days
- 35 days
- 25 days
- 45 days
- 15 days
- 35 days
- 25 days
- 45 days
How many copies of your data Aurora stores?
- 3
- 4
- 5
- 6
- 3
- 4
- 5
- 6
What is Aurora Global Database? Choose 2
- Aurora global database consists of one primary AWS Region where your data is mastered, and one read-only, secondary AWS Region
- urora global database consists of one primary AWS AZ where your data is mastered, and one read-only, secondary AZ
- Only the primary cluster performs write operations.
- Secondary performs both read and write.
- Aurora global database consists of one primary AWS Region where your data is mastered, and one read-only, secondary AWS Region
- urora global database consists of one primary AWS AZ where your data is mastered, and one read-only, secondary AZ
- Only the primary cluster performs write operations.
- Secondary performs both read and write.
What is the default backup retention period if you create the RDS DB instance using the console?
- 1 day
- 7 days
- 35 days
- 0 day
- 1 day
- 7 days
- 35 days
- 0 day
What is the default backup retention period if you create the RDS DB instance using Amazon RDS API or the AWS CLI.?
- 1 day
- 7 days
- 35 days
- 0 day
- 1 day
- 7 days
- 35 days
- 0 day
You can set up the RDS backup retention period to between 0 and 35 days. What is the effect of setting the value to 0?
- Retention period is set to 1 hour
- Retention period is set to default value of seven days
- Disables automated backups
- Retention period is set to default value of one day
- Retention period is set to 1 hour
- Retention period is set to default value of seven days
- Disables automated backups
- Retention period is set to default value of one day
Which of the following statements are correct about RDS backups? Choose 3.
- Amazon RDS creates and saves automated backups of your DB instance.
- Amazon RDS creates a storage volume snapshot of your DB instance, backing up the entire DB instance and not just individual databases.
- Amazon RDS creates a storage volume snapshot of your DB instance, backing up only individual databases chosen by you.
- You can also back up your DB instance manually, by manually creating a DB snapshot.
- Amazon RDS creates and saves automated backups of your DB instance.
- Amazon RDS creates a storage volume snapshot of your DB instance, backing up the entire DB instance and not just individual databases.
- Amazon RDS creates a storage volume snapshot of your DB instance, backing up only individual databases chosen by you.
- You can also back up your DB instance manually, by manually creating a DB snapshot.
You have used Multi-AZ deployment for Amazon RDS instances for your web application to achieve enhanced database availability and durability. You know that Amazon RDS maintains an up-to-date standby instance which is synchronously updated. What happens during Multi-AZ failover? Choose 2.
- Failover is automatically handled by Amazon RDS so that you can resume database operations as quickly as possible without administrative intervention.
- Amazon RDS simply flips the canonical name record (CNAME) for your DB instance to point at the standby, which is in turn promoted to become the new primary.
- Amazon RDS simply flips the canonical name record (CNAME) for your DB instance to point at alternate ‘failover’ record which needs to be created by you in the Route 53 hosted zone .
- Amazon RDS simply flips the A Record type for your DB instance to point at the standby, which is in turn promoted to become the new primary.
- Amazon RDS simply flips the A Record type for your DB instance to point at alternate ‘failover’ record which needs to be created by you in the Route 53 hosted zone.
- Failover is automatically handled by Amazon RDS so that you can resume database operations as quickly as possible without administrative intervention.
- Amazon RDS simply flips the canonical name record (CNAME) for your DB instance to point at the standby, which is in turn promoted to become the new primary.
- Amazon RDS simply flips the canonical name record (CNAME) for your DB instance to point at alternate ‘failover’ record which needs to be created by you in the Route 53 hosted zone .
- Amazon RDS simply flips the A Record type for your DB instance to point at the standby, which is in turn promoted to become the new primary.
- Amazon RDS simply flips the A Record type for your DB instance to point at alternate ‘failover’ record which needs to be created by you in the Route 53 hosted zone.
Which of the following statements is correct about RDS backups?
- Amazon RDS creates automated backups of your DB instance during the backup window of your DB instance.
- Amazon RDS saves the automated backups of your DB instance according to the backup retention period that you specify.
- You can recover your database to any point in time during the backup retention period.
- All of the above
- Amazon RDS creates automated backups of your DB instance during the backup window of your DB instance.
- Amazon RDS saves the automated backups of your DB instance according to the backup retention period that you specify.
- You can recover your database to any point in time during the backup retention period.
- All of the above
RDS Automated backups occur daily during the preferred backup window. While creating the RDS DB instance you didn’t specified the preferred backup window. What will happen?
- RDS will not take automated backups.
- RDS assigns a default 30-minute backup window.
- RDS will not allow to take manual backups.
- RDS will not create the DB instance.
- RDS will not take automated backups.
- RDS assigns a default 30-minute backup window.
- RDS will not allow to take manual backups.
- RDS will not create the DB instance.
RDS gives you the flexibility of automated backup as well as manual backup by taking snapshots. Which of the following three statements are correct? Choose 3.
- The first snapshot of a DB instance contains the data for the full DB instance.
- Subsequent snapshots of the same DB instance are incremental, which means that only the data that has changed after your most recent snapshot is saved.
- Subsequent snapshots of the same DB instance also contains the data of the full DB instance.
- You can copy both automatic and manual DB snapshots, and share manual DB snapshots.
- The first snapshot of a DB instance contains the data for the full DB instance.
- Subsequent snapshots of the same DB instance are incremental, which means that only the data that has changed after your most recent snapshot is saved.
- Subsequent snapshots of the same DB instance also contains the data of the full DB instance.
- You can copy both automatic and manual DB snapshots, and share manual DB snapshots.
You are sun setting an application. As part of the process you are going to delete the RDS DB instance but you want to retain the automated backups. What step can you take?
- If you delete a RDS DB Instance there is no option to retain the automated backups.
- You have to manually create copies of automated backups.
- You can take snapshot of DB Instance before deleting it.
- Choose Retain automated backups when you delete a DB instance.
- If you delete a RDS DB Instance there is no option to retain the automated backups.
- You have to manually create copies of automated backups.
- You can take snapshot of DB Instance before deleting it.
- Choose Retain automated backups when you delete a DB instance.
What is DB parameter group and DB option group? Choose 2.
- A DB option group acts as a container for engine configuration values that are applied to one or more DB instances.
- A DB parameter group acts as a container for engine feature which is empty by default.
- A DB parameter group acts as a container for engine configuration values that are applied to one or more DB instances.
- A DB option group acts as a container for engine feature which is empty.
- A DB option group acts as a container for engine configuration values that are applied to one or more DB instances.
- A DB parameter group acts as a container for engine feature which is empty by default.
- A DB parameter group acts as a container for engine configuration values that are applied to one or more DB instances.
- A DB option group acts as a container for engine feature which is empty.
What is Recovery Time Objective (RTO)?
- The time it takes after a disruption to restore a database to its service level, as defined by the operational level agreement (OLA).
- The acceptable amount of performance loss measured in time.
- The time it takes after a disruption to restore a business process to its service level, as defined by the operational level agreement (OLA).
- The acceptable amount of data loss measured in time.
- The time it takes after a disruption to restore a database to its service level, as defined by the operational level agreement (OLA).
- The acceptable amount of performance loss measured in time.
- The time it takes after a disruption to restore a business process to its service level, as defined by the operational level agreement (OLA).
- The acceptable amount of data loss measured in time.
What is Recovery Point Objective (RPO)?
- The time it takes after a disruption to restore a database to its service level, as defined by the operational level agreement (OLA).
- The acceptable amount of performance loss measured in time.
- The time it takes after a disruption to restore a business process to its service level, as defined by the operational level agreement (OLA).
- The acceptable amount of data loss measured in time.
- The time it takes after a disruption to restore a database to its service level, as defined by the operational level agreement (OLA).
- The acceptable amount of performance loss measured in time.
- The time it takes after a disruption to restore a business process to its service level, as defined by the operational level agreement (OLA).
- The acceptable amount of data loss measured in time.
Which Amazon RDS storage types will you choose for High-performance OLTP workloads and Database workloads with moderate I/O requirements? Choose 2.
- High-performance OLTP workloads: Amazon RDS Provisioned IOPS (SSD) Storage
- Database workloads with moderate I/O requirements: Amazon RDS General Purpose (SSD) Storage
- High-performance OLTP workloads: Amazon RDS General Purpose (SSD) Storage
- Database workloads with moderate I/O requirements: Amazon RDS Provisioned IOPS (SSD) Storage
- High-performance OLTP workloads: Amazon RDS Provisioned IOPS (SSD) Storage
- Database workloads with moderate I/O requirements: Amazon RDS General Purpose (SSD) Storage
- High-performance OLTP workloads: Amazon RDS General Purpose (SSD) Storage
- Database workloads with moderate I/O requirements: Amazon RDS Provisioned IOPS (SSD) Storage
Where are RDS automated backups and DB snapshots stored?
- EBS
- DynamoDB
- S3
- DocumentDB
- EBS
- DynamoDB
- S3
- DocumentDB
What DB instances for Amazon RDS for MySQL, MariaDB, PostgreSQL, Oracle, and Microsoft SQL Server use for database and log storage?
- S3
- EBS
- EFS
- Redshift
- S3
- EBS
- EFS
- Redshift
If a disaster occurs at 12:00 PM (noon) and the RTO is eight hours, by what time the DR process should restore the business process to the acceptable service level?
- 8 PM
- 4 AM
- 4 PM
- 8AM
- 8 PM
- 4 AM
- 4 PM
- 8AM
If a disaster occurs at 12:00 PM (noon) and the RPO is one hour, by how much time system should recover data?
- 11 PM
- 11 AM
- 1 PM
- 1 AM
- 11 PM
- 11 AM
- 1 PM
- 1 AM
DB instances for Amazon RDS use following for database and log storage.
- Elastic Block Store (Amazon EBS) volumes
- Amazon S3
- Amazon Aurora
- MySQL, MariaDB, PostgreSQL, Oracle, and Microsoft SQL Server
- Elastic Block Store (Amazon EBS) volumes
- Amazon S3
- Amazon Aurora
- MySQL, MariaDB, PostgreSQL, Oracle, and Microsoft SQL Server
What are the three storage types provided by RDS?
- Throughput Optimized
- General Purpose SSD
- Provisioned IOPS
- Magnetic
- Throughput Optimized
- General Purpose SSD
- Provisioned IOPS
- Magnetic
Which storage types provided by RDS will you use for production application that requires fast and consistent I/O performance?
- Throughput Optimized
- General Purpose SSD
- Provisioned IOPS
- Magnetic
- Throughput Optimized
- General Purpose SSD
- Provisioned IOPS
- Magnetic
What are the characteristics of RDS Provisioned IOPS SSD Storage type? Choose 3.
- Delivers predictable performance, and consistently low latency.
- Optimized for online transaction processing (OLTP) workloads that have consistent performance requirements.
- When you create a DB instance, you specify an IOPS rate and the size of the volume.
- Designed for throughput-intensive workloads.
- Delivers predictable performance, and consistently low latency.
- Optimized for online transaction processing (OLTP) workloads that have consistent performance requirements.
- When you create a DB instance, you specify an IOPS rate and the size of the volume.
- Designed for throughput-intensive workloads.
What are the factors that can affect RDS storage performance?
- System activities: Multi-AZ standby creation, Read replica creation, changing storage types
- Database or application design resulting in concurrency issues, locking, or other forms of database contention.
- Instance type not with enough bandwidth to support your storage type.
- All of the above
- System activities: Multi-AZ standby creation, Read replica creation, changing storage types
- Database or application design resulting in concurrency issues, locking, or other forms of database contention.
- Instance type not with enough bandwidth to support your storage type.
- All of the above
Which amazon RDS database engine supports read replica?
- MySQL, MariaDB, PostgreSQL, Oracle, Microsoft SQL Server
- MySQL, MariaDB, PostgreSQL, Oracle, Amazon Aurora
- MySQL, PostgreSQL, Oracle, Microsoft SQL Server, Amazon Aurora
- MySQL, MariaDB, Oracle, Microsoft SQL Server, Amazon Aurora
- MySQL, MariaDB, PostgreSQL, Oracle, Microsoft SQL Server
- MySQL, MariaDB, PostgreSQL, Oracle, Amazon Aurora
- MySQL, PostgreSQL, Oracle, Microsoft SQL Server, Amazon Aurora
- MySQL, MariaDB, Oracle, Microsoft SQL Server, Amazon Aurora
Which of the following scenarios are apt for deploying one or more Read Replicas for a given source DB instance? Choose 2.
- 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.
- Improving performance of a single DB instance for update heavy database workloads.
- Serving update traffic while the source DB instance is unavailable.
- 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.
- Improving performance of a single DB instance for update heavy database workloads.
- Serving update traffic while the source DB instance is unavailable.
Which of the following scenarios are apt for deploying one or more Read Replicas for a given source DB instance? Choose 2.
- Business reporting or data warehousing scenarios where you might want business reporting queries to run against a Read Replica, rather than your primary, production DB instance.
- For storing user session data.
- Implementing disaster recovery.
- All of the above.
- Business reporting or data warehousing scenarios where you might want business reporting queries to run against a Read Replica, rather than your primary, production DB instance.
- For storing user session data.
- Implementing disaster recovery.
- All of the above.
Which of the following statements are true regarding Amazon RDS Read Replica? Choose 2.
- Amazon RDS takes a snapshot of the source instance and creates a read-only instance from the snapshot.
- Amazon RDS uses the synchronous replication method for the DB engine to update the Read Replica whenever there is a change to the source DB instance.
- You have to create manually a separate copy of the main primary DB instance and mark it as Read Replica.
- Amazon RDS uses the asynchronous replication method for the DB engine to update the Read Replica whenever there is a change to the source DB instance.
- Amazon RDS takes a snapshot of the source instance and creates a read-only instance from the snapshot.
- Amazon RDS uses the synchronous replication method for the DB engine to update the Read Replica whenever there is a change to the source DB instance.
- You have to create manually a separate copy of the main primary DB instance and mark it as Read Replica.
- Amazon RDS uses the asynchronous replication method for the DB engine to update the Read Replica whenever there is a change to the source DB instance.
Which of the following statements are true regarding Amazon RDS Read Replica? Choose 2.
- The Read Replica operates as a DB instance that allows update-only connections.
- Amazon RDS replicates only those databases chosen by the user in the source DB instance.
- The Read Replica operates as a DB instance that allows read-only connections.
- Amazon RDS replicates all databases in the source DB instance.
- The Read Replica operates as a DB instance that allows update-only connections.
- Amazon RDS replicates only those databases chosen by the user in the source DB instance.
- The Read Replica operates as a DB instance that allows read-only connections.
- Amazon RDS replicates all databases in the source DB instance.
Which of the following statements are false regarding Amazon RDS Read Replica? Choose 2.
- Amazon RDS doesn’t support circular replication.
- Amazon RDS supports circular replication.
- Read Replica can resides in a different AWS Region than its source DB instance.
- Read Replica cannot resides in a different AWS Region than its source DB instance.
- Amazon RDS doesn’t support circular replication.
- Amazon RDS supports circular replication.
- Read Replica can resides in a different AWS Region than its source DB instance.
- Read Replica cannot resides in a different AWS Region than its source DB instance.
Which Amazon RDS database engine is fully compatible with MySQL and PostgreSQL?
- Amazon RDS for MySQL
- Amazon RDS for PostgreSQL
- Amazon RDS Aurora
- Amazon RDS for Oracle
- Amazon RDS for MySQL
- Amazon RDS for PostgreSQL
- Amazon RDS Aurora
- Amazon RDS for Oracle
What are the characteristics of Amazon Aurora DB Cluster? Choose 3.
- Two types of DB instances make up an Aurora DB cluster: Primary DB instance & Aurora Replica
- For primary DB instance failover you need to have a separate instance apart from Replica.
- Primary DB instance supports read and write operations, and performs all of the data modifications to the cluster volume. Each Aurora DB cluster has one primary DB instance.
- Aurora Replica connects to the same storage volume as the primary DB instance and supports only read operations. Each Aurora DB cluster can have up to 15 Aurora Replicas in addition to the primary DB instance.
- Two types of DB instances make up an Aurora DB cluster: Primary DB instance & Aurora Replica
- For primary DB instance failover you need to have a separate instance apart from Replica.
- Primary DB instance supports read and write operations, and performs all of the data modifications to the cluster volume. Each Aurora DB cluster has one primary DB instance.
- Aurora Replica connects to the same storage volume as the primary DB instance and supports only read operations. Each Aurora DB cluster can have up to 15 Aurora Replicas in addition to the primary DB instance.
What are different endpoints available in RDS Aurora? Choose 3.
- Cluster endpoint
- Reader endpoint
- Write endpoint
- Custom endpoint
- Cluster endpoint
- Reader endpoint
- Write endpoint
- Custom endpoint
Select statements which are correct for RDS Aurora storage? Choose 3.
- Aurora cluster volumes automatically grow as the amount of data in your database increases.
- An Aurora cluster volume can grow to a maximum size of 64 tebibytes (TiB).
- An Aurora cluster volume can grow to a maximum size of 64 terabytes (TB).
- Aurora data is stored in the cluster volume consisting of copies of the data across multiple Availability Zones in a single AWS Region.
- Aurora cluster volumes automatically grow as the amount of data in your database increases.
- An Aurora cluster volume can grow to a maximum size of 64 tebibytes (TiB).
- An Aurora cluster volume can grow to a maximum size of 64 terabytes (TB).
- Aurora data is stored in the cluster volume consisting of copies of the data across multiple Availability Zones in a single AWS Region.
You are the architect of a payment gateway provider and anticipating a fivefold increase in traffic in the upcoming shopping season. You are using RDS with MySQL as database engine. During load testing you notice a decrease in query performance with increase in traffic. Which of the following options you could do immediately to increase database performance?
- Instead of MySQL use Oracle or SQL Server.
- Instead of MySQL use DynamoDB.
- Use Multi-AZ deployment option to increase read and write performance.
- Use Read Replicas and redirect read queries to those replicas.
- Instead of MySQL use Oracle or SQL Server.
- Instead of MySQL use DynamoDB.
- Use Multi-AZ deployment option to increase read and write performance.
- Use Read Replicas and redirect read queries to those replicas.
How many read replicas you can create for RDS MySQL?
- 5
- 10
- 15
- 20
- 5
- 10
- 15
- 20
How many read replicas you can create for RDS Aurora?
- 5
- 10
- 15
- 20
- 5
- 10
- 15
- 20
What is the main benefit of Read Replica?
- Improving performance
- Improving Security
- Improving Availability
- Improving Durability
- Improving performance
- Improving Security
- Improving Availability
- Improving Durability
How does read replica provide increase availability? Choose 2.
- You can make a snapshot from a read replica and promote if the source DB instance fails.
- You can promote a read replica if the source DB instance fails.
- You can set up a read replica with its own standby instance in different AZ.
- Read replica automatically enables Multi-AZ deployment.
- You can make a snapshot from a read replica and promote if the source DB instance fails.
- You can promote a read replica if the source DB instance fails.
- You can set up a read replica with its own standby instance in different AZ.
- Read replica automatically enables Multi-AZ deployment.
Which RDS features you can combine to architect your application database for high availability and read scalability? Choose 2.
- Configure source database as Multi-AZ for high availability
- Create Read Replica for read scalability
- Create Read Replica for high availability
- Configure Multi-AZ for read scalability
- Configure source database as Multi-AZ for high availability
- Create Read Replica for read scalability
- Create Read Replica for high availability
- Configure Multi-AZ for read scalability
With RDS for MySQL, MariaDB, PostgreSQL, and Oracle how you can use the read replica as a DR target?
- Read Replicas are enabled as DR target by default.
- Set the read replica as Multi-AZ, allowing you to use the read replica as a DR target.
- Set the read replica as Single-AZ, allowing you to use the read replica as a DR target.
- None of the above.
- Read Replicas are enabled as DR target by default.
- Set the read replica as Multi-AZ, allowing you to use the read replica as a DR target.
- Set the read replica as Single-AZ, allowing you to use the read replica as a DR target.
- None of the above.
Amazon RDS read replicas complement Multi-AZ deployments. While both features maintain a second copy of your data, choose two differences from the following list.
- In Read Replicas only database engine on primary instance is active while in Multi-AZ all replicas are accessible and can be used for read scaling.
- Multi-AZ Deployments have synchronous replication and is highly durable while Read Replicas have Asynchronous replication and is highly scalable.
- In Multi-AZ only database engine on primary instance is active while in Read Replicas all read replicas are accessible and can be used for read scaling.
- Read Replicas have synchronous replication and is highly durable while Multi-AZ have Asynchronous replication and is highly scalable.
- In Read Replicas only database engine on primary instance is active while in Multi-AZ all replicas are accessible and can be used for read scaling.
- Multi-AZ Deployments have synchronous replication and is highly durable while Read Replicas have Asynchronous replication and is highly scalable.
- In Multi-AZ only database engine on primary instance is active while in Read Replicas all read replicas are accessible and can be used for read scaling.
- Read Replicas have synchronous replication and is highly durable while Multi-AZ have Asynchronous replication and is highly scalable.
Amazon RDS read replicas complement Multi-AZ deployments. While both features maintain a second copy of your data, choose two differences from the following list.
- In Multi-AZ Automated backups are taken from standby while in Read Replicas no backups configured by default.
- In Read Replicas Automated backups are taken from standby while In Multi-AZ no backups configured by default.
- Read Replicas always span two Availability Zones within a single Region while Multi-AZ can be within an Availability Zone, Cross-AZ, or Cross-Region.
- Multi-AZ always span two Availability Zones within a single Region while Read Replicas can be within an Availability Zone, Cross-AZ, or Cross-Region.
- In Multi-AZ Automated backups are taken from standby while in Read Replicas no backups configured by default.
- In Read Replicas Automated backups are taken from standby while In Multi-AZ no backups configured by default.
- Read Replicas always span two Availability Zones within a single Region while Multi-AZ can be within an Availability Zone, Cross-AZ, or Cross-Region.
- Multi-AZ always span two Availability Zones within a single Region while Read Replicas can be within an Availability Zone, Cross-AZ, or Cross-Region.
Which of the following statements are correct for RDS Multi-AZ and Read Replica? Choose 2.
- In Multi-AZ automatic failover to standby when a problem is detected.
- In Read Replica automatic failover to standby when a problem is detected.
- In Multi-AZ, instance can be manually promoted to a standalone database instance.
- In Read Replica, instance can be manually promoted to a standalone database instance.
- In Multi-AZ automatic failover to standby when a problem is detected.
- In Read Replica automatic failover to standby when a problem is detected.
- In Multi-AZ, instance can be manually promoted to a standalone database instance.
- In Read Replica, instance can be manually promoted to a standalone database instance.
In RDS when you deploy in single AZ, what is the effect on I/O operation when a database snapshot or backup is being taken?
- I/O may be briefly suspended while the backup process initializes (typically under a few seconds) and you may experience a brief period of elevated latency.
- No effect on I/O
- There is no I/O suspension, since the backup is taken from the standby.
- None of the above
- I/O may be briefly suspended while the backup process initializes (typically under a few seconds) and you may experience a brief period of elevated latency.
- No effect on I/O
- There is no I/O suspension, since the backup is taken from the standby.
- None of the above
Your company has SaaS product which provides different kind of reports to various subscribed customers. The reports ranges from adhoc, daily and monthly on various metrics. This is resulting in very high read traffic to underlying Amazon RDS MySQL instance. What can you do to improve the performance without affecting the user experience?
- Ensure that underlying RDS MySQL instance is Multi-AZ enabled.
- Create a read replica for underlying RDS MySQL.
- Change the RDS instance from MySQL to PostgreSQL.
- Analyze and improve the performance of read queries.
- Ensure that underlying RDS MySQL instance is Multi-AZ enabled.
- Create a read replica for underlying RDS MySQL.
- Change the RDS instance from MySQL to PostgreSQL.
- Analyze and improve the performance of read queries.
You are sunsetting an application along with its backend RDS. You had enabled automated backups for RDS instance during the life of application. What step you should take before deleting the instance so that in future you can re-create the RDS instance again?
- No need to do anything, automated backup are retained even after deleting the DB instance.
- Create a final user created DB snapshot upon deletion.
- No need to do anything, RDS automatically creates a final DB snapshot when deleting the DB instance is initiated.
- There is no way to recreate a RDS instance after it is deleted.
- No need to do anything, automated backup are retained even after deleting the DB instance.
- Create a final user created DB snapshot upon deletion.
- No need to do anything, RDS automatically creates a final DB snapshot when deleting the DB instance is initiated.
- There is no way to recreate a RDS instance after it is deleted.
Your company is launching a new SaaS application for mortgage industry. Which of the following are two options for session management in AWS?
- Sticky Sessions with Local Session Caching including a client-side cookies or via configurable duration parameters that can be set at the load balancer which routes requests to the web servers.
- Distributed Session Management using ElastiCache, Redshift, RDS
- Distributed Session Management using ElastiCache, DynamoDB, RDS
- Distributed Session Management using ElastiCache, S3, RDS
- Sticky Sessions with Local Session Caching including a client-side cookies or via configurable duration parameters that can be set at the load balancer which routes requests to the web servers.
- Distributed Session Management using ElastiCache, Redshift, RDS
- Distributed Session Management using ElastiCache, DynamoDB, RDS
- Distributed Session Management using ElastiCache, S3, RDS
What is a DB subnet group?
- A collection of subnets that you may want to designate for your RDS DB Instances in a VPC.
- When creating a DB Instance in VPC, you will need to select a DB Subnet Group.
- When creating a DB Instance in VPC, you don’t need to select a DB Subnet Group.
- Each DB Subnet Group should have at least one subnet for every Availability Zone in a given Region.
- A collection of subnets that you may want to designate for your RDS DB Instances in a VPC.
- When creating a DB Instance in VPC, you will need to select a DB Subnet Group.
- When creating a DB Instance in VPC, you don’t need to select a DB Subnet Group.
- Each DB Subnet Group should have at least one subnet for every Availability Zone in a given Region.
Which of the following statements are true regarding Multi-AZ and Read Replicas? Choose 2.
- You cannot create a read replica with a Multi-AZ DB instance deployment as its source.
- You can create a read replica with a Multi-AZ DB instance deployment as its source.
- You can configure read replicas themselves as Multi-AZ
- You cannot configure read replicas themselves as Multi-AZ
- You cannot create a read replica with a Multi-AZ DB instance deployment as its source.
- You can create a read replica with a Multi-AZ DB instance deployment as its source.
- You can configure read replicas themselves as Multi-AZ
- You cannot configure read replicas themselves as Multi-AZ
If read replica(s) uses a Multi-AZ DB instance deployment as a source, what happens if Multi-AZ failover occurs?
- You cannot create a read replica with a Multi-AZ DB instance deployment as its source.
- Any associated and available read replicas will automatically resume replication once failover has completed.
- You have to manually map the read replicas to newly promoted primary to resume replication.
- You have to delete the old read replicas and new read replicas will be created by RDS after a new primary is promoted.
- You cannot create a read replica with a Multi-AZ DB instance deployment as its source.
- Any associated and available read replicas will automatically resume replication once failover has completed.
- You have to manually map the read replicas to newly promoted primary to resume replication.
- You have to delete the old read replicas and new read replicas will be created by RDS after a new primary is promoted.
What are DB Parameter groups? Choose 2.
- A database parameter group (DB Parameter Group) acts as a “container” for engine configuration values that can be applied to one or more DB Instances.
- You cannot create a new DB parameter group with custom configuration engine values.
- RDS provides a default parameter group optimized for DB instance.
- It is mandatory to specify a DB parameter group when creating a DB instance.
- A database parameter group (DB Parameter Group) acts as a “container” for engine configuration values that can be applied to one or more DB Instances.
- You cannot create a new DB parameter group with custom configuration engine values.
- RDS provides a default parameter group optimized for DB instance.
- It is mandatory to specify a DB parameter group when creating a DB instance.
What are the metrics provided by Amazon RDS that you can use to determine how your DB instance is performing? Choose 4
- IOPS
- Latency
- Network Bandwidth
- Throughput
- Queue Depth
- IOPS
- Latency
- Network Bandwidth
- Throughput
- Queue Depth
Which of the following factor will not have negative affect on DB Instance storage performance?
- Multi-AZ standby creation.
- Read replica creation.
- Changing storage types.
- EBS-optimized instances and instances with 10-gigabit network connectivity.
- Multi-AZ standby creation.
- Read replica creation.
- Changing storage types.
- EBS-optimized instances and instances with 10-gigabit network connectivity.
You have web application architecture with web servers running on EC2 instances in auto scaling group and using RDS MySQL database. Due to sensitive nature of application you have to encrypt the in-transit data between web server and RDS database. How can you do it?
- Download Amazon RDS root CA certificate to your web server and use Secure Socket Layer (SSL) or Transport Layer Security (TLS) from your application to encrypt a connection to DB instance.
- All the connection between EC2 instances and RDS databases are by default encrypted.
- Force all connections to your DB instance to use SSL by setting the rds.force_ssl parameter to 1 (on)
- Add the SSL option to the option group associated with the DB instance.
- Download Amazon RDS root CA certificate to your web server and use Secure Socket Layer (SSL) or Transport Layer Security (TLS) from your application to encrypt a connection to DB instance.
- All the connection between EC2 instances and RDS databases are by default encrypted.
- Force all connections to your DB instance to use SSL by setting the rds.force_ssl parameter to 1 (on)
- Add the SSL option to the option group associated with the DB instance.
Because of a new regulatory compliance requirement you have to encrypt all your encrypted existing application RDS DB instances. You know that in AWS RDS DB instance you can only enable encryption for an Amazon RDS DB instance when you create it, not after the DB instance is created. What steps you should take to meet the compliance requirements? Choose 2.
- Step1: You create a new DB instance with encryption enabled
- Step 2: Copy data from the old DB instance to new encrypted DB instance
- Step1: You can create a snapshot of your DB instance, and then create an encrypted copy of that snapshot.
- Step2: You can then restore a DB instance from the encrypted snapshot, and thus you have an encrypted copy of your original DB instance.
- Step1: You create a new DB instance with encryption enabled
- Step 2: Copy data from the old DB instance to new encrypted DB instance
- Step1: You can create a snapshot of your DB instance, and then create an encrypted copy of that snapshot.
- Step2: You can then restore a DB instance from the encrypted snapshot, and thus you have an encrypted copy of your original DB instance.