Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Cloud Digital Leader practice bank has an additional 3,070 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A retail company currently operates a large, monolithic e-commerce application. During promotional sales, spikes in checkout traffic force the engineering team to scale the entire application, which significantly increases infrastructure costs. Additionally, a minor bug in the product recommendation feature recently caused the entire website to crash, and deploying new features requires coordinating all development teams for a single monthly release.
The company wants to modernize its application to achieve the following business and technical goals:
Which architectural approach should the company adopt to meet these requirements?
A stateful architecture is a system design in which an application or server retains local persistent data or session state—such as user shopping cart contents, active transaction progress, or local data caches—directly on the compute instance handling the request. Subsequent requests from the same user must be routed back to the exact same server instance to access that locally stored state.
This option represents an architectural anti-pattern for elastic cloud workloads, though stateful configurations are occasionally necessary for specialized workloads like legacy relational databases or persistent media-streaming servers that must maintain continuous local file locks.
Best practices for application modernization emphasize designing stateless architectures rather than stateful ones. By offloading state and caching to managed external services like Memorystore for Redis or Cloud Spanner, stateless microservices can scale up, scale down, and restart instantaneously without losing critical data.
A microservices architecture is a modular software design pattern that decomposes a large, monolithic application into a collection of smaller, independent, and loosely coupled services. Each microservice is built around a specific business capability—such as user authentication, product recommendations, shopping cart management, or payment processing—and communicates with other services through well-defined interfaces like APIs or asynchronous event routers.

Unlike infrastructure-level adjustments that keep the tightly coupled codebase intact, refactoring into loosely coupled microservices directly resolves the architectural root cause of the company's scaling, deployment, and reliability bottlenecks. It transforms a rigid monolith into an agile, resilient, and cost-efficient distributed system.
A custom image is a pre-configured virtual machine boot disk that contains an operating system along with application-specific software, libraries, and settings. An instance template combines this custom boot disk image with a specific machine type and network configuration, allowing Managed Instance Groups (MIGs) on Compute Engine to rapidly provision identical VM instances when scaling out.
The organization wanted to reduce the boot and configuration time of Compute Engine virtual machines in a Managed Instance Group without changing the underlying monolithic architecture of their legacy application.
When modernizing applications for agility, organizations typically move away from VM-level custom images toward containers and microservices. Containers package only the application code and its runtime dependencies, enabling fast startup and independent component deployment.
Vertical scaling (scaling up) is an infrastructure approach where an organization increases the capacity of an existing server or virtual machine (VM) by adding more processing power (CPU) and memory (RAM). In a monolithic environment, migrating to a larger machine type on Compute Engine provides the entire application stack with a bigger pool of shared hardware resources on a single host.
The scenario asked for a quick, short-term way to increase the CPU and memory capacity of a legacy relational database or a tightly coupled third-party application that cannot be refactored or scaled horizontally across multiple instances.
Modern cloud-native architectures favor horizontal scalability (adding more instances or containers) combined with modular design over vertical scaling, as horizontal scaling offers virtually unlimited growth potential and far superior fault tolerance.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated