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
5 months agoRikki
5 months agoJacqueline
5 months agoSage
5 months agoMicah
6 months agoFletcher
6 months agoHassie
6 months agoPenney
6 months agoChristoper
6 months agoEllen
6 months agoIsidra
6 months agoLeah
6 months agoVincenza
6 months agoLorean
6 months agoChau
7 months agoVilma
12 months agoRosalind
11 months agoAlisha
11 months agoReena
11 months agoErnie
11 months agoAnastacia
11 months agoSang
11 months agoAlva
12 months agoEmmanuel
12 months agoAnabel
12 months agoMartin
10 months agoRachael
10 months agoLorrine
10 months agoSherill
11 months agoStephaine
1 year agoShayne
1 year agoCatina
1 year agoMozell
11 months agoGracia
11 months agoSalley
11 months agoPura
12 months agoDaniela
1 year ago