AZ-301 Communication & Stakeholder Relations 3 — Questions and Answers
Question 1: A compliance officer joins an Azure architecture review mid-project and raises GDPR concerns not previously discussed. How should the architect handle this?
- Inform the compliance officer that the design phase is complete and changes are too costly
- Conduct a rapid impact assessment and incorporate GDPR requirements into the architecture backlog (Correct answer)
- Remove all personal data features from the solution
- Ask the compliance officer to submit a formal change request next quarter
Correct answer: Conduct a rapid impact assessment and incorporate GDPR requirements into the architecture backlog
A rapid impact assessment surfaces the scope of required changes and allows them to be prioritized without halting the project.
Question 2: When communicating Azure estimated monthly costs to a non-technical project sponsor, which approach is most effective?
- Share raw Azure Pricing Calculator JSON output
- Present costs in business terms—per transaction, per user, or as a percentage of revenue—alongside a comparison to current spending (Correct answer)
- List individual resource SKUs and their hourly rates
- Only discuss costs if the sponsor asks directly
Correct answer: Present costs in business terms—per transaction, per user, or as a percentage of revenue—alongside a comparison to current spending
Translating infrastructure costs into business-relevant units (cost per user, savings vs. baseline) makes financial impact meaningful to non-technical sponsors.
Question 3: An architect discovers that a stakeholder's requirement would create a vendor lock-in risk with Azure Cognitive Services. What is the best way to surface this concern?
- Implement the requirement silently and document the risk in internal notes only
- Raise the risk in the next stakeholder meeting with a documented risk register entry including likelihood, impact, and mitigation options (Correct answer)
- Refuse to implement the feature
- Replace the requirement with a different feature without informing the stakeholder
Correct answer: Raise the risk in the next stakeholder meeting with a documented risk register entry including likelihood, impact, and mitigation options
Formally documenting risks in a risk register and presenting them to stakeholders ensures informed consent and traceable decision-making.
Question 4: A development team lead disagrees with the architect's recommendation to use Azure Service Bus over Azure Event Grid. What is the most effective resolution approach?
- Override the team lead's objection using seniority
- Schedule a focused technical review comparing messaging patterns, ordering guarantees, and throughput requirements relevant to the use case (Correct answer)
- Let the team lead choose whichever service they prefer without analysis
- Escalate to senior management immediately
Correct answer: Schedule a focused technical review comparing messaging patterns, ordering guarantees, and throughput requirements relevant to the use case
A focused technical review grounded in specific requirements resolves disagreements with evidence rather than hierarchy.
Question 5: A stakeholder asks for weekly Azure cost reports during a cloud migration. Which Azure tool should the architect recommend to automate this communication?
- Azure Monitor Alerts for VM CPU usage
- Azure Cost Management + Billing with scheduled cost export and budget alerts configured to email stakeholders (Correct answer)
- Azure Advisor performance recommendations
- Azure Policy compliance dashboard
Correct answer: Azure Cost Management + Billing with scheduled cost export and budget alerts configured to email stakeholders
Azure Cost Management supports scheduled exports and budget alert emails that automatically deliver cost summaries to stakeholders without manual reporting.
Question 6: During a design review, two business units present conflicting requirements for an Azure shared services architecture. How should the architect facilitate resolution?
- Choose the requirement from the higher-revenue business unit automatically
- Facilitate a joint workshop with both units to identify shared goals and document agreed-upon requirements with sign-off from both parties (Correct answer)
- Design separate independent architectures for each unit to avoid conflict
- Defer the conflict to the next project phase
Correct answer: Facilitate a joint workshop with both units to identify shared goals and document agreed-upon requirements with sign-off from both parties
A joint workshop surfaces shared goals and produces mutually signed-off requirements, preventing future rework from unresolved conflicts.
Question 7: An architect needs to communicate an Azure architecture's recovery time objective (RTO) of 4 hours to operations and business stakeholders. Which scenario best validates that RTO has been understood by both audiences?
- Email the RTO value to all stakeholders and assume receipt equals understanding
- Conduct a tabletop disaster recovery exercise where both operations and business stakeholders walk through the failure scenario and confirm acceptable downtime (Correct answer)
- Include RTO in the architecture diagram footnotes
- Have stakeholders sign the SLA document without a walkthrough
Correct answer: Conduct a tabletop disaster recovery exercise where both operations and business stakeholders walk through the failure scenario and confirm acceptable downtime
Tabletop exercises validate that all stakeholders understand the practical meaning of RTO and confirm business acceptance of the recovery window.
A compliance officer joins an Azure architecture review mid-project and raises GDPR concerns not previously discussed.
How should the architect handle this?