The correct answer is A, Ambassador. In DevOps transformation, stakeholder mapping is used to understand influence, commitment, resistance, advocacy, and the social dynamics that affect change adoption. An ambassador represents a stakeholder type that can positively influence others, communicate the transformation message, model desired behaviors, and help socialize the vision across teams and organizational boundaries.
This is especially important because DevOps evolution is not simply a technical implementation; it is a leadership-led organizational change. Leaders must identify who can sponsor, advocate, reinforce, or obstruct the change. Ambassadors are valuable because they extend leadership reach and help build credibility among peer groups. They can translate the DevOps vision into practical team-level language and reduce dependency on top-down communication.
"Victim" and "Rescuer" are more closely associated with dysfunctional interaction patterns such as the drama triangle, not a constructive stakeholder category in this context. "Coach" may be a useful change role, but it is not the stakeholder type being tested here. Relevant study guide references: Articulating and Socializing Vision; DevOps and Transformational Leadership; Maintaining Energy and Momentum.