Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon DOP-C02 Exam - Topic 4 Question 61 Discussion

Posted by Ilona on Apr 11, 2026 at 06:27 PM

A company has many applications. Different teams in the company developed the applications by using multiple languages and frameworks. The applications run on premises and on different servers with different operating systems. Each team has its own release protocol and process. The company wants to reduce the complexity of the release and maintenance of these applications.

The company is migrating its technology stacks, including these applications, to AWS. The company wants centralized control of source code, a consistent and automatic delivery pipeline, and as few maintenance tasks as possible on the underlying infrastructure.

What should a DevOps engineer do to meet these requirements?

Suggested Answer: D

because of 'as few maintenance tasks as possible on the underlying infrastructure'. Fargate does that better than 'one centralized application server'


Get Premium DOP-C02 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
21 comments · newest first
SO
Sonal Chauhan 11 days ago
I lean towards D because using per application Docker images in ECR and deploying to ECS on Fargate minimizes maintenance on the underlying infrastructure.
LA
Lashaunda 2 months ago
D gives centralized control and automation. Perfect fit!
MI
Micaela 2 months ago
C is interesting, but managing AMIs can be tricky.
RE
Reita 2 months ago
B is too slow, building one at a time isn't efficient.
DA
Dawne 2 months ago
Option A seems too complex with branches.
LE
Lenna 3 months ago
Agreed! ECS with Fargate reduces maintenance.
DE
Deangelo 3 months ago
I think option D is the best choice. Docker simplifies deployment.
MA
Martha 3 months ago
I disagree with B; having separate repos is a better practice.
LY
Lyla 3 months ago
Wait, are we really going to use Docker for everything? Seems overkill.
MA
Matilda 3 months ago
Definitely leaning towards C for better scalability.
AN
An 3 months ago
I think A could work too, but it might get messy with branches.
EL
Elvera 4 months ago
Option D seems like the best choice for modern apps.
TE
Terrilyn 4 months ago
C sounds good, but managing AMIs can be a hassle.
AR
Arlie 4 months ago
Surprised there's no mention of microservices here!
GE
Geraldo 4 months ago
A centralized repo could lead to merge conflicts.
SH
Shayne 6 months ago
I think B is too simplistic for multiple apps.
RO
Ronnie 6 months ago
Option D seems like the best choice for modern deployments!
LI
Lisbeth 6 months ago
I recall that using CloudFormation can simplify infrastructure management, but I'm not clear on how it fits with the AMIs in option C. It seems like a lot to manage.
ZO
Zona 7 months ago
I practiced a similar question where we had to centralize deployments. I feel like having separate repositories might help with organization, but I wonder if it complicates the pipeline.
RE
Reita 7 months ago
I think option D sounds familiar. Using Docker and ECS seems like a good way to manage different applications, but I'm unsure about the specifics of Fargate.
OR
Ora 7 months ago
I remember studying about using CodeCommit for version control, but I'm not sure if one repo for all apps is the best approach. It could get messy with branches.
0/2000 characters

Save Cancel