PROFESSIONAL-CLOUD-DEVELOPER · Question #138
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
The correct answer is A. Migrate the Product catalog, which has integrations to the frontend and product database.. When migrating a revenue-critical ecommerce application in stages, the guiding principle is to start with the component that has the fewest external dependencies and lowest business risk. The Product catalog is a largely read-only, display service with simple integrations (fronte
Question
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?
Options
- AMigrate the Product catalog, which has integrations to the frontend and product database.
- BMigrate Payment processing, which has integrations to the frontend, order database, and third-
- CMigrate Order fulfillment, which has integrations to the order database, inventory system, and
- DMigrate the Shopping cart, which has integrations to the frontend, cart database, inventory
How the community answered
(36 responses)- A83% (30)
- B8% (3)
- C6% (2)
- D3% (1)
Explanation
When migrating a revenue-critical ecommerce application in stages, the guiding principle is to start with the component that has the fewest external dependencies and lowest business risk. The Product catalog is a largely read-only, display service with simple integrations (frontend + product database). A failure in the product catalog is visible but not immediately revenue-blocking (users can't browse but existing carts still work). This makes it the safest first migration candidate. Payment processing (B) is extremely high-risk-it integrates with third parties and directly handles revenue; a failure here causes immediate financial loss. Order fulfillment (C) has complex integrations with inventory and shipping systems. Shopping cart (D) is deeply intertwined with frontend, inventory, and cart database. Both C and D have more dependencies and higher risk than the catalog. Migrating the simplest component first validates the migration process with minimal risk.
Topics
Community Discussion
No community discussion yet for this question.