| Topic | Details |
| Topic 1 | - Recognize common integration problems, use cases, and technical solutions: This section of the exam measures the skills of an Integration Architect and focuses on recognizing integration scenarios and choosing appropriate technologies. It distinguishes between enterprise system types and compares traditional versus modern integration approaches. Candidates are expected to deconstruct complex business problems into core use cases and identify suitable technologies to support them. A solid understanding of technology classes and their application in business scenarios is tested, along with knowledge of how to break down an integration solution into its system components.
|
| Topic 2 | - Recognize and interpret essential integration concepts and terminology: This section evaluates the competency of a Platform Specialist and covers fundamental terms and technical knowledge essential for integration. It includes differentiating cloud service models such as IaaS, PaaS, and SaaS, and the supporting infrastructure such as computing, storage, and scalability principles. The domain further explores network protocols, data formats like XML and JSON, and security concepts in API and enterprise systems. A detailed understanding of HTTP mechanics, RESTful services, and classifications of API types such as GraphQL and AsyncAPI is expected. It also introduces precise terminology necessary for defining API roles and interactions.
|
| Topic 3 | - Explain the common technical complexities and patterns in integration development: This section tests the expertise of a Platform Specialist and explores various technical patterns and complexities found in integration development. It includes a comparative review of interaction patterns such as batch, stream, and multicast, as well as integration composition styles like orchestration and choreography. The section emphasizes the use of design-first API development, observability practices, and log management. It also introduces architecture concepts such as microservices versus monolithic deployment, hybrid and cloud infrastructure, and the roles of API gateways and service meshes.
|