GOOGLE-PROFESSIONAL-CLOUD-DEVELOPER practice question 3 of 35

You have been tasked with planning the migration of your company’s application from on-premises to Google Cloud. Your company’s monolithic…

Full set: 265 questions
You have been tasked with planning the migration of your company’s application from on-premises to Google Cloud. Your company’s monolithic application is an ecommerce website. The application will be migrated to microservices deployed on Google Cloud in stages. The majority of your company’s revenue is generated through online sales, so it is important to minimize risk during the migration. You need to prioritize features and select the first functionality to migrate. What should you do?
Answer options
A: Migrate the Product catalog, which has integrations to the frontend and product database. Correct answer
B: Migrate Payment processing, which has integrations to the frontend, order database, and third- party payment vendor.
C: Migrate Order fulfillment, which has integrations to the order database, inventory system, and third-party shipping vendor.
D: Migrate the Shopping cart, which has integrations to the frontend, cart database, inventory system, and payment processing system.
Correct Answer:
A. Migrate the Product catalog, which has integrations to the frontend and product database.
Explanation

To minimize risk when migrating a monolith to microservices, the best practice is to start with a functionality that has the fewest dependencies and is less transactionally complex. This approach, often part of the "strangler fig" pattern, allows the development team to learn and validate the migration process on a lower-risk component. The Product catalog, with its limited integrations (frontend and product database), is the most loosely coupled option. It is primarily a read-heavy service, and a potential failure would be less catastrophic to immediate revenue generation than a failure in payments or the shopping cart.

Why Incorrect

B. Payment processing is a high-risk, core transactional component with external dependencies; migrating it first is extremely risky and directly impacts revenue.
C. Order fulfillment is a complex backend process with multiple integrations, including third-party systems, making it a poor choice for an initial, low-risk migration.
D. The Shopping cart is a stateful component with numerous critical dependencies (inventory, payments), making it one of the most complex and risky services to extract first.

References

1. Google Cloud Architecture Center, "Best practices for migrating a monolithic app to microservices on Google Kubernetes Engine." In the "Migration strategy" section, under the "Extract services" subsection, the documentation advises: "A good candidate for a first service is one that is small and doesn't have many dependencies." This directly supports selecting the Product catalog (Option A) as it has the fewest dependencies listed.

2. Google Cloud Architecture Center, "Decomposing a monolith into microservices." The document discusses identifying service boundaries by finding "seams" to create "loosely coupled services." The Product catalog represents the clearest "seam" among the choices, as it is less entangled with the core transactional logic of payments, orders, and the shopping cart, thus embodying the principle of loose coupling for an initial migration step.

Scroll to Top