Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Question 36 of 108
Free Preview · 108 of 359 · questions 1–108 of 359 are free. Sign up free to sync your progress across devices.
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
B. Replace the application's features with appropriate microservices in phases. When transitioning from a monolithic application to a microservices architecture, it is generally best to do it incrementally, rather than all at once. This allows you to break down the application into smaller, manageable pieces and make sure each piece is functioning correctly before moving on to the next. It minimizes risk, allows for easier troubleshooting, and reduces the impact on the business because you can gradually shift traffic to the new services as they are tested and deployed.
Here's why the other options are less suitable: A. Deploying the application to Compute Engine with autoscaling does not change the architecture from monolithic to microservices. It may help with some scaling issues but does not achieve the goal of re-architecting the application. C. Refactoring the entire monolithic application into microservices in a single effort can be very risky. It can introduce complex issues that are hard to troubleshoot, and if something goes wrong, it could impact the entire business. D. Building a new application separate from the monolith and replacing it once complete is another approach, but it can be less efficient than replacing in phases. It requires a big-bang cutover, which can be risky. Phased approaches allow for gradual cutover and testing in production with real users, which can lead to a more reliable outcome.
Option B is most logical in this situation.