Broker Architecture Pattern Quiz V2

Q1. Which component in the Broker pattern resides on the **client** side and handles marshalling of requests?




Q2. What term describes the Broker pattern’s ability to let a client invoke a service without hard-coding its network address?




Q3. A company’s microservices call each other directly over HTTP. Engineers complain about duplicated auth code, brittle endpoints, and scaling headaches. **Which architectural pattern best addresses these issues?**




Q4. Which of the following is **NOT** a typical core component of a Broker-based RPC framework?




Q5. In gRPC, service contracts are defined in files with which extension?




Q6. What is the primary job of the Naming/Registry service?




Q7. Which mechanism below is **least** related to fault tolerance in a Broker setup?




Q8. Marking a Thrift method with the keyword **oneway** results in what kind of invocation?




Q9. Designing an API that requires dozens of tiny remote calls to finish a single business action exemplifies which anti-pattern?




Q10. Your API gateway has gradually accumulated message transformations, orchestration flows, and conditional business rules, becoming a single giant service. **Which anti-pattern does this illustrate?**




Q11. Which Broker responsibility directly enables distributing traffic across multiple healthy service instances?




Q12. Generating stubs and skeletons from an IDL primarily enables:




Q13. If a client should continue working while waiting for the server’s reply, which invocation model is appropriate?




Q14. Mutual TLS (mTLS) between sidecar proxies in a service mesh mainly provides:




Q15. In an Istio-style service mesh, which component pair acts as the distributed Broker?




Q16. Which observability technique shows the **end-to-end timeline** of a single request through multiple services?




Q17. Dynamic binding at runtime primarily depends on:




Q18. You deploy UserService v1 and v2 concurrently. The Broker routes 10 % of traffic to v2 based on request metadata. Which concept best describes this?




Q19. Which of these **is NOT** a common load-balancing algorithm in Broker/proxy implementations?




Q20. gRPC uses which underlying transport protocol by default?




Q21. A single, non-replicated Broker node mediates all traffic. What is the **largest architectural risk**?




Q22. NATS achieves request-reply RPC semantics by:




Q23. Adding an extra network hop through a Broker inevitably introduces:




Q24. Which statement about a **circuit breaker** in a Broker or stub is true?




Q25. Where is **connection pooling** most commonly implemented in a Broker-based stack?




Q26. Centralizing **authentication and authorization** checks in the Broker provides:




Q27. Which technology pair exemplifies a Broker framework that relies on **Protocol Buffers over HTTP/2**?




Q28. Envoy’s overload manager can start shedding requests when resource limits are hit. This feature primarily provides:




Q29. Which of the following is **NOT** a typical registry technology for service discovery?




Q30. Apache Thrift natively supports several serialization formats. **Which format below is NOT one of them?**




software-architecture