ExamTopics Logo
Mail Us[email protected]
Menu
Amazon Discussions
exam questions

Exam AWS Certified DevOps Engineer - Professional DOP-C02 All Questions

View all questions & answers for the AWS Certified DevOps Engineer - Professional DOP-C02 exam
Go to Exam

Exam AWS Certified DevOps Engineer - Professional DOP-C02 topic 1 question 162 discussion

Exam question from Amazon's AWS Certified DevOps Engineer - Professional DOP-C02
Question #: 162
Topic #: 1
[All AWS Certified DevOps Engineer - Professional DOP-C02 Questions]

A company runs applications in an Amazon Elastic Kubernetes Service (Amazon EKS) cluster. The EKS cluster uses an Application Load Balancer to route traffic to the applications that run in the cluster.

A new application that was migrated to the EKS cluster is performing poorly. All the other applications in the EKS cluster maintain appropriate operation. The new application scales out horizontally to the preconfigured maximum number of pods immediately upon deployment, before any user traffic routes to the web application.

Which solution will resolve the scaling behavior of the web application in the EKS cluster?

  • A. Implement the Horizontal Pod Autoscaler in the EKS cluster.
  • B. Implement the Vertical Pod Autoscaler in the EKS cluster.
  • C. Implement the Cluster Autoscaler.
  • D. Implement the AWS Load Balancer Controller in the EKS cluster.
Show Suggested Answer Hide Answer
Suggested Answer: B 🗳️
by PrasannaBalaji at Dec. 29, 2023, 1:53 p.m.
Disclaimers:
  • - ExamTopics website is not related to, affiliated with, endorsed or authorized by Amazon.
  • - Trademarks, certification & product names are used for reference only and belong to Amazon.

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
Submit Cancel
vmahilevskyi
Highly Voted 1 year, 5 months ago
Selected Answer: B
In my opinion A is incorrect because "The new application scales out horizontally to the preconfigured maximum number of pods immediately upon deployment" means that the Horizontal Pod Autoscaler is already implemented but doesn't resolve the issue with poor performance. This may indicate inappropriate resource allocation. But Vertical Pod Autoscaler will help us "right size" our application. So, for me it's B.
upvoted 10 times
moonj
3 months, 2 weeks ago
But the question is asking "Which solution will resolve the scaling behavior" but not for the performance, then should be A?
upvoted 2 times
...
...
a54b16f
Highly Voted 1 year, 7 months ago
Selected Answer: B
scaled out to maximum when there is no user traffic: this means that the configured pod instance is wrong-sized, for example, need more memory or CPU.
upvoted 8 times
...
nickp84
Most Recent 3 months, 1 week ago
Selected Answer: A
B. Vertical Pod Autoscaler adjusts the CPU/memory resources per pod, not the number of pods. It won’t solve premature scaling out.
upvoted 1 times
...
GripZA
4 months ago
Selected Answer: A
HPA dynamically adjusts the number of pods based on actual metrics, like CPU utilization, memory, or custom metrics. in this case, the app is likely using a static replica count, or has a misconfigured initial replica setting or resource requests that trigger autoscaling early. implementing HPA would ensure pods scale only when needed, based on real usage, e.g CPU > 70%
upvoted 1 times
...
Srikantha
4 months, 3 weeks ago
Selected Answer: A
If scaled "Before" traffic is flew, then option A to control autoscaling
upvoted 1 times
...
DKM
5 months ago
Selected Answer: C
Enable Cluster Autoscaler: Ensure that the Cluster Autoscaler is enabled and configured to scale the number of nodes based on the actual demand. Verify that the Cluster Autoscaler is not causing unnecessary scaling by reviewing its configuration and logs.
upvoted 1 times
...
spring21
8 months, 2 weeks ago
Selected Answer: A
For stateless applications with variable traffic, start with HPA. For stateful or resource-intensive applications, start with VPA.
upvoted 2 times
...
VerRi
9 months, 2 weeks ago
Selected Answer: B
The keywords here are "immediately upon deployment" If the pods scale to the max immediately, it indicates that the pods may not have enough resources to handle the workload
upvoted 3 times
...
auxwww
1 year ago
Selected Answer: A
The app is currently deployed as Deployment with a set of replicas which explains that it scales to the maximum set without any traffic. It needs HPA to scale up in response to traffic not Vertical Pod Autoscaler which is in response to adding more cpu/mem resources to already running pods
upvoted 4 times
...
jamesf
1 year ago
Selected Answer: B
Should be B keywords: "scaled out to maximum before user traffic route to web application" - this means that the configured pod instance is wrong-sized before user traffic, which need more cpu or memory. increase CPU/memory for resources - Vertical Pod Autoscaler increase pod for traffic - Horizontal Pod Autoscaler
upvoted 4 times
...
that1guy
1 year, 3 months ago
Selected Answer: A
It's A, in Kubernetes you can specific the number of pod replicas without the use of HPA. "The new application scales out horizontally to the preconfigured maximum number of pods This would imply that they are doing it statically currently.
upvoted 3 times
...
seetpt
1 year, 3 months ago
Selected Answer: B
B for me
upvoted 3 times
...
dkp
1 year, 4 months ago
Selected Answer: A
Ans: A Horizontal Pod Autoscaler (Option A) is the most appropriate solution for adjusting the number of pods based on CPU and memory utilization. Vertical Pod Autoscaler (Option B) adjusts the CPU and memory reservations for pods, which might not directly address the scaling behavior issue in this scenario.
upvoted 1 times
...
WhyIronMan
1 year, 4 months ago
Selected Answer: A
A. Assuming that the first part of the question is related to replicas, which is the max number controlled by the deployment, the Replicaset will set it to the maximum Kind: deployment Replicas:4 which means this is NOT necessarily HPA, just replica set. So, there is a need to configure the HPA properly, BASED on CPU other them STATiC
upvoted 2 times
WhyIronMan
1 year, 4 months ago
but then, when it comes to resources, seems to be B, so changing my to B
upvoted 1 times
...
...
ogerber
1 year, 5 months ago
Selected Answer: B
Given the nature of the problem — scaling out to the maximum number of pods prematurely, the issue appears to be related to resource allocation rather than the need to handle increased traffic/load. Option B (Implement the Vertical Pod Autoscaler in the EKS cluster) is more likely to address the underlying issue by optimizing the resource allocation for the pods, which could prevent the unnecessary immediate scale-out of the application. VPA adjusts pod resources to match their needs more accurately, potentially mitigating the need for immediate horizontal scaling.
upvoted 4 times
...
thanhnv142
1 year, 6 months ago
Selected Answer: A
A is correct: There are problem with horizontal scale so we need to implement it properly
upvoted 2 times
...
matanasov
1 year, 7 months ago
Selected Answer: A
The key here is "preconfigured maximum number of pods". The HPA should be configured to scale the number of pods up based on actual CPU utilization, not based on a preconfigured maximum number of pods.
upvoted 2 times
...
Load full discussion...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel