Your team uses continuous delivery.
What are two reasons to keep the batch size small? (Choose two.)
Suggested Answer: B, D
Get Premium DEVOPSF Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
12 comments · newest first
GW
Gwen
12 months ago
Kaizen blitzes are a great bonus with smaller batches!
LE
Lelia
12 months ago
Wait, can small batches really make that much of a difference?
LO
Louann
12 months ago
Isn't it also about making sure the product owner knows what's delivered?
KA
Kayleigh
1 year ago
Totally agree, smaller batches mean quicker fixes.
IS
Isaac
1 year ago
Keeping batch sizes small helps spot issues fast!
RO
Royce
1 year ago
I think there's something about Kaizen blitzes in there, but I can't recall if that's a main reason for small batch sizes.
CO
Cordell
1 year ago
I feel like option B is definitely right, but I'm a bit confused about the other one. Could it be related to reporting back to customers?
CR
Cristy
1 year ago
I remember practicing a question about how smaller batches can help the product owner track progress better. Maybe that's one of the reasons?
EM
Emile
1 year ago
I think keeping the batch size small helps with identifying root causes quickly, but I'm not sure about the other option.
BR
Breana
1 year ago
I remember learning about Splunk jobs in class, so I'm feeling confident about this one.
MA
Man
1 year ago
Hmm, this is about gratuity tax. I remember there's a specific exemption limit for non-Gratuity Act organizations.
AN
Annice
1 year ago
Hmm, good point Emily. Let me walk through this step-by-step. The responder policy is checking the DIAMETER request, and if the AVP 264 value matches 'host1.example.net', it will redirect the request to 'host.example.com'. So I think the answer is A as well.