An organization wants to move from a tactical cloud adoption approach to a transformational approach. How should they adapt the way they lead the organization?

Question

Options

• AIncrease top-down visibility and foster a culture of blamelessness
• BShift from an operational expenditure model to capital expenditure
• CDrive cloud adoption with an individual contributor focus
• DInvest in on-premises infrastructure to redesign relationships between IT and employees

• A
  78% (39)
• B
  14% (7)
• C
  2% (1)
• D
  6% (3)

Explanation

Moving from a tactical to a transformational cloud adoption approach requires a cultural and leadership shift, not just a technical one. 'Top-down visibility' means leadership must be actively engaged and transparent about cloud strategy across the organization. A 'culture of blamelessness' (a core SRE and DevOps principle) encourages teams to report failures and experiment without fear of punishment, which is essential for the innovation and continuous improvement that define a transformational approach. Option B is wrong because transformational cloud adoption actually moves away from capital expenditure (CapEx) toward operational expenditure (OpEx). Option C (individual contributor focus) is too narrow - transformation requires organizational alignment. Option D (investing in on-premises) directly contradicts cloud adoption goals.

No community discussion yet for this question.