New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

iSQI CTFL-AT Exam - Topic 1 Question 28 Discussion

Actual exam question for iSQI's CTFL-AT exam
Question #: 28
Topic #: 1
[All CTFL-AT Questions]

Which of the following is a risk that continuous integration introduces?

Show Suggested Answer Hide Answer
Suggested Answer: A

by Roslyn at Jun 03, 2024, 02:24 PM

Limited Time Offer

25%

Off

Get Premium CTFL-AT Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Kris
3 months ago
Wait, are we saying CI makes manual testing obsolete? That sounds off!
upvoted 0 times
...
Wade
3 months ago
D is a real concern, I've noticed a drop in productivity.
upvoted 0 times
...
Herminia
3 months ago
C seems unlikely, manual tests still have their place, right?
upvoted 0 times
...
Bok
4 months ago
Totally agree with B, too many builds can overwhelm testers.
upvoted 0 times
...
Delila
4 months ago
A is definitely a risk, I've seen it happen.
upvoted 0 times
...
Crissy
4 months ago
I recall that D was mentioned in a practice question. Increased workload for developers can definitely impact their output negatively.
upvoted 0 times
...
Sarah
4 months ago
I feel like C is a bit misleading. I know teams can still run manual tests, even with automation being a focus.
upvoted 0 times
...
Chandra
4 months ago
I'm not entirely sure, but I think B makes sense too. If there are too many builds, testers might not cover everything properly.
upvoted 0 times
...
Crista
5 months ago
I remember discussing how over-relying on unit tests could lead to missing critical system tests, so I think A might be a valid risk.
upvoted 0 times
...
Janet
5 months ago
Okay, I've got this. The answer is clearly B - testers can get overwhelmed with too many builds to test, which can reduce the overall quality of testing. Continuous integration is all about speed, but we can't forget about maintaining high standards. I'm feeling good about this one.
upvoted 0 times
...
Ula
5 months ago
Ugh, I'm not sure about this one. All the options seem plausible, but I'm a bit confused. I think I'll need to review my notes on continuous integration before I can make a solid decision. Wish me luck!
upvoted 0 times
...
Eladia
5 months ago
Hmm, this is a good question. I'm pretty sure the answer is A - teams can sometimes over-rely on unit tests and forget about the importance of system and acceptance tests. I'll double-check my understanding, but I feel confident about this one.
upvoted 0 times
...
Abel
5 months ago
This is a tricky one. I think the key is to focus on the risks that continuous integration can introduce, rather than the benefits. I'm leaning towards option B, but I'll need to think it through carefully.
upvoted 0 times
...
Rikki
5 months ago
I feel pretty confident that the action button on a FlexCard can launch a Vlocity Calculation Procedure. That seems like a logical option given the FlexCard's capabilities.
upvoted 0 times
...
Brent
5 months ago
The Workflow Rule solution in option D seems a bit outdated. I don't think that would give the volunteers the interactive experience they need to make those decisions on the spot. I'm feeling more confident about the Flow or Lightning Component approaches.
upvoted 0 times
...
Jolene
10 months ago
Continuous integration is great, but it's not a magical solution. B is the way to go - too many builds can definitely compromise testing. Gotta keep that quality up, folks!
upvoted 0 times
Bulah
8 months ago
Definitely, we need to find a balance to ensure thorough testing.
upvoted 0 times
...
Elly
8 months ago
Yeah, quality is key. We can't let testing suffer because of too many builds.
upvoted 0 times
...
Keneth
8 months ago
B) Testers sometimes have too many builds to test, which reduces the quality of testing.
upvoted 0 times
...
Horace
8 months ago
A) Teams sometimes over-rely on unit tests and exclude some important system and acceptance tests.
upvoted 0 times
...
...
William
10 months ago
A is an interesting one. I can see how teams might over-rely on unit tests and forget about the bigger picture. But I think B is the best answer here. Quality testing is key, and too many builds can really impact that.
upvoted 0 times
Celeste
8 months ago
D is definitely a concern too. Balancing workload is crucial for maintaining productivity.
upvoted 0 times
...
Kayleigh
8 months ago
I think C is also worth considering. Automation is great, but manual tests can still be valuable.
upvoted 0 times
...
Charolette
8 months ago
I see your point, but I think B is a bigger risk. Quality testing should never be compromised.
upvoted 0 times
...
Janine
8 months ago
I agree, A is a valid concern. It's important to not overlook system and acceptance tests.
upvoted 0 times
...
...
My
10 months ago
Haha, D definitely sounds like something my manager would say. 'Developer's workload is increased, which can result in a reduction of output.' That's a risk alright, but not one that continuous integration itself introduces.
upvoted 0 times
...
Charisse
10 months ago
I'm going with C. Teams no longer have the ability to run manual tests, as all tests must be automated. That's a real risk of continuous integration that I've seen in my experience.
upvoted 0 times
Gayla
10 months ago
But having a good balance between automated and manual testing is important for thorough testing.
upvoted 0 times
...
Junita
10 months ago
I agree, relying solely on automated tests can be risky.
upvoted 0 times
...
...
Viola
11 months ago
I think the correct answer is B. Testers sometimes have too many builds to test, which reduces the quality of testing. Continuous integration can definitely lead to an increased workload for testers.
upvoted 0 times
...
Luis
11 months ago
But what about the workload increase for developers? That could also be a significant risk.
upvoted 0 times
...
Curtis
11 months ago
I agree with Chaya. It's important to have a balance between unit tests and system tests for effective testing.
upvoted 0 times
...
Chaya
11 months ago
I think the risk is that teams might over-rely on unit tests and skip important system tests.
upvoted 0 times
...

Save Cancel