For IndividualsFor Educators
ExpertMinds LogoExpertMinds
ExpertMinds

Ace your certifications with Practice Exams and AI assistance.

  • Browse Exams
  • For Educators
  • Blog
  • Privacy Policy
  • Terms of Service
  • Cookie Policy
  • Support
  • AWS SAA Exam Prep
  • PMI PMP Exam Prep
  • CPA Exam Prep
  • GCP PCA Exam Prep

© 2026 TinyHive Labs. Company number 16262776.

    PracticeAzure Solutions Architect Expert (AZ-305)Azure Solutions Architect Expert AZ-305 Practice Exam 4Question 47
    Hard1 markMultiple Choice
    Domain 4.2: Design an Application ArchitectureArchitectureMicroservicesDesign Patterns

    AZ-305 · Question 47 · Domain 4.2: Design an Application Architecture

    You are designing a microservices architecture for a high-traffic ticketing system.

    During ticket sales events, the system experiences massive spikes in 'write' operations (users buying tickets). The 'read' operations (users viewing available seats) are also high but require different scaling and performance characteristics. You need to design an architecture that scales the read and write workloads independently.

    Which architectural pattern should you recommend?

    Answer options:

    A.

    Saga Pattern

    B.

    Command and Query Responsibility Segregation (CQRS)

    C.

    Circuit Breaker Pattern

    D.

    Strangler Fig Pattern

    How to approach this question

    Keywords: 'scales the read and write workloads independently'. This is the exact definition of CQRS.

    Full Answer

    B.Command and Query Responsibility Segregation (CQRS)✓ Correct
    Command and Query Responsibility Segregation (CQRS)
    The Command and Query Responsibility Segregation (CQRS) pattern separates read and update operations for a data store. Implementing CQRS in your application can maximize its performance, scalability, and security. It allows the read workload (viewing seats) to scale independently from the write workload (buying tickets), often using different database technologies for each.

    Common mistakes

    Choosing Saga. While Saga is common in microservices, it solves the problem of distributed transactions, not read/write scaling.
    Question 46All questionsQuestion 48

    Practice the full Azure Solutions Architect Expert AZ-305 Practice Exam 4

    55 questions · hints · full answers · grading

    Sign up freeTake the exam

    More questions from this exam

    Q01CASE STUDY: Tailspin Toys Tailspin Toys is a global manufacturing company with 50,000 employees ...MediumQ02CASE STUDY: Tailspin Toys Tailspin Toys is a global manufacturing company with 50,000 employees ...MediumQ03CASE STUDY: Tailspin Toys Tailspin Toys is a global manufacturing company with 50,000 employees ...HardQ04CASE STUDY: Tailspin Toys Tailspin Toys is a global manufacturing company with 50,000 employees ...MediumQ05CASE STUDY: Tailspin Toys Tailspin Toys is a global manufacturing company with 50,000 employees ...Hard
    View all 55 questions →