Pre-Summer Special Limited Time 70% Discount Offer - Ends in 0d 00h 00m 00s - Coupon code: force70

Amazon Web Services AWS Certified DevOps Engineer - Professional DOP-C02 Question # 21 Topic 3 Discussion

Amazon Web Services AWS Certified DevOps Engineer - Professional DOP-C02 Question # 21 Topic 3 Discussion

DOP-C02 Exam Topic 3 Question 21 Discussion:
Question #: 21
Topic #: 3

A company is migrating an application to Amazon Elastic Container Service (Amazon ECS). The company wants to consolidate log data in Amazon CloudWatch in the us-west-2 Region. No CloudWatch log groups currently exist for Amazon ECS.

The company receives the following error code when an ECS task attempts to launch:

“service my-service-name was unable to place a task because no container instance met all of its requirements.”

The ECS task definition includes the following container log configuration:

" logConfiguration " : {

" logDriver " : " awslogs " ,

" options " : {

" awslogs-create-group " : " true " ,

" awslogs-group " : " awslogs-mytask " ,

" awslogs-region " : " us-west-2 " ,

" awslogs-stream-prefix " : " awslogs-mytask " ,

" mode " : " non-blocking " ,

" max-buffer-size " : " 25m "

}

}

The ECS cluster uses an Amazon EC2 Auto Scaling group to provide capacity for tasks. EC2 instances launch an Amazon ECS-optimized AMI.

Which solution will fix the problem?


A.

Modify the ECS infrastructure IAM role to add the logs:CreateLogStream and logs:PutLogEvents permissions.


B.

Modify the ECS log configuration to use blocking mode.


C.

Modify the ECS container instance IAM role to add the logs:CreateLogStream and logs:PutLogEvents permissions.


D.

Modify the ECS log configuration by setting the awslogs-create-group option to false.


Get Premium DOP-C02 Questions

Contribute your Thoughts:


Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.