Unit 2: Evolution of Cloud Microservices - Practice Quiz

INT363 — Cloud Microservices 60 Questions
0 Correct 0 Wrong 60 Left
0/60

1 What is a monolithic application architecture?

Application Architectures—Monolithic and Distributed Easy
A. An application divided into independent services
B. An application without any business logic
C. An application built as one deployable unit
D. An application running only on mobile devices

2 How do components in a distributed application commonly communicate?

Application Architectures—Monolithic and Distributed Easy
A. Through manual file editing
B. Through local variables only
C. Through one shared function
D. Through network connections

3 What is a common limitation of monolithic architecture?

Application Architectures—Monolithic and Distributed Easy
A. All components scale independently
B. Each feature has its own gateway
C. The whole application is redeployed
D. Every module uses a separate network

4 What is a potential benefit of distributed architecture?

Application Architectures—Monolithic and Distributed Easy
A. Components can be scaled independently
B. All failures become impossible
C. Network communication is always removed
D. Deployment tools are never required

5 What does a microservice usually represent?

Microservice Fundamentals Easy
A. A complete operating system
B. A physical network switch
C. A focused business capability
D. A single database column

6 Which characteristic is commonly associated with a microservice?

Microservice Fundamentals Easy
A. It must share all source code
B. It cannot communicate over networks
C. It must use one programming language
D. It can be deployed independently

7 How do microservices commonly exchange information?

Microservice Fundamentals Easy
A. Using compiler instructions
B. Using APIs or messages
C. Using shared screen pixels
D. Using keyboard shortcuts

8 Which practice supports loose coupling between microservices?

Microservice Fundamentals Easy
A. Storing all logic in one service
B. Combining all deployment pipelines
C. Sharing every internal class
D. Using clear service contracts

9 What is microservices architecture?

Microservices Architecture Easy
A. A system without communication interfaces
B. A system organized as small cooperating services
C. A system designed without business features
D. A system stored in a single source file

10 Which deployment approach is typical in microservices architecture?

Microservices Architecture Easy
A. Deploy without testing any service
B. Deploy only after replacing all databases
C. Deploy services independently when needed
D. Deploy every service as one package

11 What does fault isolation mean in a microservices system?

Microservices Architecture Easy
A. A failure can remain limited to one service
B. Failures are hidden from all monitoring tools
C. Every failure stops the entire system
D. Each service removes its own error records

12 Which organizational approach commonly supports microservices?

Microservices Architecture Easy
A. Small teams own individual services
B. One team controls every minor task
C. No team maintains deployed services
D. External users manage internal code

13 In domain-driven design, what does the term domain refer to?

Domain-driven design (DDD) principles Easy
A. The network's physical location
B. The application's color scheme
C. The server's operating system
D. The business area being modeled

14 What is a bounded context in domain-driven design?

Domain-driven design (DDD) principles Easy
A. A boundary where a model has a specific meaning
B. A firewall rule for blocking service traffic
C. A limit on the number of application users
D. A storage quota assigned to a database

15 What is the purpose of a ubiquitous language in DDD?

Domain-driven design (DDD) principles Easy
A. To encrypt communication between services
B. To select one programming language
C. To translate every user interface
D. To create a shared domain vocabulary

16 Who should help develop the domain model in DDD?

Domain-driven design (DDD) principles Easy
A. Hardware vendors and auditors
B. Only network administrators
C. Developers and domain experts
D. Only application customers

17 What does a service boundary define?

Service boundaries Easy
A. The responsibilities owned by a service
B. The number of users in a company
C. The physical size of a server
D. The screen resolution of an application

18 Which quality indicates a well-defined service boundary?

Service boundaries Easy
A. Frequent changes across every service
B. High cohesion and loose coupling
C. Low cohesion and tight coupling
D. Shared ownership and repeated logic

19 What is the main role of an API gateway?

API gateway Easy
A. To compile source code for each service
B. To design user interfaces for mobile devices
C. To replace every database in the system
D. To provide an entry point for client requests

20 Which task is commonly performed by an API gateway?

API gateway Easy
A. Installing hardware in a data center
B. Writing all business rules for services
C. Routing requests to suitable services
D. Replacing the application's source control

21 A team modifies the payment logic inside a tightly coupled monolithic application. What is the most likely deployment consequence?

Application Architectures—Monolithic and Distributed Medium
A. Deploy and retest the entire application
B. Restart only the payment database
C. Replace the monolith with several independently managed serverless platforms
D. Deploy only the payment process

22 An order service calls an inventory service that is temporarily unavailable. Which approach best addresses this distributed-system failure?

