CPSA Integration and Interfaces Questions and Answers Flashcards
6 cards from real CPSA practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 6 CPSA Integration and Interfaces Questions and Answers flashcards as text
In software architecture, what is the primary purpose of defining explicit interfaces between components?
Answer: To decouple components so they can evolve independently without breaking each other
Explicit interfaces create stable contracts between components, enabling independent evolution and reducing coupling.
What distinguishes synchronous integration from asynchronous integration between software components?
Answer: Synchronous integration requires the caller to wait for a response, while asynchronous integration allows the caller to continue processing
In synchronous integration the caller blocks until the response arrives; asynchronous integration decouples timing by using messages or callbacks.
Which integration style uses a central hub to route messages between multiple systems?
Answer: Message broker / hub-and-spoke integration
Hub-and-spoke integration centralizes routing logic in a broker, reducing the number of direct connections between systems.
What is 'interface bloat' and why is it considered an architectural problem?
Answer: Adding too many methods to an interface, making it harder to implement and increasing coupling
Interface bloat occurs when interfaces grow too large, violating the Interface Segregation Principle and increasing the burden on implementing components.
In enterprise integration patterns, what is a 'canonical data model'?
Answer: A shared data format that all integrated systems use to avoid point-to-point format translations
A canonical data model provides a common intermediate format, reducing the number of translators needed from N×(N-1) to 2×N in an N-system landscape.
What is the key architectural risk of 'shared database' integration between multiple systems?
Answer: It creates tight coupling at the data layer, making independent evolution and deployment of systems difficult
Shared database integration tightly couples systems through their data model, meaning a schema change in one system can break all others.