I'm pretty confident that option D is the right answer here. Preserving flexibility in both areas is the best way to implement the "Assume variability; preserve options" principle.
Ah yes, I remember now. Containers are all about packaging and deploying applications consistently across different environments. And they're more resource-efficient than VMs. Those are the two key problems they solve.
Hey, I heard that 'assuming variability' is like assuming your coworker will forget to refill the coffee pot. Might as well just make your own brew, right?
Hmm, I'm torn between B and D. Preserving flexibility in the system functionality and design seems ideal, but I don't want to completely ignore the solution intent either.
I think option D is the way to go. Preserving flexibility in both system functionality and design aligns perfectly with the SAFe principle of 'Assume variability; preserve options'.
Alesia
3 months agoRikki
3 months agoJacqueline
3 months agoSage
4 months agoMicah
4 months agoFletcher
4 months agoHassie
4 months agoPenney
5 months agoChristoper
5 months agoEllen
5 months agoIsidra
5 months agoLeah
5 months agoVincenza
5 months agoLorean
5 months agoChau
5 months agoVilma
10 months agoRosalind
9 months agoAlisha
9 months agoReena
9 months agoErnie
9 months agoAnastacia
10 months agoSang
10 months agoAlva
10 months agoEmmanuel
10 months agoAnabel
10 months agoMartin
8 months agoRachael
8 months agoLorrine
8 months agoSherill
9 months agoStephaine
11 months agoShayne
11 months agoCatina
11 months agoMozell
9 months agoGracia
9 months agoSalley
10 months agoPura
10 months agoDaniela
11 months ago