AWS Certified Solutions Architect - Professional Questions and Answers (Dumps and Practice Questions)
Question : Please map the below RDS types and its features.
1. Magnetic (Standard)
2. General Purpose (SSD)
3. Provisioned IOPS
A. This storage type is excellent for small to medium-sized databases.
B. offers cost-effective storage that is ideal for applications with light or burst I/O requirements.
C. You specify the amount of storage you want allocated, and then specify the amount of dedicated IOPS you want.
1. 1-A, 2-B, 3-C
2. 1-B, 2-A, 3-C
3. 1-A, 2-C, 3-B
4. 1-C, 2-B, 3-A
Correct Answer : Get Lastest Questions and Answer :
Explanation:Amazon RDS provides three storage types: magnetic, General Purpose (SSD), and Provisioned IOPS (input/output operations per second). They differ in performance characteristics
and price, allowing you to tailor your storage performance and cost to the needs of your database. For a complete discussion of the different volume types, see the topic Amazon EBS
Volume Types.
Magnetic (Standard) - Magnetic storage, also called standard storage, offers cost-effective storage that is ideal for applications with light or burst I/O requirements. These
volumes deliver approximately 100 IOPS on average, with burst capability of up to hundreds of IOPS, and they can range in size from 5 GB to 3 TB, depending on the DB instance
engine that you chose. Magnetic storage is not reserved for a single DB instance, so performance can vary greatly depending on the demands placed on shared resources by other
customers.
General Purpose (SSD) - General Purpose, SSD-backed storage, also called gp2, can provide faster access than disk-based storage. This storage type can deliver single-digit
millisecond latencies, with a base performance of 3 IOPS/GB and the ability to burst to 3,000 IOPS for extended periods of time. In certain cases, based on your instance and
storage configuration, you may get more than 3000 IOPS. General Purpose (SSD) volumes can range in size from 5 GB to 3 TB. This storage type is excellent for small to
medium-sized databases.
Provisioned IOPS - Provisioned IOPS storage is designed to meet the needs of I/O-intensive workloads, particularly database workloads, that are sensitive to storage performance
and consistency in random access I/O throughput. Provisioned IOPS volumes can range in size from 100 GB to 3 TB for MySQL, PostgreSQL, and Oracle DB engines. SQL Server Express
and Web editions can range in size from 100 GB to 1 TB, while SQL Server Standard and Enterprise editions can range in size from 200 GB to 1 TB. You specify the amount of storage
you want allocated, and then specify the amount of dedicated IOPS you want. These two values form a ratio, and this value maintains the ratio specified for the DB engine you
chose. Amazon RDS delivers within 10 percent of the provisioned IOPS performance 99.9 percent of the time over a given year.
Several factors can affect the performance of Amazon EBS volumes, such as instance configuration, I/O characteristics, and workload demand.
Question : You have created an RDS for you website. Now in which of the following case you will face "first touch penalty"
1. DB instance created from a snapshot
2. a point-in-time restore of database
3. Access Mostly Uused Products by 50000+ Subscribers
4. None of the above
5. All 1,2 and 3
Correct Answer : Get Lastest Questions and Answer :
Explanation:Facts About Amazon RDS Storage
The following points are important facts you should know about Amazon RDS storage:
The current maximum channel bandwidth available is 1000 megabits per second (Mbps) full duplex. In terms of the read and write throughput metrics, this equates to about 105
megabytes per second (MB/s) in each direction. A perfectly balanced workload of 50% reads and 50% writes may attain a maximum combined throughput of 210 MB/s. Note that this is
channel throughput, which includes protocol overhead, so the actual data throughput may be less.
Provisioned IOPS works with an I/O request size of 32 KB. An I/O request smaller than 32 KB is handled as one I/O; for example, 1000 16 KB I/O requests are treated the same as
1000 32 KB requests. I/O requests larger than 32 KB consume more than one I/O request; Provisioned IOPS consumption is a linear function of I/O request size above 32 KB. For
example, a 48 KB I/O request consumes 1.5 I/O requests of storage capacity; a 64 KB I/O request consumes 2 I/O requests, etc. For more information about Provisioned IOPS, see
Amazon RDS Provisioned IOPS Storage to Improve Performance.
Note that I/O size does not affect the IOPS values reported by the metrics, which are based solely on the number of I/Os over time. This means that it is possible to consume all
of the IOPS provisioned with fewer I/Os than specified if the I/O sizes are larger than 32 KB. For example, a system provisioned for 5,000 IOPS can attain a maximum of 2,500
IOPS with 64 KB I/O or 1,250 IOPS with 128 KB IO.
Note that standard storage does not provision I/O capacity, so all I/O sizes are counted as a single I/O.
The first time a DB instance is started and accesses an area of disk for the first time, the process can take longer than all subsequent accesses to the same disk area. This is
known as the "first touch penalty." Once an area of disk has incurred the first touch penalty, that area of disk does not incur the penalty again for the life of the instance,
even if the DB instance is rebooted, restarted, or the DB instance class changes. Note that a DB instance created from a snapshot, a point-in-time restore, or a read replica is a
new instance and does incur this first touch penalty.
Because Amazon RDS manages your DB instance, we reserve overhead space on the instance. While the amount of reserved storage varies by DB instance class and other factors, this
reserved space can be as much as one or two percent of the total storage.
Provisioned IOPS provides a way to reserve I/O capacity by specifying IOPS. Like any other system capacity attribute, maximum throughput under load will be constrained by the
resource that is consumed first. That resource could be IOPS, channel bandwidth, CPU, memory, or database internal resources.
Question : You have two DB instances with GB-months of provisioned database storage, however, only one instance is in active mode. How much backup storage
you will get as a free.
1. 10 GB-months
2. 20 GB-months
3. Access Mostly Uused Products by 50000+ Subscribers
4. Nothing free of cost in case of database storage
Correct Answer : Get Lastest Questions and Answer :
Explanation: When you use Amazon RDS, you pay only for what you use, and there are no minimum or setup fees. You are billed according to the following criteria.
Instance class - Pricing is based on the class (e.g., micro, small, large, xlarge) of the DB instance consumed.
Running time - You are billed by the instance-hour, which is equivalent to a single instance running for an hour. For example, both a single instance running for two hours and
two instances running for one hour consume 2 instance-hours. If a DB instance runs for only part of an hour, you are charged for a full instance-hour.
Storage - The storage capacity that you have provisioned to your DB instance is billed per GB per month. If you scale your provisioned storage capacity within the month, your
bill will be pro-rated.
I/O requests per month - Total number of storage I/O requests that you have made in a billing cycle.
Backup storage - Backup storage is the storage that is associated with automated database backups and any active database snapshots that you have taken. Increasing your backup
retention period or taking additional database snapshots increases the backup storage consumed by your database. Amazon RDS provides backup storage up to 100% of your provisioned
database storage at no additional charge. For example, if you have 10 GB-months of provisioned database storage, we will provide up to 10 GB-months of backup storage at no
additional charge. Most databases require less raw storage for a backup than for the primary dataset, so if you don't keep multiple backups, you will never pay for backup
storage. Backup storage is free only for active DB instances.
Data transfer -Internet data transfer in and out of your DB instance.
In addition to regular RDS pricing, you can purchase reserved DB instances. Reserved DB instances let you make a one-time up-front payment for a DB instance and reserve the DB
instance for a one- or three-year term at significantly lower rates
Related Questions
Question : QuickTechie.com is creating a VPC for their application hosting and has created two private subnets in the same AZ and created one subnet
in a separate zone. QuickTechie.com wants to make a HA system with the internal ELB. Which of the below mentioned statements is true with respect to an internal ELB in this scenario?
1. ELB can support only one subnet in each availability zone.
2. ELB does not allow subnet selection; instead it will automatically select all the available subnets of the VPC.
3. Access Mostly Uused Products by 50000+ Subscribers
4. If the user is creating an internal ELB, he should use only private subnets.
Question : HadoopExam.com has setup a VPC with public and private subnets and does not want everyone to connect to the private VPC instance.
Instead it wants to setup secure access from a single IP. Which of the below mentioned options fits best as a solution?
1. Create an IAM user who will have secure access to the private subnet.
2. Allow only the public subnet to SSH to the private subnet.
3. Access Mostly Uused Products by 50000+ Subscribers
4. Create a NAT instance which allows access only from the selected IP address.
Question : QuickTechie.com is planning to setup a 'warm standby' to AWS for fast recovery of the application in case of DR.
Which of the below mentioned configurations will not fit the 'warm standby' requirement setup?
1. Setup EC2 with the smallest server and ELB which run continuously.
2. Setup the backup data on S3 and transfer data regularly to S3 using the storage gateway.
3. Access Mostly Uused Products by 50000+ Subscribers
4. Mirror the data from in premise data to EC2.
Question : QuickTechie.com is running an application on an EBS backed EC instance for hours a day across days.
The application is a scalable web application which uses RDS for fetching data. Which of the below mentioned options
is a better scalable and cost effective solution for this scenario?
1. Use RDS with heavy utilized Reserved Instances and EC2 with medium utilized Reserved Instances.
2. Use both RDS and EC2 with heavy utilized Reserved Instances.
3. Access Mostly Uused Products by 50000+ Subscribers
4. Use RDS with a medium utilized Reserved Instance and EC2 with low utilized Reserved Instances.
Question : QuickTechie.com has launched two applications: one for polling and one for review on the same AWS Linux EC instance running in the AWS VPC.
And has attached two private IPs (primary and secondary) to the above mentioned instance also wants the instance OS to recognize the secondary IP address.
How can the organization configure this?
1. Use the ec2-net-utility package which updates routing tables, uses DHCP to refresh the secondary IP and adds the network interface.
2. Use the ec2-ip-update package which can configure the network interface as well as update the secondary IP with DHCP.
3. Access Mostly Uused Products by 50000+ Subscribers
4. Use the ec2-ip-utility package which can update the routing tables as well as refresh the secondary IP using DHCP.
Question : QuickTechie.com has setup a web application in the AWS VPC and also running a database on the EC instance and the application server connects to the
DB server only on the internal IP. QuickTechie is looking for HA and DR for the database. Which of the below mentioned options fulfils the QuickTechie's need for a DB backup?
1. Setup the database in the private subnet and keep a hot standby running in the public subnet for immediate failover.
2. Use the AWS storage gateway with VPC to switchover from the primary to secondary DB in separate zones.
3. Access Mostly Uused Products by 50000+ Subscribers
with a different subnet.
4. Setup the database on the instance with an elastic network interface which will have a fixed private IP address and also keep a hot standby running in a separate zone
with a different subnet.