Exam CV0-003 All Questions

View all questions & answers for the CV0-003 exam

Exam CV0-003 topic 1 question 178 discussion

Actual exam question from CompTIA's CV0-003

Question #: 178
Topic #: 1

A systems administrator is troubleshooting an application that is configured to auto-scale with a minimum of two nodes and a maximum of four. The application will scale out if the CPU utilization of one of the nodes exceeds 80% for more than five minutes and will scale in if the CPU utilization of one of the nodes drops under
20% for more than ten minutes. There is a reverse proxy in front of the application. The systems administrator notices two of the nodes are often running over 80% for a long period of time, which is triggering the creation of the other two nodes; however, they are being created and terminated while the load in the first two remains over 50% all the time. Which of the following should the administrator configure to fix this issue?

A. Disable DNS caching in the reverse proxy.
B. Reduce the minimum node count to one.
C. Disable TLS tickets.
D. Reduce the scale-out rule to 50%.
E. Increase the scale-in rule to 50%.

Show Suggested Answer

Suggested Answer: E 🗳️

by ROCompTIA at June 18, 2023, 9:16 a.m.

Comments

Submit Cancel

BigM

5 months, 3 weeks ago

Selected Answer: E

E The issue described suggests that the auto-scaling adds nodes when CPU usage is high but removes them too aggressively, leading to constant scaling activity without stabilizing the load. Current Scale-In Rule is Too Aggressive: The system scales in (removes nodes) when CPU drops below 20% for more than 10 minutes. This is too low of a threshold, meaning nodes get terminated too soon, which then forces the remaining nodes to handle more load again. Why Raising the Scale-In Threshold to 50% Helps: By increasing the scale-in threshold to 50%, extra nodes stay active longer and prevent premature termination. This allows the system to stabilize under a balanced load rather than oscillating between scaling up and down.

upvoted 1 times

...

Pisces225

1 year, 4 months ago

The problem being described is that the application is scaling out at 50% instead of the intended 80%. Zero of the solutions fixes this issue. Which is what you get when CompTIA outsources their questions and testing to India and literally no one reads what they come up with and put into the exams.

upvoted 4 times

...

FasterN8

1 year, 5 months ago

Selected Answer: A

At first there seemed to be no right answer. But the given answer I think is right. If the reverse proxy isn't sending any traffic to the 2 new machines, they themselves trigger the 20% rule and trigger the scale-in action. Disabling DNS caching will force the Rev.proxy to constantly look for new VMs in the pool and finally send traffic their way.

upvoted 3 times

lamborghini

1 year, 1 month ago

It is sending traffic to the new 2 machines. "first two remains over 50% all the time". None of the solution truly fix the issue but I'm going with E

upvoted 1 times

...

Jhonattan0032

1 year, 6 months ago

Selected Answer: E

I think is e

upvoted 2 times

...

Jhonattan0032

1 year, 6 months ago

Selected Answer: E

increasing the scale-in rule to 50%, nodes will only be terminated when their CPU utilization drops below 50%

upvoted 2 times

...

FrancisDrake

1 year, 7 months ago

None of these answers seem to address the problem.

upvoted 4 times

...

ROCompTIA

2 years, 2 months ago

Selected Answer: D

By reducing the scale-out rule to 50%, the auto-scaling system will only trigger the creation of new nodes when the CPU utilization exceeds 50%, instead of the current threshold of 80%. This adjustment will prevent unnecessary creation of new nodes when the load is still relatively high but below 80%

upvoted 1 times

slcc99

2 years, 1 month ago

Since it says "The systems administrator notices two of the nodes are often running over 80% for a long period of time", wouldn't reducing the scale-out rule to 50% solve the problem?

upvoted 2 times

...