Application Architectures—Monolithic and Distributed Medium
A. Move both services into one database
B. Increase the inventory table size
C. Retry every request indefinitely until the inventory service responds successfully
D. Use a circuit breaker with a fallback

23 Two services must always be released together because they directly depend on each other's internal classes. Which microservice property is most clearly being violated?

Microservice Fundamentals Medium
A. Geographic distribution
B. Automated monitoring
C. Independent deployability
D. Horizontal scalability

24 Why is assigning each microservice ownership of its own data generally preferred?

Microservice Fundamentals Medium
A. It eliminates all data duplication
B. It allows every service to modify all stored records through one shared administrative interface
C. It guarantees immediate consistency
D. It reduces coupling through shared schemas

25 A product page synchronously calls pricing, inventory, reviews, and recommendation services. One slow dependency frequently delays the whole page. Which improvement is most appropriate?

Microservices Architecture Medium
A. Use one shared database transaction
B. Apply timeouts and circuit breakers
C. Allow each dependency to wait without a deadline so that no response is lost
D. Remove all service monitoring

26 An order service publishes an OrderCreated event, and the inventory service processes it asynchronously. Which consequence should the design handle?

Microservices Architecture Medium
A. Automatic schema unification
B. Temporary eventual consistency
C. Guaranteed global transactions
D. Permanent request blocking

27 In a retail platform, the term Product means an item for sale in Catalog but a stored unit in Inventory. How should DDD represent these meanings?

Domain-driven design (DDD) principles Medium
A. Store them only in the API gateway
B. Replace both concepts with a single database row used directly by every service
C. Place them in separate bounded contexts
D. Force them into one shared model

28 Developers and business experts use different names for the same shipping concepts, causing recurring misunderstandings. Which DDD practice best addresses this problem?

Domain-driven design (DDD) principles Medium
A. Establish a ubiquitous language
B. Create a shared infrastructure database
C. Document every technical class while allowing domain terminology to remain inconsistent
D. Increase the number of deployment stages

29 A purchase order must ensure that its total always equals the sum of its line items whenever it is updated. Which DDD concept should define this consistency boundary?

Domain-driven design (DDD) principles Medium
A. Deployment pipeline
B. Aggregate
C. Value stream
D. API route

30 A new billing service must integrate with a legacy system whose data model uses incompatible terminology. Which DDD pattern best protects the new domain model?

Domain-driven design (DDD) principles Medium
A. Direct table access
B. Database replication
C. Shared kernel
D. Anti-corruption layer

31 Customer profile and loyalty rules change for different business reasons and are managed by different teams. What is the best boundary decision?

Service boundaries Medium
A. Combine them by customer identifier
B. Separate them into distinct services
C. Create one service containing every customer-related capability and all supporting databases
D. Place both inside the gateway

32 Several services directly update the same database tables. What is the main architectural risk?

Service boundaries Medium
A. Schema changes tightly couple services
B. Network latency becomes impossible
C. Each service gains complete deployment independence through coordinated schema ownership
D. Authentication is automatically disabled

33 A single CommerceService handles catalog, pricing, orders, payments, and shipping, and unrelated changes frequently conflict. Which criterion is most useful when splitting it?

Service boundaries Medium
A. Length of source file names
B. A separate service for every class regardless of domain cohesion or operational cost
C. Number of database columns
D. Business capabilities and change patterns

34 After decomposition, retrieving one customer page requires dozens of synchronous service calls for tiny pieces of data. What does this most likely indicate?

Service boundaries Medium
A. Every service must be moved into a different cloud region before boundaries can be evaluated
B. The gateway lacks encryption
C. The monolith is still deployed
D. The boundaries are too fine-grained

35 Mobile clients currently call eight internal services and must know each service location. What is the primary benefit of introducing an API gateway?

API gateway Medium
A. It converts all independently deployed services into one executable application at runtime
B. It provides one client-facing entry point
C. It removes every internal service failure
D. It guarantees distributed transaction consistency

36 A team wants consistent authentication, request routing, and rate limiting for public APIs. Where should these cross-cutting concerns primarily be implemented?

API gateway Medium
A. In a shared table modified by all clients
B. Inside every database
C. At the API gateway
D. Within domain entities

37 A gateway contains pricing rules, discount calculations, and order approval logic. What is the best architectural improvement?

API gateway Medium
A. Require clients to duplicate every pricing and approval rule before sending requests
B. Store all service data in the gateway
C. Add more domain rules to the gateway
D. Move domain logic into owning services

38 Web and mobile clients require substantially different response shapes for the same platform capabilities. Which gateway-related approach is most suitable?

