CompTIA CAS-005 Exam - Topic 4 Question 11 Discussion

Actual exam question for CompTIA's CAS-005 exam

Question #: 11
Topic #: 4

A developer makes a small change to a resource allocation module on a popular social media website and causes a memory leak. During a peak utilization period, several web servers crash, causing the website to go offline. Which of the following testing techniques is the most efficient way to prevent this from reoccurring?

ALoad

BSmoke

CRegression

DCanary

Show Suggested Answer

Suggested Answer: C

Comprehensive and Detailed Step-by-Step

Regression testing ensures that new changes do not break existing functionality. It would have identified the memory leak before deployment, preventing downtime.

by Alba at Mar 09, 2025, 10:12 AM

Limited Time Offer

25%

Off

Get Premium CAS-005 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Fabiola

4 months ago

Not sure if smoke testing would help in this case.

upvoted 0 times

...

Denae

5 months ago

Definitely need to do load tests during peak times.

upvoted 0 times

...

Mozell

5 months ago

Wait, canary testing? That’s a new one for me!

upvoted 0 times

...

Fausto

5 months ago

I think regression testing would be more effective.

upvoted 0 times

...

Shannon

5 months ago

Load testing is key to catch those issues!

upvoted 0 times

...

Denny

6 months ago

Smoke testing seems too basic for this situation; I don't think it would catch something like a memory leak.

upvoted 0 times

...

Peggy

6 months ago

I feel like canary testing might be useful too, but I can't recall if it directly addresses memory leaks.

upvoted 0 times

...

Genevieve

6 months ago

I remember practicing regression testing questions, and it seems like that would catch the memory leak after changes are made.

upvoted 0 times

...

Laura

6 months ago

I think load testing could help identify issues under peak conditions, but I'm not entirely sure if it's the best choice here.

upvoted 0 times

...

Sonia

6 months ago

Canary testing sounds interesting, but I'm not sure it's the most efficient approach here. Wouldn't that be more for rolling out new features gradually?

upvoted 0 times

...

Latrice

6 months ago

Regression testing could be a good way to catch this kind of bug, especially if it's a change to an existing module. I'd want to make sure we have a solid regression suite in place.

upvoted 0 times

...

Hildred

6 months ago

Hmm, I'm a bit confused here. Is smoke testing really the best option to prevent a memory leak issue? I feel like we need something more comprehensive.

upvoted 0 times

...

Twila

6 months ago

This seems like a tricky one. I'm thinking load testing might be the way to go, since the issue was caused by high utilization. But I'm not totally sure.

upvoted 0 times

...

Lauran

6 months ago

Canary testing could be really useful here. We can roll out the change to a small subset of servers first to see how it performs.

upvoted 0 times

...

Frank

6 months ago

Regression testing could be a solid option to ensure no regressions are introduced with the code change. Gotta cover all our bases.

upvoted 0 times

...

Joesph

6 months ago

Hmm, I'm a bit unsure here. Smoke testing might be a good place to start, but I'm not sure if that would be the most efficient way to prevent this issue.

upvoted 0 times

...

Lacey

6 months ago

This seems like a tricky one. I'm thinking load testing might be the best approach to catch memory leaks during peak usage.

upvoted 0 times

...

Hubert

1 year ago

Canary testing could also be useful to gradually roll out changes and monitor for any issues.

upvoted 0 times

...

Whitley

1 year ago

I believe Regression testing is also important to ensure the fix didn't break anything else.

upvoted 0 times

...

Audra

1 year ago

I agree with Xuan, Load testing can help identify performance issues.

upvoted 0 times

...

Laticia

1 year ago

Smoke testing is the way to go. Keep it simple, keep it fast, and keep those servers from crashing again.

upvoted 0 times

Leontine

11 months ago

A: Let's make sure to include smoke testing in our regular testing process to prevent this from happening again.

upvoted 0 times

...

Della

11 months ago

A: Let's make sure to include smoke testing in our regular testing process to avoid any future issues with resource allocation.

upvoted 0 times

...

Rossana

12 months ago

B: Agreed, smoke testing is quick and efficient. It's a good way to prevent any memory leaks from causing problems.

upvoted 0 times

...

Adolph

12 months ago

B: Agreed, smoke testing is quick and effective at catching major issues like this.

upvoted 0 times

...

Mira

12 months ago

A: We should definitely do some smoke testing to catch any potential issues before they cause the servers to crash again.

upvoted 0 times

...

Katina

1 year ago

A: We should definitely do some smoke testing to catch any memory leaks before they cause servers to crash.

upvoted 0 times

...

Margret

1 year ago

Hey, at least it wasn't a Titanic-sized memory leak, am I right? Load testing all the way!

upvoted 0 times

...

Margarita

1 year ago

Regression testing, for sure. Can't let those previous bugs sneak back in. Gotta keep an eye on the whole system.

upvoted 0 times

Gracia

1 year ago

D) Canary

upvoted 0 times

...

Cary

1 year ago

C) Regression

upvoted 0 times

...

Haydee

1 year ago

A) Load

upvoted 0 times

...

Amira

1 year ago

I'm thinking Canary would be the way to go. Roll out the changes gradually and catch any issues early on.

upvoted 0 times

...

Xuan

1 year ago

I think the answer is A) Load testing.

upvoted 0 times

...

Yaeko

1 year ago

Definitely go with load testing. Gotta stress that system and find those pesky memory leaks!

upvoted 0 times

Mertie

1 year ago

B: I agree, we can't afford to have the website crash again during peak utilization. Load testing is key.

upvoted 0 times

...

Micheline

1 year ago

A: Load testing is definitely the way to go. We need to stress test the system to find those memory leaks.

upvoted 0 times

...