Question : Restarting an instance in AWS VPC, retains the same primary private IP address ? 1. Yes, It keeps the same primary private IP address 2. No, It does not keep the same primary private IP address 3. Access Mostly Uused Products by 50000+ Subscribers 4. None of the above is correct
For instances launched in a VPC, a private IP address remains associated with the network interface when the instance is stopped and restarted, and is released when the instance is terminated. But For instances launched in EC2-Classic, a private IP address is associated with the instance until it is stopped or terminated.
Question : Which one of the following you create, will automatically a set of DHCP options is automatically added and associated with it
Explaination : When you create a VPC, we automatically create a set of DHCP options and associate them with the VPC. This set includes only a single option: domain-name-servers=AmazonProvidedDNS. This is an Amazon DNS server, and this option enables DNS for instances that need to communicate over the VPCs Internet gateway. The string AmazonProvidedDNS maps to a DNS server running on a reserved IP address at the base of the VPC network range "plus two". For example, the DNS Server on a 10.0.0.0/16 network is located at 10.0.0.2.
Question : For the CloudFormation once you have been created the resources, which one of the following you can use to identify resources outside of AWS CloudFormation templates, 1. Template 2. Stack ID 3. Access Mostly Uused Products by 50000+ Subscribers 4. Logical IDs
Correct Answer : Get Lastest Questions and Answer : In the Resources sections of a template, you declare the AWS resources that you want AWS CloudFormation to manage, such as an Amazon EC2 instance or an Amazon S3 bucket. All templates must declare a Resources section with at least one resource. You must declare each resource separately; however, you can specify multiple resources of the same type.
Each resource declaration includes three parts:
A logical name that is unique within the template
A resource type
Properties for that resource
You use the logical name to reference the resource in other parts of the template. For example, if you want to map an Amazon Elastic Block Store to an Amazon EC2 instance, you reference the logical IDs of both the block stores and the instance to specify the mapping. Logical names must be alphanumeric (A-Za-z0-9). For a list of all the resource types.
In addition to the logical ID, certain resources also have a physical ID, which is the actual assigned name for that resource, such as an Amazon EC2 instance ID or an Amazon S3 bucket name. You use the physical IDs to identify resources outside of AWS CloudFormation templates, but only after the resources have been created. For example, you might give an Amazon EC2 instance resource a logical ID of MyEC2Instance; but when AWS CloudFormation creates the instance, AWS CloudFormation automatically generates and assigns a physical ID (such as i-28f9ba55) to the instance. You can use this physical ID to identify the instance and view its properties (such as the DNS name) by using the Amazon EC2 console. For resources that support custom names, you can assign your own names (physical IDs) to help you quickly identify resources. For example, you can name an Amazon S3 bucket that stores logs as MyPerformanceLogs
1. No, you can only create the S3 bucket and the IAM user. 2. Yes, all these resources can be created using a CloudFormation template 3. Access Mostly Uused Products by 50000+ Subscribers 4. S3 is not supported by CloudFormation.
1. The desired capacity will not get updated as scaling is frozen 2. The desired capacity will get updated, but the scaling activity will not happen 3. Access Mostly Uused Products by 50000+ Subscribers 4. The scaling activity will happen as this is manual scaling