[2021-New] Amazon AWS-Certified-DevOps-Engineer-Professional Dumps With Update Exam Questions (1-10)

AWS-Certified-DevOps-Engineer-Professional Dumps

AWS-Certified-DevOps-Engineer-Professional Exam Questions - Online Test

AWS-Certified-DevOps-Engineer-Professional Premium VCE File

Learn More 100% Pass Guarantee - Dumps Verified - Instant Download
150 Lectures, 20 Hours

Q1. You need to migrate 10 million records in one hour into DynamoDB. All records are 1.5KB in size. The data is evenly distributed across the partition key. How many write capacity units should you provision during this batch load?

A. 6667

B. 4166

C. 5556

D. 2778

Answer: C

Explanation:

You need 2 units to make a 1.5KB write, since you round up. You need 20 million total units to perform this load. You have 3600 seconds to do so. DMde and round up for 5556.

Reference: http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/HowItWorks.ProvisionedThroughp ut.htmI

Q2. For AWS CloudFormation, which is true?

A. Custom resources using SNS have a default timeout of 3 minutes.

B. Custom resources using SNS do not need a <code>ServiceToken</code> property.

C. Custom resources using Lambda and <code>Code.ZipFiIe</code> allow inline nodejs resource composition.

D. Custom resources using Lambda do not need a <code>ServiceToken</code>property

Answer: C

Explanation:

Code is a property of the AWS::Lambda::Function resource that enables to you specify the source code of an AWS Lambda (Lambda) function. You can point to a file in an Amazon Simple Storage Service (Amazon S3) bucket or specify your source code as inline text (for nodejs runtime environments only). Reference:

http://docs.aws.amazon.com/AWSCIoudFormation/latest/UserGuide/template-custom-resources.html

Q3. What is the scope of an EBS volume?

A. VPC

B. Region

C. Placement Group

D. Availability Zone

Answer: D

Explanation:

An Amazon EBS volume is tied to its Availability Zone and can be attached only to instances in the same Availability Zone.

Reference: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/resources.htmI

Q4. What method should I use to author automation if I want to wait for a CIoudFormation stack to finish completing in a script?

A. Event subscription using SQS.

B. Event subscription using SNS.

C. Poll using <code>ListStacks</code> / <code>Iist-stacks</code>.

D. Poll using <code>GetStackStatus</code> / <code>get-stack-status</code>.

Answer: C

Explanation:

Event driven systems are good for IFTTT logic, but only polling will make a script wait to complete. ListStacks / list-stacks is a real method, GetStackStatus / get-stack-status is not.

Reference: http://docs.aws.amazon.com/cli/latest/reference/cloudformation/Iist-stacks.html

Q5. What does it mean if you have zero IOPS and a non-empty I/O queue for all EBS volumes attached to a running EC2 instance?

A. The I/O queue is buffer flushing.

B. Your EBS disk head(s) is/are seeking magnetic stripes.

C. The EBS volume is unavailable.

D. You need to re-mount the EBS volume in the OS.

Answer: C

Explanation:

This is the definition of Unavailable from the EC2 and EBS SLA.

"UnavaiIabIe" and "Unavai|abi|ity" mean... For Amazon EBS, when all of your attached volumes perform zero read write IO, with pending IO in the queue.

Reference: https://aws.amazon.com/ec2/s|a/

Q6. For AWS CIoudFormation, which stack state refuses UpdateStack calls?

A. <code>UPDATE_ROLLBACK_FAILED</code>

B. <code>UPDATE_ROLLBACK_COMPLETE</code>

C. <code>UPDATE_CONIPLETE</code>

D. <code>CREATE_COMPLETE</code>

Answer: A

Explanation:

When a stack is in the UPDATE_ROLLBACK_FA|LED state, you can continue rolling it back to return it to a working state (to UPDATE_ROLLBACK_COMPLETE). You cannot update a stack that is in the UPDATE_ROLLBACK_FA|LED state. However, if you can continue to roll it back, you can return the stack to its original settings and try to update it again.

