A change affects many teams and they resist it. What should the architect use?
Why D is the answer
Stakeholder and change management
Stakeholder and change management helps when a change meets resistance across teams.
In detail
- Stakeholder and change management addresses resistance.
- Listen to objections.
Use case
An illustrative scenario, not a real incident.
Teams resist a platform change, so an architect involves them early and explains why.
See it in different ways
mindmap
root((Change))
Migration
Migration Center
Licenses
Finance
CapEx to OpEx
People
Training
Stakeholders
Delivery
Service catalogflowchart LR S0["Identify stakeholders"] --> S1["Explain why"] --> S2["Listen"] --> S3["Roll out"]
Key point: Change needs stakeholder management.
Why the other options are wrong
- A. A bigger VPC
- A VPC is unrelated.
- B. A new billing account
- Billing is unrelated.
- C. A larger logging budget
- A budget is unrelated.

