Question : A user is creating a Cloudformation stack. Which of the below mentioned limitations does not hold true for Cloudformation?
1. One account by default is limited to 100 templates 2. The user can use 60 parameters and 60 outputs in a single template 3. Access Mostly Uused Products by 50000+ Subscribers 4. One account by default is limited to 20 stacks
Exp: AWS Cloudformation is an application management tool which provides application modelling, deployment, configuration, management and related activities. The limitations given below apply to the Cloudformation template and stack. There are no limits to the number of templates but each AWS CloudFormation account is limited to a maximum of 20 stacks by default. The Template, Parameter, Output, and Resource description fields are limited to 4096 characters. The user can include up to 60 parameters and 60 outputs in a template.
Question : A user has two EC instances running in two separate regions. The user is running an internal memory management tool, which captures the data and sends it to CloudWatch in US East, using a CLI with the same namespace and metric. Which of the below mentioned options is true with respect to the above statement? 1. The setup will not work as CloudWatch cannot receive data across regions 2. CloudWatch will receive and aggregate the data based on the namespace and metric 3. Access Mostly Uused Products by 50000+ Subscribers 4. CloudWatch will take the data of the server, which sends the data first
Explanation: Amazon CloudWatch does not differentiate the source of a metric when receiving custom data. If the user is publishing a metric with the same namespace and dimensions from different sources, CloudWatch will treat them as a single metric. If the data is coming with the same timezone within a minute, CloudWatch will aggregate the data. It treats these as a single metric, allowing the user to get the statistics, such as minimum, maximum, average, and the sum of all across all servers.
Question : An organization has created a Queue named "modularqueue" with SQS. The organization is not performing any operations such as SendMessage, ReceiveMessage, DeleteMessage, GetQueueAttributes, SetQueueAttributes, AddPermission, and RemovePermission on the queue. What can happen in this scenario?
1. AWS SQS sends notification after 15 days for inactivity on queue 2. AWS SQS can delete queue after 30 days without notification 3. Access Mostly Uused Products by 50000+ Subscribers 4. AWS SQS notifies the user after 2 weeks and deletes the queue after 3 weeks.
Explanation: Amazon SQS can delete a queue without notification if one of the following actions hasn't been performed on it for 30 consecutive days: SendMessage, ReceiveMessage, DeleteMessage, GetQueueAttributes, SetQueueAttributes, AddPermission, and RemovePermission.
1. It can connect to the AWS services, such as S3 and RDS by default 2. It will have all the inbound traffic by default 3. It will have all the outbound traffic by default 4. It will by default allow traffic to the internet gateway
1. Perform a health check until cool down before declaring that the instance has failed 2. Terminate the instance and launch a new instance 3. Notify the user using SNS for the failed state 4. Notify ELB to stop sending traffic to the impaired instance
1. It is not possible that the stack creation will wait until one service is created and launched 2. The user can use the HoldCondition resource to wait for the creation of the other dependent resources 3. The user can use the DependentCondition resource to hold the creation of the other dependent resources 4. The user can use the WaitCondition resource to hold the creation of the other dependent resources