A development team is using AWS Elastic Beanstalk to deploy a two-tier application that consists of a load-balanced web tier and an Amazon RDS database tier in production. The team would like to separate the RDS instance from the Elastic Beanstalk.
How can this be accomplished?

• A.Use the Elastic Beanstalk CLI to disassociate the database.
• B.Use the AWS CLI to disassociate the database.
• C.Change the deployment policy to disassociate the database.
• D.Recreate a new Elastic Beanstalk environment without Amazon RDS.

Comment: *

Name: *

Email: *

Verification: *

You attempt to store an object in the US-STANDARD region in Amazon S3, and receive a confirmation that it has been successfully stored. You then immediately make another API call and attempt to read this object. S3 tells you that the object does not exist What could explain this behavior?

• A.US-STANDARD imposes a 1 second delay before new objects are readable.
• B.Objects in Amazon S3 do not become visible until they are replicated to a second region.
• C.You exceeded the bucket object limit, and once this limit is raised the object will be visible.
• D.US-STANDARD uses eventual consistency and it can take time for an object to be readable in a bucket

Comment: *

Name: *

Email: *

Verification: *

A company has three different environments: Development, QA, and Production. The company wants to deploy its code first in the Development environment, then QA, and then Production.
Which AWS service can be used to meet this requirement?

• A.Use AWS CodeCommit to create multiple repositories to deploy the application.
• B.Use AWS CodeBuild to create, configure, and deploy multiple build application projects.
• C.Use AWS Data Pipeline to create multiple data pipeline provisions to deploy the application.
• D.Use AWS CodeDeploy to create multiple deployment groups.

Comment: *

Name: *

Email: *

Verification: *

A Developer created a Lambda function for a web application backend. When testing the Lambda function from the AWS Lambda console, the Developer can see that the function is being executed, but there is no log data being generated in Amazon CloudWatch Logs, even after several minutes.
What could cause this situation?

• A.The Lambda function is missing CloudWatch Logs as a source trigger to send log data.
• B.The Lambda function does not have any explicit log statements for the log data to send it to CloudWatch Logs.
• C.The execution role for the Lambda function is missing permissions to write log data to the CloudWatch Logs.
• D.The Lambda function is missing a target CloudWatch Log group.

Comment: *

Name: *

Email: *

Verification: *

A developer is trying to monitor an application's status by running a cron job that returns 1 if the service is up and 0 if the service is down. The developer created code that uses an AWS CLI put-metric-alarm command to publish the custom metrics to Amazon CloudWatch and create an alarm However the developer is unable to create an alarm as the custom metrics do not appear m the CloudWatch console What is causing this issue?

• A.Sending custom metrics using the CLI is not supported
• B.The code is not running on an Amazon EC2 instance
• C.The developer must use a unified CloudWatch agent to publish custom metrics
• D.The developer needs to use the put-metric-data command.

Comment: *

Name: *

Email: *

Verification: *