Reference:

http://docs.aws.amazon.com/AWSCIoudFormation/latest/UserGuide/using-cfn-updating-stacks-continueu pdateroIIback.htmI

Q7. You need to create an audit log of all changes to customer banking data. You use DynamoDB to store this customer banking data. |t's important not to lose any information due to server failures. What is an elegant way to accomplish this?

A. Use a DynamoDB StreamSpecification and stream all changes to AWS Lambda. Log the changes to

AWS CIoudWatch Logs, removing sensitive information before logging.

B. Before writing to DynamoDB, do a pre-write acknoledgment to disk on the application sewer, removing sensitive information before logging. Periodically rotate these log files into S3.

C. Use a DynamoDB StreamSpecification and periodically flush to an EC2 instance store, removing sensitive information before putting the objects. Periodically flush these batches to S3.

D. Before writing to DynamoDB, do a pre-write acknoledgment to disk on the application sewer, removing sensitive information before logging. Periodically pipe these files into CloudWatch Logs.

Answer: A

Explanation:

All suggested periodic options are sensitive to sewer failure during or between periodic flushes. Streaming to Lambda and then logging to CIoudWatch Logs will make the system resilient to instance and Availability Zone failures.

Reference: http://docs.aws.amazon.com/Iambda/latest/dg/with-ddb.html

Q8. Your serverless architecture using AWS API Gateway, AWS Lambda, and AWS DynamoDB experienced

a large increase in traffic to a sustained 400 requests per second, and dramatically increased in failure rates. Your requests, during normal operation, last 500 milliseconds on average. Your DynamoDB table did not exceed 50% of provisioned throughput, and Table primary keys are designed correctly. What is the most likely issue?

A. Your API Gateway deployment is throttling your requests.

B. Your AWS API Gateway Deployment is bottlenecking on request (de)seriaIization.

C. You did not request a limit increase on concurrent Lambda function executions.

D. You used Consistent Read requests on DynamoDB and are experiencing semaphore lock.

Answer: C

Explanation:

AWS API Gateway by default throttles at 500 requests per second steady-state, and 1000 requests per second at spike. Lambda, by default, throttles at 100 concurrent requests for safety. At 500 milliseconds (half of a second) per request, you can expect to support 200 requests per second at 100 concurrency. This is less than the 400 requests per second your system now requires. Make a limit increase request via the AWS Support Console.

AWS Lambda: Concurrent requests safety throttle per account -> 100

Reference: http://docs.aws.amazon.com/generaI/latest/gr/aws_service_Iimits.htm|#|imits_|ambda

Q9. Which status represents a failure state in AWS CIoudFormation?

A. <code>UPDATE_COMPLETE_CLEANUP_IN_PROGRESS</code>

B. <code>DELETE_COMPLETE_WITH_ARTIFACTS</code>

C. <code>ROLLBACK_IN_PROGRESS</code>

D. <code>ROLLBACK_FAILED</code>

Answer: C

Explanation:

ROLLBACK_IN_PROGRESS means an UpdateStack operation failed and the stack is in the process of trying to return to the valid, pre-update state. UPDATE_COMPLETE_CLEANUP_IN_PROGRESS means an update was successful, and CIoudFormation is deleting any replaced, no longer used resources. ROLLBACK_FA|LED is not a CloudFormation state (but UPDATE_ROLLBACK_FAILED is). DELETE_COMPLETE_W|TH_ART|FACTS does not exist at all.

Reference:

http://docs.aws.amazon.com/AWSCIoudFormation/latest/UserGuide/using-cfn-updating-stacks.html

Q10. 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.

Answer: B

Explanation:

For the highest possible performance, all instances in a clustered database like this one should be in a single Availability Zone in a placement group, using EBS optimized instances, and using PIOPS SSD EBS Volumes. The particular Availability Zone the system is running in should not be important, as long as it is the same as the requesting resources.

Reference: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/placement-groups.html