Question : You havesetup Multi AZ with the MS SQL RDS instance. Which of the below mentioned functionalities can be achieved by you? 1. High availability 2. Scalability 3. Access Mostly Uused Products by 50000+ Subscribers 4. Disaster recovery
Explanation: When you create or modify your DB Instance to run as a Multi-AZ deployment, Amazon RDS automatically provisions and maintains a synchronous "standby" replica in a different Availability Zone. Updates to your DB Instance are synchronously replicated across Availability Zones to the standby in order to keep both in sync and protect your latest database updates against DB Instance failure. During certain types of planned maintenance, or in the unlikely event of DB Instance failure or Availability Zone failure, Amazon RDS will automatically failover to the standby so that you can resume database writes and reads as soon as the standby is promoted. Since the name record for your DB Instance remains the same, you application can resume database operation without the need for manual administrative intervention. With Multi-AZ deployments, replication is transparent: you do not interact directly with the standby, and it cannot be used to serve read traffic. If you are using Amazon RDS for MySQL and are looking to scale read traffic beyond the capacity constraints of a single DB Instance, you can deploy one or more Read Replicas. The Multi AZ feature allows the user to achieve High Availability. MS SQL does not support Multi AZ.
Question : You have created an RDS instance with MySQL. Now you are using the HeidiSQL client to connect with the RDS DB. The client is unable to connect to DB from his home machine. What is a possible reason for the failure? 1. You can never connect to RDS from your desktop 2. The security group is not configured to allow a request from the user's IP on port 3306 3. Access Mostly Uused Products by 50000+ Subscribers 4. The user has to open port 22 in the RDS security group to connect with RDS DNS
Explanation: If the user needs to connect to RDS then he has to open port 3306 in the RDS security group for his IP address. Amazon RDS uses DB security groups, VPC security groups, and EC2 security groups. In simple terms, a DB security group controls access to a DB instance that is not in a VPC, a VPC security group controls access to a DB instance inside a VPC, and an Amazon EC2 security group controls access to an EC2 instance and can be used with a DB instance. For more information about security groups, see Amazon RDS Security Groups. DB Parameter Groups
You manage the configuration of a DB engine by using a DB parameter group. A DB parameter group contains engine configuration values that can be applied to one or more DB instances of the same instance type. Amazon RDS applies a default DB parameter group if you dont specify a DB parameter group when you create a DB instance. The default group contains defaults for the specific database engine and instance class of the DB instance. DB Option Groups
Some DB engines offer tools that simplify managing your databases and making the best use of your data. Amazon RDS makes such tools available through option groups. Currently, option groups are available for Oracle, Microsoft SQL Server, and MySQL 5.6 DB instances. For more information about individual Oracle options, go to Appendix: Options for Oracle Database Engine. For more information about SQL Server options With regard to RDS, the user can manage the configuration of a DB engine by using a DB parameter group. A DB parameter group contains engine configuration values that can be applied to one or more DB instances of the same instance type.
Question : Being Developer for AWS at QuickTechie.com you are launching an AWS RDS with MySQL. Which of the below mentioned options allows you to configure the INNODB engine parameters? 1. Engine parameters 2. DB parameters 3. Access Mostly Uused Products by 50000+ Subscribers 4. Options group
A security group controls the access to a DB instance. It does so by allowing access to IP address ranges or Amazon EC2 instances that you specify.
Amazon RDS uses DB security groups, VPC security groups, and EC2 security groups. In simple terms, a DB security group controls access to a DB instance that is not in a VPC, a VPC security group controls access to a DB instance inside a VPC, and an Amazon EC2 security group controls access to an EC2 instance and can be used with a DB instance. For more information about security groups, see Amazon RDS Security Groups. DB Parameter Groups
You manage the configuration of a DB engine by using a DB parameter group. A DB parameter group contains engine configuration values that can be applied to one or more DB instances of the same instance type. Amazon RDS applies a default DB parameter group if you dont specify a DB parameter group when you create a DB instance. The default group contains defaults for the specific database engine and instance class of the DB instance. DB Option Groups
Some DB engines offer tools that simplify managing your databases and making the best use of your data. Amazon RDS makes such tools available through option groups. Currently, option groups are available for Oracle, Microsoft SQL Server, and MySQL 5.6 DB instances. For more information about individual Oracle options, go to Appendix: Options for Oracle Database Engine. For more information about SQL Server options With regard to RDS, the user can manage the configuration of a DB engine by using a DB parameter group. A DB parameter group contains engine configuration values that can be applied to one or more DB instances of the same instance type.