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 online retail enterprise is modernizing its enterprise applications and planning its Google Cloud migration. The architecture review board is evaluating disposition strategies for two distinct systems:
The organization has finite software engineering resources and must optimize Total Cost of Ownership (TCO), minimize ongoing operational burden, and maximize competitive advantage.
Which workload disposition strategy should the cloud architect recommend?
This strategy involves abandoning the specialized dynamic pricing algorithm to simplify IT complexity while performing an unoptimized lift-and-shift migration (rehosting) of the existing on-premises HR database onto Compute Engine virtual machines without modernization.
The business had decided that dynamic pricing provided negative ROI and the legacy HR system was an immutable, specialized mainframe workload that could not be replaced by modern SaaS platforms.
This strategy relies exclusively on buying existing commercial software or turnkey third-party products to satisfy both administrative and core customer-facing operations, eliminating all custom in-house software development.
The dynamic pricing and loyalty requirements were completely standard, provided no unique business edge, and the enterprise had decided to phase out all in-house software development entirely.
This approach relies on developing, hosting, and maintaining bespoke custom software internally for all business functions, including generic administrative processes like payroll, accounting, and human resource management.
The organization operated under highly specialized, non-standard jurisdictional mandates that no commercially available software package could satisfy, and had unlimited software engineering capacity.
A strategic workload disposition framework evaluates workloads along two primary dimensions: strategic business differentiation (competitive advantage) and commodity vs. specialized functionality. For non-differentiating, standardized business functions, adopting commercial off-the-shelf (COTS) or Software-as-a-Service (SaaS) offerings minimizes development lead time and long-term maintenance. For proprietary capabilities that drive market distinction, building a custom cloud-native solution ensures complete control over business logic and intellectual property.
Building commodity software consumes engineering capacity without generating distinct market value, whereas purchasing a generic pricing tool fails to deliver the tailored customer loyalty mechanisms required to outpace competitors. Combining COTS for commodity processes with custom build for strategic differentiators delivers the ideal balance of speed, cost, and distinct value.
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