Question : You have created a MySQL RDS instance as backend database for www.QuickTechie.com website. Which of the below mentioned options is mandatory to configure while creating an instance? 1. Maintenance window 2. Multi AZ deployment setup 3. Access Mostly Uused Products by 50000+ Subscribers 4. Availability Zone
Correct Answer : Get Lastest Questions and Answer : Explanation: When creating an RDS instance, the user needs to specify whether it is Multi AZ or not. If the user does not provide the value for the zone, the maintenance window or automated backup window, RDS will automatically select the value. Amazon cloud computing resources are housed in highly available data center facilities in different areas of the world (for example, North America, Europe, and Asia). Each data center location is called a region.
Each region contains multiple distinct locations called Availability Zones, or AZs. Each Availability Zone is engineered to be isolated from failures in other Availability Zones, and to provide inexpensive, low-latency network connectivity to other zones in the same region. By launching instances in separate Availability Zones, you can protect your applications from the failure of a single location. If the user is launching RDS with Multi AZ the user cannot provision the Availability Zone. RDS is launched automatically instead It is important to remember that each region is completely independent. Any Amazon RDS activity you initiate (for example, creating database instances or listing available database instances) runs only in your current default region. The default region can be changed in the console, by setting the EC2_REGION environment variable, or it can be overridden by using the --url parameter with the command line interface.
Question : You are launching an AWS RDS instance with MySQL as backend database for www.QuickTechie.com website. Now you wants to enable the Multi AZ feature. Which of the below mentioned parameters will not be allowed to configure by RDS? 1. DB subnet group 2. Availability Zone 3. Access Mostly Uused Products by 50000+ Subscribers 4. Database port
Explanation: Amazon cloud computing resources are housed in highly available data center facilities in different areas of the world (for example, North America, Europe, and Asia). Each data center location is called a region.
Each region contains multiple distinct locations called Availability Zones, or AZs. Each Availability Zone is engineered to be isolated from failures in other Availability Zones, and to provide inexpensive, low-latency network connectivity to other zones in the same region. By launching instances in separate Availability Zones, you can protect your applications from the failure of a single location. If the user is launching RDS with Multi AZ the user cannot provision the Availability Zone. RDS is launched automatically instead It is important to remember that each region is completely independent. Any Amazon RDS activity you initiate (for example, creating database instances or listing available database instances) runs only in your current default region. The default region can be changed in the console, by setting the EC2_REGION environment variable, or it can be overridden by using the --url parameter with the command line interface.
Question : An EC instance has one additional EBS volume attached to it. How can you attach the same volume to another running instance in the same AZ? 1. Detach the volume first and attach to new instance 2. Attach the volume as read only to the second instance 3. Access Mostly Uused Products by 50000+ Subscribers 4. No need to detach. Just select the volume and attach it to the new instance, it will take care of mapping internally
Correct Answer : Get Lastest Questions and Answer : Explanation: If an EBS volume is attached to a running EC2 instance, the user needs to detach the volume from the original instance and then attach it to a new running instance. The user doesn't need to stop / terminate the original instance. You can detach an Amazon EBS volume from an instance explicitly or by terminating the instance. However, if the instance that the volume is attached to is running, you must unmount the volume (from the instance) before you detach it. Failure to do so results in the volume being stuck in the busy state while it is trying to detach, which could possibly damage the file system or the data it contains.
If an EBS volume is the root device of an instance, you must stop the instance before you can detach the volume.
When a volume with an AWS Marketplace product code is detached from an instance, the product code is no longer associated with the instance.
Important
After you detach a volume, you are still charged for volume storage as long as the storage amount exceeds the limit of the Free Usage Tier. You must delete a volume to avoid incurring further charges.
This example unmounts the volume and then explicitly detaches it from the instance. This is useful when you want to terminate an instance or attach a volume to a different instance. To verify that the volume is no longer attached to the instance
Note that you can reattach a volume that you detached (without unmounting it), but it might not get the same mount point and the data on the volume might be out of sync if there were writes to the volume in progress when it was detached.