API gateway Medium
A. Force one identical response format
B. Expose every database directly
C. Use a backend for each frontend
D. Combine all platform services into a monolith solely to avoid client-specific response composition

39 A payment, order, and inventory workflow spans separate services without a shared transaction manager. Which pattern is most appropriate for coordinating the workflow?

Microservices Architecture Medium
A. Shared writable service tables
B. A permanent lock held across every service until all network calls eventually complete
C. Saga with compensating actions
D. Single local database transaction

40 A user request passes through a gateway and four services, but logs cannot be connected across components. Which addition would most improve diagnosis?

Microservices Architecture Medium
A. Disable asynchronous communication
B. Write all logs only to local files and inspect each machine manually after an incident
C. Propagate a correlation identifier
D. Use different timestamps per service

41 A tightly coupled monolith has modules that share tables, internal classes, and transaction boundaries. The organization wants to migrate incrementally to microservices while minimizing distributed-system risk. What should be done first?

Application Architectures—Monolithic and Distributed Hard
A. Deploy every existing module independently while retaining all current synchronous calls
B. Restructure the monolith around explicit business boundaries and controlled module interfaces
C. Introduce a message broker and convert every in-process method invocation into an event
D. Extract the highest-traffic module and let it continue accessing the monolith's database

42 A request succeeds only if four independently failing synchronous services are available. Each service has availability , and network failure is ignored. What is the approximate end-to-end availability?

Application Architectures—Monolithic and Distributed Hard
A.
B.
C.
D.

43 Two independently deployed services directly update different columns of the same database table. Schema changes require coordinated releases, although each service has a separate code repository. Which microservice property is most directly violated?

Microservice Fundamentals Hard
A. Independent deployability through encapsulated data ownership
B. Location transparency through service discovery
C. Fault detection through centralized health monitoring
D. Horizontal scalability through stateless request processing

44 An Order service must save an order and publish an OrderCreated event. A crash between the database commit and broker publication currently causes lost events. Which design best closes this failure window without a distributed transaction?

Microservices Architecture Hard
A. Have the API gateway publish the event after receiving a successful HTTP response
B. Publish the event first and roll back the broker if the database commit fails
C. Store the event in an outbox within the order transaction and relay it asynchronously
D. Retry the entire client request until both the database and broker acknowledge success

45 In Sales, Customer means a prospect or buyer with pricing terms. In Support, Customer means a party associated with cases and service-level agreements. Which DDD treatment is most appropriate?

Domain-driven design (DDD) principles Hard
A. Use separate Customer models in distinct bounded contexts with an explicit translation
B. Rename both models until they share an identical ubiquitous language across the company
C. Place both models in one shared kernel so either team may modify their common semantics
D. Create one enterprise-wide Customer aggregate containing fields required by both teams

46 A business rule states that the total allocation across all lines of a Budget must never exceed its approved amount at commit time. Which aggregate design most strongly preserves this invariant?

Domain-driven design (DDD) principles Hard
A. Make every allocation line an aggregate root and reconcile totals once per day
B. Publish allocation events from separate line services and assume consumers receive them in order
C. Make Budget the aggregate root and update its allocation lines through that root
D. Store the approved amount in the API gateway and reject excessive incoming requests

47 Inventory and Pricing are maintained by different teams and change for different business reasons. Checkout synchronously invokes both services many times while constructing one cart response, causing latency and release coordination. Which redesign best addresses the boundary problem without merging unrelated domains?

Service boundaries Hard
A. Add more granular endpoints to both services so Checkout can retrieve each individual field independently
B. Expose each database directly so Checkout can join current records in one query
C. Give Checkout read-oriented projections populated from Inventory and Pricing events
D. Move Inventory and Pricing into one service because Checkout calls them together

48 A proposed service contains operations that always change together, share one strict invariant, and are owned by the same team. Splitting those operations would require a saga for nearly every command. What is the strongest architectural conclusion?

Service boundaries Hard
A. They should be coordinated by the API gateway as one distributed transaction
B. They must be separated to maximize independent scaling
C. They likely belong inside one service boundary
D. They should share a database while remaining separate services

49 A gateway authenticates users, applies quotas, routes requests, and also decides whether an order qualifies for a domain-specific refund. What is the best correction?

API gateway Hard
A. Keep all behavior in the gateway because centralized logic always reduces service coupling
B. Keep authentication and routing in the gateway, but move refund policy to the owning domain service
C. Move refund policy into a shared database trigger that the gateway invokes before forwarding the request
D. Move authentication, quotas, routing, and refund policy into every backend service independently

50 A gateway times out after two seconds and retries POST /payments once. The first attempt may complete after the timeout, creating duplicate charges. Which control provides the strongest end-to-end protection?

API gateway Hard
A. Use sticky sessions so both attempts reach the same in-memory payment handler
B. Increase the gateway timeout so every payment finishes before any retry occurs
C. Attach an idempotency key and persist its result atomically in the Payment service
D. Configure the gateway to retry only against a different Payment service instance

51 A checkout saga reserves inventory, authorizes payment, and requests shipment. Shipment creation fails after payment authorization. Payment authorization can be voided, but the inventory reservation may already have expired. What should the saga do?

Microservices Architecture Hard
A. Execute defined compensations while treating already-expired inventory release as idempotently satisfied
B. Repeat shipment creation forever because compensation would violate atomicity
C. Delete the order immediately and rely on nightly reconciliation to reverse every external effect
D. Roll back all service databases through the original transaction coordinator

52 An event consumer updates its database and then crashes before acknowledging the message. The broker redelivers the event. Which assumption should the consumer design make?

Microservices Architecture Hard
A. Delivery is effectively at-most-once because the database update already committed
B. Exactly-once business effects follow automatically from persistent broker acknowledgements
C. Duplicate delivery is possible, so processing must be idempotent or deduplicated
D. The broker will inspect the consumer database and suppress the second delivery

53 A legacy billing model is inconsistent with a new Subscription bounded context. Reusing legacy billing objects directly would force legacy terminology and rules into the new model. Which DDD pattern best isolates the new context?

Domain-driven design (DDD) principles Hard
A. Conformist relationship
B. Open-host service
C. Shared kernel
D. Anti-corruption layer

54 A downstream context has no influence over an upstream vendor model and chooses to adopt that model exactly rather than maintain translation logic. Which DDD context-map relationship does this describe?

Domain-driven design (DDD) principles Hard
A. Shared kernel
B. Customer-supplier
C. Conformist
D. Partnership

55 A team proposes one microservice per database entity: Customer, Address, PhoneNumber, and EmailPreference. Most use cases require coordinated calls to all four, and they are released by one team. Which signal most strongly indicates poor boundaries?

Service boundaries Hard
A. Most business changes require coordinated modifications across all four services
B. The entities have different table schemas and different primary-key formats
C. Each service has a separate deployment descriptor
D. Some services use smaller compute instances than the others

56 Service A needs a small subset of Service B's data to validate commands even when B is temporarily unavailable. Slightly stale validation data is acceptable, but A must not write B's records. Which design best preserves ownership and resilience?

Service boundaries Hard
A. Replicate the required data into A through published integration events
B. Let A read B's database through a read-only account
C. Move B's validation tables into a schema jointly owned by both services
D. Require A to synchronously call B for every validation and disable commands whenever that call fails

57 A single gateway instance handles all external traffic and stores rate-limit counters and sessions only in local memory. Which change most directly removes both the availability bottleneck and state-related scaling constraint?

API gateway Hard
A. Move all gateway state into the largest backend database and route every request through its primary node
B. Create one gateway per backend service while preserving local session state in each gateway
C. Increase the gateway instance size and configure the operating system to queue more incoming connections
D. Deploy multiple stateless gateway instances and externalize shared state to resilient stores

58 After validating a user token, a gateway forwards an unsigned X-User-Role header to internal services. Some services are also reachable through an internal network path that bypasses the gateway. What is the primary security flaw?

API gateway Hard
A. Backend services trust identity claims that callers can forge when bypassing the gateway
B. Internal services perform authorization even though the gateway has already authenticated the user
C. The gateway uses role information instead of placing all permissions in URL paths
D. The gateway validates authentication before rather than after applying rate limits

59 During a strangler migration, /accounts requests are routed to a new service, but both the monolith and the service can update account balances. Reconciliation repeatedly finds divergent balances. What is the most important corrective action?

Application Architectures—Monolithic and Distributed Hard
A. Have the gateway update both systems synchronously and return success when either update completes
B. Establish one authoritative writer and route all balance-changing commands through it
C. Allow both systems to write but select whichever balance has the latest timestamp
D. Increase reconciliation frequency until divergence becomes too brief for clients to observe

60 A distributed request crosses six services using asynchronous messaging and background workers. Logs contain timestamps but cannot reliably connect work performed after queue delivery to the original request. Which observability mechanism best addresses this?

Microservice Fundamentals Hard
A. Increase log verbosity at the API gateway because every distributed operation begins at the edge
B. Propagate trace context through HTTP headers and message metadata across every processing hop
C. Assign one permanent correlation identifier to each service instance and include it in every log
D. Synchronize all service clocks more frequently and sort centralized logs strictly by timestamp