Which statement best describes MuleSoft's view of integration solution architectures vs enterprise architectures?

• A. Integration solutions architecture focuses only on ETL; Enterprise architecture eliminates API-Led connectivity.
• B. Integration solutions architecture is irrelevant; Enterprise architecture is the same as IT infrastructure.
• C. Integration solutions architecture requires no layering; Enterprise architecture uses monolithic APIs.
• D. Integration solutions architecture documents individual integration initiatives; Enterprise architecture is an application network using API-Led connectivity with layering and reuse.

Answer: (B)

The idea being tested is how MuleSoft distinguishes practical integration work from the broader enterprise architecture, emphasizing API-led connectivity, layering, and reuse. In MuleSoft’s view, integration solutions architecture focuses on the concrete work of connecting individual systems and apps—documenting the specific initiatives and the patterns used to make those connections. Enterprise architecture, on the other hand, envisions an overarching application network that uses API-led connectivity to enable scalable, reusable integration across the organization. This network is organized with layering: System APIs that encapsulate underlying systems, Process APIs that orchestrate data flows, and Experience APIs that tailor data for specific applications. Reuse and governance across these APIs are key to achieving a scalable, maintainable architecture.

The other descriptions don’t fit this approach. They either imply ETL-only thinking or equate enterprise architecture with IT infrastructure, or suggest no layering and monolithic APIs. These ideas conflict with API-led connectivity and the layered, reusable network MuleSoft promotes. The description that best matches MuleSoft’s view is that integration solutions architecture documents individual integration initiatives while enterprise architecture is an application network using API-led connectivity with layering and reuse.