MENU
Which statement is true about batch size?
Suggested Answer: D
Get Premium SAFe-Agilist Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
39 comments · newest first
IV
Ivory
11 months ago
Wait, are we really saying large batches ensure quality? That sounds off!
CH
Chery
11 months ago
Not sure about B, large batches can actually hurt quality sometimes.
AN
Anissa
11 months ago
D makes sense too, flow usually means smaller batches.
IZ
Izetta
11 months ago
I think C is spot on. Large batches really do limit options.
NO
Noel
12 months ago
A is definitely true! Smaller tasks = smaller batches.
TE
Tequila
12 months ago
I have a vague recollection that large batch sizes are not great for quality, but I can't remember if that relates to B or C.
GE
Geraldo
12 months ago
I feel like we practiced a question similar to this, and I think A might be the right choice since breaking stories into tasks usually means smaller batches.
SH
Sherman
1 year ago
I'm not entirely sure, but I think large batch sizes might actually hinder preserving options, which could point to C.
MY
My
1 year ago
I remember discussing how smaller batch sizes can improve flow, so maybe D is correct?
KA
Kattie
1 year ago
Large batch sizes can limit options, that much I remember. Now I just need to figure out how that relates to the other statements.
SO
Solange
1 year ago
Okay, I know that small batch sizes are generally better for quality and flexibility. I'll focus on that as I consider the options.
LO
Louann
1 year ago
Hmm, I'm a bit unsure about the difference between batch size and flow. Let me think this through carefully.
SH
Shizue
1 year ago
This question seems straightforward, I think I can handle it.
SH
Shaun
1 year ago
Hmm, I think the safest approach here would be to replace the Cart-Show controller route in the client cartridge and add the datalayer object to the viewData variable. That way, I can ensure the LINK cartridge functionality is preserved.
MA
Magnolia
1 year ago
The key here is to focus on where you can run tests in Azure Sentinel. I'd say the most likely place would be the Playbooks section, so I'm going to go with A.
WA
Wade
1 year ago
I'm pretty sure this is about the monitoring options in the Add Data feature, but I'm not 100% sure what the correct answer is. I'll have to think this through carefully.
TA
Talia
1 year ago
This looks like a tricky networking question. I'll need to carefully read through the options and think about the implications of the different flag settings.
LE
Leonora
1 year ago
This question reminds me of one we did in practice about adjusting basis, but I can't recall the specifics of the formula we used for splits.
CH
Chantell
1 year ago
Hey, did you hear about the programmer who got stuck in the bathtub? He tried to apply agile principles and ended up in a small batch!
HU
Huey
1 year ago
Hmm, I'm torn between A and D. I guess it depends on whether you're talking about stories or the actual work flow.
RE
Reed
1 year ago
It seems like both A and D could be true depending on the context.
GA
Gary
1 year ago
D) When there is flow it means there are small batch sizes
FR
Francene
1 year ago
A) When stories are broken into tasks it means there are small batch sizes
TE
Temeka
1 year ago
I think option C is the winner here. Large batch sizes limit flexibility, which is a big no-no in Agile.
LI
Lizette
1 year ago
Option C is definitely the best choice when it comes to batch size.
TO
Tomas
1 year ago
Small batch sizes are crucial for maintaining flexibility in Agile.
AD
Adell
1 year ago
I agree, large batch sizes limit the ability to preserve options.
SE
Serita
1 year ago
Batch size is all about efficiency, and large batches are clearly the way to go according to option B.
FI
Filiberto
1 year ago
Small batch sizes are better for maintaining flow
LA
Lamonica
1 year ago
But large batch sizes limit the ability to preserve options
ER
Erinn
1 year ago
Large batch sizes ensure time for built-in quality
LA
Laine
2 years ago
I agree with Alease, A makes more sense because small batch sizes allow for flexibility
AL
Alease
2 years ago
I disagree, I believe the answer is A
CR
Cristal
2 years ago
Option D makes the most sense to me. Small batch sizes are necessary for flow and to preserve options.
BE
Becky
1 year ago
Large batch sizes do not ensure time for built-in quality.
ER
Ernest
1 year ago
When stories are broken into tasks, it means there are small batch sizes.
SU
Sunny
1 year ago
I agree, large batch sizes limit the ability to preserve options.
BE
Bette
1 year ago
Small batch sizes are important for flow and preserving options.
RE
Renay
2 years ago
I think the answer is C