Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
An enterprise organization is planning to migrate its mission-critical retail application to Google Cloud. The project involves cross-functional stakeholders who have competing priorities:
You are the lead Cloud Architect facilitating the initial discovery sessions. Which facilitation approach should you use to establish a shared understanding of technical constraints and achieve consensus on target architectural outcomes?
This approach involves the Cloud Architect designing a complete technical blueprint in a vacuum using standard reference patterns and presenting it to stakeholders in a one-way broadcast session to secure approval.
The organization had already completed discovery and established strict corporate landing zone standards that were non-negotiable across all projects.
Collaborative discovery is an interactive stakeholder management methodology where a Cloud Architect brings together cross-functional business, security, finance, and engineering leaders. The goal is to elicit operational and technical requirements in a shared forum, translating broad business desires into quantified metrics such as Service Level Objectives (SLOs), Recovery Time Objectives (RTO), and Recovery Point Objectives (RPO).
This approach directly addresses the challenge of balancing multi-disciplinary organizational needs. Rather than imposing top-down technical choices or allowing one department's priorities to overshadow others, structured workshops provide a transparent mechanism to reconcile technical feasibility, compliance mandates, and business outcomes.
Siloed requirement gathering involves holding one-on-one interviews or departmental meetings in isolation, compiling disjointed requirement documents, and designing the architecture without collective group interaction.
Individual discovery interviews were used solely as an initial preparatory step to gather raw background data before conducting a unified cross-functional alignment workshop.
This approach focuses exclusively on functional features (business capabilities and UI logic) during initial discovery and design, postponing non-functional requirements (NFRs)—such as data residency, security controls, availability, and cost governance—to later testing phases.
The team were building a non-critical, throwaway proof-of-concept (PoC) where compliance, enterprise data security, and production uptime were explicitly out of scope.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated