EIP study plan

Diagram the layered enterprise architecture stack (business, application, data, technology) and place each integration component on the correct layer.

Compare request-response, event-driven publish-subscribe, file/batch transfer, and shared-database integration styles, then select one style for three stated business scenarios and justify each choice in writing.

Define at least 15 core integration terms - ESB, API gateway, canonical message model, orchestration versus choreography, idempotency, service registry - and pair each with a concrete usage example.

Trace one end-to-end business transaction across five systems and annotate every handoff with its protocol, data contract, and failure mode.

Construct a canonical data model that reconciles two source systems and document field-level source-to-target mappings, including type and nullability differences.

Evaluate synchronous versus asynchronous messaging for a given flow and specify retry policy, idempotency keys, ordering guarantees, and dead-letter handling.

Compare normalized warehouse, lakehouse, and data-virtualization approaches against a stated latency, cost, and governance requirement set.

Assess a sample dataset against the six data-quality dimensions and record which defects would break downstream integration contracts.

Design a star schema for a defined reporting question, declaring the fact grain, at least three dimensions, and the slowly changing dimension handling for two of them.

Interpret ten SQL patterns covering multi-table joins, aggregation, window functions, and null handling, and predict each result set before verifying it.

Contrast batch, change-data-capture, and streaming ingestion on latency, cost, complexity, and recovery behavior, and recommend one per scenario.

Specify the governance artifacts for a data asset: catalog entry fields, lineage from source to report, steward ownership, and a retention and archival rule.

Distinguish authentication from authorization and trace how OAuth 2.0, OIDC, and SAML assertions are issued, validated, and propagated across an integration boundary.

Threat-model an API-mediated integration with STRIDE and list at least six threats, each paired with a preventive or detective control.

Map three data-classification tiers to concrete encryption, masking, key-management, and logging requirements.

Complete a 40-question mixed diagnostic across Domains 1 and 2 and convert every missed item into a dated remediation task.

Apply least-privilege and role-based versus attribute-based access control to three access scenarios and state the entitlement model each requires.

Translate regulatory and contractual obligations into implementable technical controls, separating what must be enforced in code from what is enforced by process.

Specify audit-log content, immutability, retention period, and non-repudiation evidence for a transaction-processing system.

Build a risk register that scores likelihood and impact, assigns an owner, and selects a treat, transfer, avoid, or accept response for each entry.

Compare waterfall, agile, and hybrid delivery models and select one for a regulated integration program, defending the choice against its main failure mode.

Draft a RACI matrix for a cross-functional release and identify the two handoffs most likely to stall.

Define the approval path for a production change, naming which body reviews architecture impact, which approves the schedule, and which accepts residual risk.

Establish requirements traceability from a business need through design, build, and test case, and demonstrate it for three requirements.

Design an environment promotion path from development through test to production and list the automated quality, security, and approval gates at each transition.

Explain infrastructure as code, configuration drift, and immutable infrastructure, and state which artifact type each practice governs.

Select IaaS, PaaS, SaaS, containers, or serverless for three workloads and justify each against operational burden, scaling profile, and portability.

Define SLI, SLO, SLA, and error budget for two services and compute the monthly error budget at a stated availability target.

Diagnose common operational failure modes - capacity exhaustion, autoscaling lag, backup gaps, alert fatigue - and prescribe a monitoring or control fix for each.

Select a disaster-recovery strategy for three scenarios by deriving recovery time and recovery point objectives from stated business impact.

Complete a timed 60-question full-length practice exam under test conditions and tag every incorrect answer to its domain and root cause.

Consolidate a two-page cheat sheet that allocates space across all five domains in proportion to their exam weighting, with Domain 1 receiving the largest share.