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: HR & Payroll Processing: Standardized back-office administrative workflows with common regulatory compliance requirements that provide no proprietary market differentiation. Dynamic Pricing & Loyalty Engine: A proprietary real-time algorithmic engine that leverages historical purchase habits to deliver personalized promotions, representing a major competitive differentiator. 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?

Adopt a commercial off-the-shelf (COTS) or SaaS solution for HR & Payroll, and build a custom cloud-native solution on Google Cloud for the Dynamic Pricing & Loyalty Engine.: ### What the Hybrid Build vs. Buy Strategy Is 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. ### How It Meets the Business Requirements - **Competitive Advantage**: Allocates scarce engineering bandwidth directly toward the **Dynamic Pricing & Loyalty Engine**, preserving unique intellectual property and enabling rapid algorithmic iteration. - **Total Cost of Ownership (TCO)**: Buying a SaaS/COTS product for **HR & Payroll** significantly lowers lifetime TCO by avoiding custom code development, continuous maintenance, regulatory updates, and dedicated operational overhead. - **Speed to Market**: Delivers standard back-office functionality rapidly through proven vendor capabilities while focusing in-house teams on high-impact differentiating cloud infrastructure. ### Key Advantages and Capabilities - **Focused Resource Allocation**: Maximizes the return on engineering investment by directing developer talent to proprietary revenue-generating features. - **Operational Efficiency**: Eliminates operational overhead such as patching, specialized tax compliance updates, and standard HR feature development. - **Scalable Differentiation**: Allows the custom pricing engine to leverage specialized Google Cloud analytics and machine learning services for deep customization. - **Reduced Time to Value**: Delivers mature administrative workflows immediately without reinventing standard commodity processes. ### Why This Is Optimal 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.

StudyCerts

Strategic Build Vs Buy Workload Disposition | Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam! | StudyCerts

Professional Cloud Architect

Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Strategic Build Vs Buy Workload Disposition

Section: Workload disposition strategies (e.g., build, buy, modify, or deprecate)

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

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:

HR & Payroll Processing: Standardized back-office administrative workflows with common regulatory compliance requirements that provide no proprietary market differentiation.
Dynamic Pricing & Loyalty Engine: A proprietary real-time algorithmic engine that leverages historical purchase habits to deliver personalized promotions, representing a major competitive differentiator.

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?

Adopt a commercial off-the-shelf (COTS) or SaaS solution for HR & Payroll, and build a custom cloud-native solution on Google Cloud for the Dynamic Pricing & Loyalty Engine.

Deprecate the proprietary Dynamic Pricing & Loyalty Engine in favor of static pricing rules, and rehost the legacy on-premises HR system on Compute Engine virtual machines.

Procure commercial off-the-shelf (COTS) software packages for both workloads to minimize custom development and eliminate in-house operational overhead.

Build custom in-house solutions on Google Cloud for both systems to ensure complete architectural ownership and avoid external software licensing fees.

Professional Cloud Architect

Strategic Build Vs Buy Workload Disposition

Related questions