Question : Considering CloudWatch Alarm state, in above in which period Alarm state will 'ALARM' 1. one through fifth time periods 2. third through fifth time periods 3. two through sixth time periods 4. third through sixth time periods
Correct Answer 2 :
Explanation: In the given figure, the alarm threshold is set to 3 and the minimum breach is 3 periods. That is, the alarm invokes its action only when the threshold is breached for 3 consecutive periods. In the figure, this happens with the third through fifth time periods, and the alarm's state is set to ALARM. At period six, the value dips below the threshold, and the state reverts to OK. Later, during the ninth time period, the threshold is breached again, but not for the necessary three consecutive periods. Consequently, the alarm's state remains OK.
Question : While practicing on HadoopExam As a learner you have launched an EC Windows instance from an instance store backed AMI. Now you wants to convert the AMI to an EBS backed AMI. How can you convert it? 1. Learner has to attach an EBS volume to the instance and unbundle all the AMI bundled data inside the EBS 2. A Windows based instance store backed AMI cannot be converted to an EBS backed AMI 3. It is not possible to convert an instance store backed AMI to an EBS backed AMI 4. Learner has to attach an EBS volume and use the copy command to copy all the ephermal content to the EBS Volume
Correct Answer 2 :
Explanation: Converting your Instance Store-Backed AMI to an Amazon EBS-Backed AMI You can convert an instance store-backed Linux AMI that you own to an Amazon EBS-backed Linux AMI. Important You can't convert an instance store-backed Windows AMI to an Amazon EBS-backed Windows AMI and you cannot convert an AMI that you do not own. Generally when a user has launched an EC2 instance from an instance store backed AMI, it can be converted to an EBS backed AMI provided the user has attached the EBS volume to the instance and unbundles the AMI data to it. However, if the instance is a Windows instance, AWS does not allow this. In this case, since the instance is a Windows instance, the user cannot convert it to an EBS backed AMI.
Question : Ramesh has created a VPC with public and private subnets using the VPC Wizard. The VPC has CIDR 20.0.0.0/16. The private subnet uses CIDR 20.0.0.0/24. Which of the below mentioned entries are required in the main route table to allow the instances in VPC to communicate with each other? 1. Destination : 20.0.0.0/24 and Target : VPC 2. Destination : 20.0.0.0/16 and Target : ALL 3. Destination : 20.0.0.0/0 and Target : ALL 4. Destination : 20.0.0.0/16 and Target : Local
Correct Answer 1 :
Explanation: Connections with Your Local Network and Other VPCs You can optionally set up a connection between your VPC and your corporate or home network. If you have an IP address prefix in your VPC that overlaps with one of your networks' prefixes, any traffic to the network's prefix is dropped. For example, let's say that you have the following: >A VPC with CIDR block 10.0.0.0/16 >A subnet in that VPC with CIDR block 10.0.1.0/24 >Instances running in that subnet with IP addresses 10.0.1.4 and 10.0.1.5 >On-premises host networks using CIDR blocks 10.0.37.0/24 and 10.1.38.0/24
When those instances in the VPC try to talk to hosts in the 10.0.37.0/24 address space, the traffic is dropped because 10.0.37.0/24 is part of the larger prefix assigned to the VPC (10.0.0.0/16). The instances can talk to hosts in the 10.1.38.0/24 space because that block isn't part of 10.0.0.0/16.
You can also create a VPC peering connection between your VPCs, or with a VPC in another AWS account. A VPC peering connection enables you to route traffic between the VPCs using private IP addresses; however, you cannot create a VPC peering connection between VPCs that have overlapping CIDR blocks.
We therefore recommend that you create a VPC with a CIDR range large enough for expected future growth, but not one that overlaps with current or expected future subnets anywhere in your corporate or home network, or that overlaps with current or future VPCs. A user can create a subnet with VPC and launch instances inside that subnet. If the user has created a public private subnet, the instances in the public subnet can receive inbound traffic directly from the Internet, whereas the instances in the private subnet cannot. If these subnets are created with Wizard, AWS will create two route tables and attach to the subnets. The main route table will have the entry "Destination: 20.0.0.0/24 and Target: Local", which allows all instances in the VPC to communicate with each other.