An online retail enterprise currently hosts a monolithic backend application on a fleet of Compute Engine virtual machines. As business demand increases, the engineering team encounters several challenges: Deployment velocity: Releasing minor bug fixes or features requires building, testing, and deploying the entire monolithic codebase, resulting in multi-week release cycles. Operational overhead and technical debt: Teams spend substantial engineering effort patching operating systems, managing server configurations, and maintaining tightly coupled code. Resource utilization: Compute Engine instances run continuously to handle potential traffic spikes, incurring high baseline infrastructure costs during low-traffic periods. You need to modernize the architecture to support independent CI/CD release cycles, eliminate infrastructure management overhead, and achieve rapid elasticity with zero idle cost. Which modernization strategy should you recommend?

Decompose the application into modular, containerized microservices and event-driven services deployed on Cloud Run and Cloud Run functions, integrated with automated CI/CD pipelines and Pub/Sub messaging.: ### What serverless microservices architecture is A serverless microservices architecture breaks down a large, monolithic application into smaller, loosely coupled domain services. Deploying these containerized components onto fully managed services like **Cloud Run** and **Cloud Run functions** abstracts away all underlying server and infrastructure management while leveraging native Google Cloud event-driven tools like **Pub/Sub** and **Eventarc**. ### How it meets the requirements - **Deployment velocity & CI/CD**: Decoupling the monolith into independent microservices enables individual product teams to establish dedicated CI/CD pipelines (e.g., using Cloud Build). Teams can deploy isolated services quickly without re-testing or deploying the entire system. - **Eliminate infrastructure management**: **Cloud Run** and **Cloud Run functions** provide serverless execution environments, removing the need for operating system maintenance, node provisioning, and virtual machine patching. - **Elasticity and zero idle costs**: Serverless platforms provide instant autoscaling to handle rapid traffic fluctuations and automatically scale down to zero instances during idle periods, significantly reducing baseline operational expenses. ### Key advantages and capabilities - **True pay-per-use model**: Incur compute costs only when requests or events are actively processed. - **Container portability**: Standard OCI containers allow developers to package dependencies consistently across local and cloud environments. - **Reduced blast radius**: Failures or bugs within one microservice do not bring down unrelated business capabilities. - **Native asynchronous integration**: Seamlessly decouples background tasks using **Pub/Sub** and **Workflows**. ### Why this is optimal Migrating directly to serverless container and event platforms addresses the organizational shift toward agility and cost efficiency. It eliminates legacy VM maintenance debt while granting development teams the autonomy to innovate and release code continuously.

StudyCerts

Modernize Monolith Serverless Cloud Run | 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

Modernize Monolith Serverless Cloud Run

Section: Evolution of business needs

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 currently hosts a monolithic backend application on a fleet of Compute Engine virtual machines. As business demand increases, the engineering team encounters several challenges:

Deployment velocity: Releasing minor bug fixes or features requires building, testing, and deploying the entire monolithic codebase, resulting in multi-week release cycles.
Operational overhead and technical debt: Teams spend substantial engineering effort patching operating systems, managing server configurations, and maintaining tightly coupled code.
Resource utilization: Compute Engine instances run continuously to handle potential traffic spikes, incurring high baseline infrastructure costs during low-traffic periods.

You need to modernize the architecture to support independent CI/CD release cycles, eliminate infrastructure management overhead, and achieve rapid elasticity with zero idle cost.

Which modernization strategy should you recommend?

Decompose the application into modular, containerized microservices and event-driven services deployed on Cloud Run and Cloud Run functions, integrated with automated CI/CD pipelines and Pub/Sub messaging.

Maintain the monolithic virtual machines on Compute Engine, implement Cloud Memorystore for Redis in-memory caching, and conduct code profiling to reduce database load.

Rehost the monolithic application across a Compute Engine Managed Instance Group (MIG) configured with predictive autoscaling, and automate VM image creation using CI/CD pipelines.

Refactor the monolith into containerized services hosted on custom, self-managed Kubernetes clusters on Compute Engine VMs with manual node provisioning.

Professional Cloud Architect

Modernize Monolith Serverless Cloud Run

Related questions