1. Right Answer: A
Explanation: When the user gets an error insufficient capacity pending when launching or starting an EC2 instance, this means that AWS does not currently have sufficient capacity available to process the user request. If the user requests a large number of cases, there would not be enough server capacity to host. The user can try again later, specifying a smaller number of cases or change the availability zone If the launch of a new instance.
2. Right Answer: D
Explanation: mounted. This shows that the file system is created. When the user accesses the volume AWS EBS erase the block storage or instantiate the snapshot. Thus, the volume shows a loss of IOPS. It is recommended that the user needs to pre heat the LBS before using to get a better 10.
3. Right Answer: A
Explanation: Amazon RDS performs maintenance on the instance DB during a maintenance window defined by the user. The system can be offline or experiencing the weakest performance in this window. The only maintenance events that may require RDS DB instance to make online are: Scaling calculation software patching operations. patching software required is automatically scheduled only for patches that are related to safety and sustainability. Such patching occurs infrequently (typically once every few months. And rarely require more than a fraction of the maintenance window.
4. Right Answer: E
Explanation: Last automatic scaling based on a calendar allows the user to scale the application in response to changes in load predictable. To configure the Auto Scaling group-wide according to a schedule, the user needs to create the programmed actions. A planned action indicates Auto Scaling to perform a scaling action at some point in the future.
5. Right Answer: E
Explanation: A volume provisioning lops EBS can vary in size from 10 GB to 1 TB and available to the user box up to 4,000 IOPS per volume. The ratio of IOPS provisioned on the volume size requested must be a maximum of 30; for example, a volume of 3000 IOPS must be at least 100 GB.