Communication & Stakeholder Relations Flashcards
7 cards from real AZ-301 practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Communication & Stakeholder Relations flashcards as text
A product owner wants to accelerate an Azure deployment timeline by skipping the security review. How should an architect respond?
Answer: Clearly explain the regulatory and business risks of bypassing security review and propose a streamlined fast-track security assessment as an alternative
Proposing a streamlined alternative addresses the time concern while preserving necessary oversight, demonstrating both responsiveness and responsibility.
A stakeholder requests that an Azure architecture support an undefined future global expansion. How should an architect document and communicate this non-functional requirement?
Answer: Record it as an assumption with specific triggers (e.g., expansion to 3+ regions) that would prompt an architecture review, and have the stakeholder acknowledge it
Documenting vague future requirements as assumptions with defined triggers manages stakeholder expectations while avoiding over-engineering.
An Azure architect is onboarding a new technical stakeholder who missed the initial design sessions. Which artifact is most efficient for bringing them up to speed on key decisions?
Answer: A curated set of Architecture Decision Records (ADRs) and the current architecture diagram with annotations
ADRs paired with annotated architecture diagrams efficiently convey both what was built and why, enabling rapid onboarding of new technical stakeholders.
During an Azure architecture governance review, an executive asks why the team chose Azure Kubernetes Service over Azure App Service. Which response demonstrates architectural communication best practice?
Answer: Reference the documented ADR that compared containerization needs, scaling requirements, and team expertise, summarizing the key trade-offs that led to the AKS decision
Referencing a documented ADR shows structured decision-making and translates technical rationale into terms relevant to governance reviewers.
A stakeholder is frustrated that an Azure solution delivered all agreed features but still does not meet their expectations. What is the most likely root cause and how should the architect address it?
Answer: There was a gap between stated requirements and actual business needs; conduct a retrospective to identify the missing context and use it to refine the requirements process
A gap between stated requirements and actual needs is a communication failure; a retrospective prevents recurrence and realigns the solution.
An architect is asked to present Azure architecture diagrams in a board-level meeting. Which diagram type is most appropriate?
Answer: A high-level conceptual diagram showing major components, data flows, and business capabilities without implementation details
Board-level audiences need conceptual diagrams that map architecture to business outcomes, not implementation details.
A legal stakeholder requires that all Azure data processing activities be documented for an upcoming audit. How should an architect support this requirement?
Answer: Produce a data flow diagram mapped to Azure services, annotated with data classification, processing purpose, and applicable compliance controls
A purpose-annotated data flow diagram directly serves audit needs by linking architecture components to compliance controls and data processing purposes.