Monitor Auto Scaling Groups and optimize resource utilization.

Answer simple questions about user activity.

Write a cron job to purge the files after one month.

Configure the S3 Lifecycle rules to purge the files after a month.

Create a bucket policy to purge the rules after one month.

Add an S3 Lifecycle rule to archive these files to Glacier after one month.

Support for sticky sessions using application-generated cookies.

A single public subnet without any private subnets.

A single public subnet with two private subnets.

A single private subnet without any public subnets

Launch your instances in a cluster placement group

Upload the data to S3 using your public internet connection.

Order a Snowcone device to transmit the data.

Use a Snowball device to transmit the data.

Use S3 to store the messages being sent between the EC2 instances.

Use SQS FIFO to decouple the applications.

Use SQS Standard. Include a unique ordering ID in each message, and have the backend application use this to deduplicate messages

Upsize your EC2 instances to reduce the message load on the backend servers.

Deploy an SFTP client on a local server and transfer data to Amazon S3 using AWS Transfer for SFTP

Deploy an AWS Storage Gateway volume gateway configured in cached volume mode.

Deploy an AWS DataSync agent on a local server and configure an S3 bucket as the destination.

Deploy an AWS Storage Gateway volume gateway configured in stored volume mode.

Make sure the instance has a private IP address.

A virtual private gateway needs to be configured.

Add a route to the route table, from the subnet containing the instance, to the Internet Gateway.

Place CloudFront in front of the Database

Update the AMI in the old region, as AMIs are universal.

Create a mapping in the template. Define the unique AMI value per region.

Create a Parameter section in the template. Whenever the template is run, fill in the correct AMI ID.

Create a condition in the template to automatically select the correct AMI ID.

Use an SQS queue with the Auto Scaling group to capture all requests.

Use larger instances in the Auto Scaling group.

Use a Network Load Balancer instead for faster throughput.

You can add or remove rules from the default network ACL.

You can only edit the default NACL if it is the only NACL in the VPC.

DB instance based on each minute a process is connected.

The ALB notifies the Auto Scaling group that the instance is down.

The ALB stops sending traffic to the instance.

The CNAME is switched from the primary db instance to the secondary.

The Elastic IP address for the primary database is moved to the secondary database.

Route 53 points the CNAME to the secondary database instance.

A Lambda function kicks off a CloudFormation template to deploy a backup database.

No such service, but there are third-party tools

Simply create the needed versions. Launch configurations already have versioning.

Create the launch configurations in CloudFormation and version the templates accordingly.

Store the launch configurations in S3 and turn on versioning.

Modify the application to store the data on instance store volumes. Reattach the volumes while restarting them. 

Snapshot the instances before stopping them. Restore the snapshot after restarting the instances.

Run the applications on instances enabled for hibernation. Hibernate the instances before the shutdown

Note the Availability Zone for each instance before stopping it. Restart the instances in the same Availability Zones after the shutdown.

Attach ENI to an instance when it's running

Attach ENI when the instance is being launched.

Attach ENI before the public IP address is assigned.

Only public subnets can use the default NACL.

Each subnet in your VPC must be associated with a network ACL. If you don't explicitly associate a subnet with a network ACL, the subnet is automatically associated with the default network ACL.

The default NACL will always be associated with each subnet.

You have to delete the default NACL before creating a custom NACL to associate with a subnet.

The EC2 instance has failed the load balancer health check.

You are load testing at a moderate traffic level and not all instances are needed.

The EC2 instance has failed EC2 status checks.

The instance has not been registered with CloudWatch.

You can configure a standby replica in a different Availability Zone and send traffic synchronously or asynchronously depending on your cost considerations.

Amazon RDS automatically provisions and maintains a synchronous standby replica in a different Region.

Amazon RDS automatically provisions and maintains a synchronous standby replica in a different Availability Zone.

Amazon RDS automatically provisions and maintains an asynchronous standby replica in a different Availability Zone.

Attach the ENI before the public IP address is assigned.

Attach the ENI to an instance when it's running

Attach the ENI when the instance is being launched.

Attach the ENI to an instance when it is stopped.

You can assign up to five security groups to the instance.

You can assign two security groups to an instance.

You can only assign one security group to an instance.

Instances in private subnets cannot have multiple security groups.

There is no route in the route table to the internet gateway (or it has been deleted).

Each instance needs its own security group.

All IPv6, private IP, and elastic IP address.

Ensure that your network access control lists and security group rules allow the relevant traffic to flow to and from your instance.

Add a route to your subnet's route table that directs internet-bound traffic to the internet gateway.

A route in the route table to the DynamoDB table.

Create an IAM policy that you attach to the EC2 instance to give temporary security credentials to applications running on the instance.

Create an IAM role that you attach to the EC2 instance to give temporary security credentials to applications running on the instance.

Create an IAM user, grant the user permissions, and pass the user credentials to the application.

Embed the appropriate credentials to access AWS services in the application.

The volume can only accommodate writes while a snapshot is in progress.

The volume can only accommodate reads while a snapshot is in progress.

The volume cannot be used while a snapshot is in progress.

The volume can be used normally while the snapshot is in progress.

Security groups act at the subnet level, not the instance level.

Security groups act at the instance level, not the subnet level.

Security groups act at the VPC level, not the instance level.

Configure Amazon GuardDuty to prevent these attacks.

Immediately block the offending IP address on the NACL.

Using the AWS WAF service, set up rules which block SQL injection, and cross-site scripting attacks. Associate the rules to the ALB.

Use Amazon Inspector to detect these attacks and manually block the IP addresses from which these attacks come.

You will need a Classic Load Balancer to meet this requirement.

You will need an Application Load Balancer to meet this requirement.

All the AWS load balancers meet the requirement and perform the same.

You will select a Network Load Balancer to meet this requirement.

Increase the maximum message retention period for the queue

Increase the maximum receives for the redrive policy for the queue.

 Increase the default visibility timeout for the queue.

Increase the receive message wait time for the queue.

You can't delete this group, nor can you change the group's rules.

You can delete this group, however, you can't change the group's rules.

You can delete this group or you can change the group's rules.

You can't delete this group, however, you can change the group's rules.

Create a new policy which will grant permissions to the bucket. Create a group and attach the policy to that group. Add the users to this group.

Create a new policy which will grant permissions to the bucket. Create a role and attach the policy to that role. Add the users to this role.

Create a new role which will grant permissions to the bucket. Create a group and attach the role to that group. Add the users to this group.

Create a new bucket policy granting the appropriate permissions and attach it to the bucket.

Practice Exam

1 of 66 Score: 0