Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25

- Free Preparation Discussions

Scaled Agile SAFe-Agilist Exam - Topic 7 Question 29 Discussion

Actual exam question for Scaled Agile's SAFe-Agilist exam

Question #: 29
Topic #: 7

[All SAFe-Agilist Questions]

Which statement is true about batch size?

AWhen stories are broken into tasks it means there are small batch sizes

BLarge batch sizes ensure time for built-in quality

CLarge batch sizes limit the ability to preserve options

DWhen there is flow it means there are small batch sizes

Show Suggested Answer

Suggested Answer: D

by Hollis at May 28, 2024, 09:41 AM

Limited Time Offer

25%

Off

Get Premium SAFe-Agilist Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Ivory

8 months ago

Wait, are we really saying large batches ensure quality? That sounds off!

upvoted 0 times

...

Chery

8 months ago

Not sure about B, large batches can actually hurt quality sometimes.

upvoted 0 times

...

Anissa

8 months ago

D makes sense too, flow usually means smaller batches.

upvoted 0 times

...

Izetta

8 months ago

I think C is spot on. Large batches really do limit options.

upvoted 0 times

...

Noel

9 months ago

A is definitely true! Smaller tasks = smaller batches.

upvoted 0 times

...

Tequila

9 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.

upvoted 0 times

...

Geraldo

9 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.

upvoted 0 times

...

Sherman

9 months ago

I'm not entirely sure, but I think large batch sizes might actually hinder preserving options, which could point to C.

upvoted 0 times

...

My

9 months ago

I remember discussing how smaller batch sizes can improve flow, so maybe D is correct?

upvoted 0 times

...

Kattie

9 months 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.

upvoted 0 times

...

Solange

9 months 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.

upvoted 0 times

...

Louann

9 months ago

Hmm, I'm a bit unsure about the difference between batch size and flow. Let me think this through carefully.

upvoted 0 times

...

Shizue

10 months ago

This question seems straightforward, I think I can handle it.

upvoted 0 times

...

Shaun

10 months 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.

upvoted 0 times

...

Magnolia

10 months 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.

upvoted 0 times

...

Wade

10 months 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.

upvoted 0 times

...

Talia

10 months 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.

upvoted 0 times

...

Leonora

10 months 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.

upvoted 0 times

...

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!

upvoted 0 times

...

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.

upvoted 0 times

Reed

1 year ago

It seems like both A and D could be true depending on the context.

upvoted 0 times

...

Gary

1 year ago

D) When there is flow it means there are small batch sizes

upvoted 0 times

...

Francene

1 year ago

A) When stories are broken into tasks it means there are small batch sizes

upvoted 0 times

...

...

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.

upvoted 0 times

Lizette

1 year ago

Option C is definitely the best choice when it comes to batch size.

upvoted 0 times

...

Tomas

1 year ago

Small batch sizes are crucial for maintaining flexibility in Agile.

upvoted 0 times

...

Adell

1 year ago

I agree, large batch sizes limit the ability to preserve options.

upvoted 0 times

...

...

Serita

1 year ago

Batch size is all about efficiency, and large batches are clearly the way to go according to option B.

upvoted 0 times

Filiberto

1 year ago

Small batch sizes are better for maintaining flow

upvoted 0 times

...

Lamonica

1 year ago

But large batch sizes limit the ability to preserve options

upvoted 0 times

...

Erinn

1 year ago

Large batch sizes ensure time for built-in quality

upvoted 0 times

...

...

Laine

1 year ago

I agree with Alease, A makes more sense because small batch sizes allow for flexibility

upvoted 0 times

...

Alease

1 year ago

I disagree, I believe the answer is A

upvoted 0 times

...

Cristal

1 year ago

Option D makes the most sense to me. Small batch sizes are necessary for flow and to preserve options.

upvoted 0 times

Becky

1 year ago

Large batch sizes do not ensure time for built-in quality.

upvoted 0 times

...

Ernest

1 year ago

When stories are broken into tasks, it means there are small batch sizes.

upvoted 0 times

...

Sunny

1 year ago

I agree, large batch sizes limit the ability to preserve options.

upvoted 0 times

...

Bette

1 year ago

Small batch sizes are important for flow and preserving options.

upvoted 0 times

...

...

Renay

1 year ago

I think the answer is C

upvoted 0 times

...