Evaluate an Application Design Considering Scalability and Modularity 350-901 Practice Questions (Page 1)

Questions 1–5

1. 1foundation · easy

   In modular design, which characteristic describes a module that has a single, well-defined purpose and contains all the elements necessary to fulfill that purpose?

   • ALoose coupling
   • BHigh cohesion
   • CSeparation of concerns
   • DInformation hiding
   Reveal Solution Discussion Select an answer first
2. 2foundation · easy

   An application is designed as a set of microservices to improve modularity. Which trade-off is most likely to be introduced?

   • ADecreased scalability because each service is limited to a single instance.
   • BIncreased operational complexity due to managing multiple services and their interactions.
   • CReduced ability to reuse code across the application.
   • DSimpler debugging because all code is in one place.
   Reveal Solution Discussion Select an answer first
4. 3expert · hard

   A startup has a monolithic application that is becoming difficult to maintain. They want to improve modularity by breaking it into microservices. However, they have a small team and a tight deadline for a new feature. The CTO is concerned that a full microservices migration will delay the feature. What is the most balanced approach?

   • AKeep the monolith and add a new feature as a separate microservice.
   • BUse the strangler fig pattern to gradually extract services while keeping the monolith running.
   • CScale the monolith horizontally and defer all modularity work.
   • DDo a complete rewrite of the monolith into microservices before adding any new features.
   Reveal Solution Discussion Select an answer first
5. 4expert · hard

   A team is designing a system that must handle unpredictable spikes in traffic. They are considering two options: (1) a set of always-on VMs that can scale out, and (2) a serverless function that scales automatically. The team has a limited budget and wants to minimize cost during low-traffic periods. What is the most important consideration?

   • AAlways-on VMs are always cheaper because they have a predictable cost.
   • BServerless functions are always the cheapest option for any workload.
   • CServerless functions scale to zero, so you do not pay for idle capacity, but you may pay per invocation and for supporting resources.
   • DAlways-on VMs are more scalable than serverless functions.
   Reveal Solution Discussion Select an answer first
6. 5expert · hard

   A company runs a stateful application that handles WebSocket connections. The application is currently deployed on a single server. To scale, they are considering horizontal scaling with a load balancer. What is the primary challenge they must address?

   • AWebSocket connections cannot be load balanced at all.
   • BThe load balancer must be placed in front of the database to handle WebSocket traffic.
   • CWebSocket connections are tied to a specific server instance, so the load balancer must use sticky sessions or a shared state store.
   • DThe application must be rewritten to use HTTP polling instead of WebSockets.
   Reveal Solution Discussion Select an answer first