You run a clustered NoSQL database on AWS EC2 using AWS EBS. You need to reduce latency for database response times. Performance is the most important concern, not availability. You did not perform the initial setup, someone without much AWS knowledge did, so you are not sure if they configured everything optimally. Which of the following is NOT likely to be an issue contributing to increased latency?

• A.The EC2 instances are not EBS Optimized.
• B.The database and requesting system are both in the wrong Availability Zone.
• C.The EBS Volumes are not using PIOPS.
• D.The database is not running in a placement group.

Comment: *

Name: *

Email: *

Verification: *

A production account has a requirement that any Amazon EC2 instance that has been logged into manually must be terminated within 24 hours. All applications in the production account are using Auto Scaling groups with Amazon CloudWatch Logs agent configured.
How can this process be automated?

• A.Create a CloudWatch Logs subscription to an AWS Step Functions application. Configure the function to add a tag to the EC2 instance that produced the login event and mark the instance to be decommissioned. Then create a CloudWatch Events rule to trigger a second AWS Lambda function once a day that will terminate all instances with this tag.
• B.Create a CloudWatch alarm that will trigger on the login event. Send the notification to an Amazon SNS topic that the Operations team is subscribed to, and have them terminate the EC2 instance within 24 hours.
• C.Create a CloudWatch Logs subscription in an AWS Lambda function. Configure the function to add a tag to the EC2 instance that produced the login event and mark the instance to be decommissioned.
  Create a CloudWatch Events rule to trigger a daily Lambda function that terminates all instances with this tag.
• D.Create a CloudWatch alarm that will trigger on the login event. Configure the alarm to send to an Amazon SQS queue. Use a group of worker instances to process messages from the queue, which then schedules the Amazon CloudWatch Events rule to trigger.

Comment: *

Name: *

Email: *

Verification: *

You have just recently deployed an application on EC2 instances behind an ELB. After a couple of weeks, customers are complaining on receiving errors from the application. You want to diagnose the errors and are trying to get errors from the ELB access logs. But the ELB access logs are empty. What is the reason for this.

• A.You do not have the appropriate permissions to access the logs
• B.You do not have your CloudWatch metrics correctly configured
• C.ELB Access logs are only available for a maximum of one week.
• D.Access logging is an optional feature of Elastic Load Balancing that is disabled by default

Comment: *

Name: *

Email: *

Verification: *

You need to perform ad-hoc analysis on log data, including searching quickly for specific error codes and reference numbers. Which should you evaluate first?

• A.AWS Elasticsearch Service
• B.AWSRedShift
• C.AWSEMR
• D.AWSDynamoDB

Comment: *

Name: *

Email: *

Verification: *

You have an ASP.NET web application running in Amazon Elastic Beanstalk.
Your next version of the application requires a third-party Windows Installer package to be installed on the instance on first boot and before the application launches.
Which options are possible? Choose 2 answers

• A.In the source bundle's .ebextensions folder, create a file with a .config extension.
  In the file, under the "packages" section and "msi" package manager, include the package's URL.
• B.Launch a new Amazon EC2 instance from the AMI used by the environment.
  Log into the instance, install the package and run sysprep. Create a new AMI.
  Configure the environment to use the new AMI.
• C.In the application's Global.asax file, run msiexec.exe to install the package using Process.Start() in the Application Start event handler.
• D.In the environment's configuration, edit the instances configuration and add the package's URL to the "Packages" section.
• E.In the source bundle's .ebextensions folder, create a "Packages" folder.
  Place the package in the folder.

Comment: *

Name: *

Email: *

Verification: *