AWS Certified Developer - Associate Questions and Answers (Dumps and Practice Questions)

Question : You wants to access RDS from an EC instance using IP addresses. Both RDS and EC are in the same region,
but different AZs. Which of the below mentioned options help configure that the instance is accessed faster?

1. Configure the Private IP of the Instance in RDS security group
2. Configuring the elastic IP of the instance in RDS security group
3. Access Mostly Uused Products by 50000+ Subscribers
4. Security group of EC2 allowed in the RDS security group

Correct Answer : Get Lastest Questions and Answer :

Explanation: A DB security group controls network access to a DB instance that is not inside a VPC. By default, network access is turned off to a DB instance. You can specify rules in a security group that allows access from an IP address range, port, or EC2 security group. Once ingress rules are configured, the same rules apply to all DB instances that are associated with that security group. You can specify up to 20 rules in a security group.

If you are a new customer to Amazon RDS or if you are an existing customer who is using a new region, your DB instance is most likely in a default VPC. You cannot use a DB security group for a DB instance inside a VPC; you must create a VPC security group. For information on creating a VPC security group, see Security Groups for Your VPC. To determine if you have a default VPC, see step 2 in the following procedure. If the user is going to specify an IP range in RDS security group, AWS recommends using the private IP address of the Amazon EC2 instance. This provides a more direct network route from the Amazon EC2 instance to the Amazon RDS DB instance, and does not incur network charges for the data sent outside of the Amazon network.

Question : Being a QuickTechie.com AWS developer you have launched a MySQL RDS.
And now wants to plan for the DR and automate the snapshot. Which of the below mentioned functionality offers this option with RDS?

1. Automated synchronization
2. Snapshot
3. Access Mostly Uused Products by 50000+ Subscribers
4. Automated backup

Correct Answer : Get Lastest Questions and Answer :
Explanation: DB snapshots are user-initiated and enable you to back up your DB instance in a known state as frequently as you wish, and then restore to that specific state at any time. DB snapshots can be created with the Amazon RDS console or the CreateDBSnapshot action in the Amazon RDS API. DB snapshots are kept until you explicitly delete them with the Amazon RDS console or the DeleteDBSnapshot action in the Amazon RDS API. Amazon RDS provides two different methods for backing up and restoring the Amazon DB instances: automated backups and DB snapshots. Automated backups automatically back up the DB instance during a specific, user-definable backup window, and keep the backups for a limited, user-specified period of time. When you create a DB snapshot, you need to identify which DB instance you are going to back up, and then give your DB snapshot a name so you can restore from it later. Note : Creating a DB snapshot creates a backup of your DB instance. Creating this backup on a Single-AZ DB instance results in a brief I/O suspension that typically lasting no more than a few minutes. Multi-AZ DB instances are not affected by this I/O suspension since the backup is taken on the standby.
Restoring From a DB Snapshot

You must create a DB snapshot before you can restore a DB instance from one. When you restore the DB instance, you provide the name of the DB snapshot to restore from, and then provide a name for the new DB instance that is created from the restore. You cannot restore from a DB snapshot to an existing DB instance; a new DB instance is created when you restore.

When you restore a DB instance, only the default DB parameter and security groups are associated with the restored instance. As soon as the restore is complete, you should associate the custom DB parameter or security group you used by the instance you restored from. You must apply these changes explicitly using the RDS console's Modify command, the ModifyDBInstance API, or the rds-modify-db-instance command line tool, once the DB instance is available. We recommend that you retain parameter groups for any DB snapshots you have so that you can associate a restored instance with the correct parameter file.

Note : If you use Oracle GoldenGate, always retain the parameter group with the compatible parameter. If you restore an instance from a DB snapshot, you must modify the restored instance to use the parameter group that has a matching or greater compatible parameter value. This should be done as soon as possible after the restore action, and will require a reboot of the instance.

The option group associated with the DB snapshot is associated with the restored DB instance once it is created. For example, if the DB snapshot you are restoring from uses Oracle Transparent Data Encryption, the restored DB instance will use the same option group, which had the TDE option. When an option group is assigned to a DB instance, it is also linked to the supported platform the DB instance is on, either VPC or EC2-Classic (non-VPC). Furthermore, if a DB instance is in a VPC, the option group associated with the instance is linked to that VPC. This means that you cannot use the option group assigned to a DB instance if you attempt to restore the instance into a different VPC or onto a different platform. If you restore a DB instance into a different VPC or onto a different platform, you must either assign the default option group to the instance, assign an option group that is linked to that VPC or platform, or create a new option group and assign it to the DB instance. Note that with persistent or permanent options, such as Oracle TDE, you must create a new option group that includes the persistent or permanent option when restoring a DB instance into a different VPC.

You can change to a different edition of the DB engine when restoring from a DB snapshot only if the DB snapshot has the required storage allocated for the new edition. For example, to change from SQL Server Web Edition to SQL Server Standard Edition, the DB snapshot must have been created from a SQL Server DB instance that had at least 200 GB of allocated storage, which is the minimum allocated storage for SQL Server Standard edition.

Question : You are creating a new EBS volume from an existing snapshot. The snapshot size shows GB. Can the user create a volume of GB from that snapshot?

1. Yes
2. Provided the original volume has set the change size attribute to true
3. Access Mostly Uused Products by 50000+ Subscribers
4. Provided the snapshot has the modify size attribute set as true

Correct Answer : Get Lastest Questions and Answer :
Explanation: Sometimes, you might need to increase the storage space of an existing EBS volume without losing the data that is on the volume. You can expand the storage space of an EBS volume by migrating your data to a larger volume and then extending the file system on the volume to recognize the newly-available space. After you verify that your new volume is working properly, you can delete the old volume. A user can always create a new EBS volume of a higher size than the original snapshot size. The user cannot create a volume of a lower size. When the new volume is created the size in the instance will be shown as the original size. The user needs to change the size of the device with resize2fs or other OS specific commands.
When you create a DB snapshot, you need to identify which DB instance you are going to back up, and then give your DB snapshot a name so you can restore from it later.

Note :

Creating a DB snapshot creates a backup of your DB instance. Creating this backup on a Single-AZ DB instance results in a brief I/O suspension that typically lasting no more than a few minutes. Multi-AZ DB instances are not affected by this I/O suspension since the backup is taken on the standby.

AWS Certified Developer - Associate Questions and Answers (Dumps and Practice Questions)

Related Questions