Boomi Architect study plan

Map every Boomi integration component type (connector, shape, operation, map, process property) to the integration lifecycle stage it serves

Trace a single-record process end to end and annotate where document flow, branching, and error handling occur

Configure process properties, dynamic process properties, and document caching to pass state between shapes

Distinguish when to use a sub-process versus a process call versus a low-latency listener

Design retry, try/catch, and exception-path handling for a process that writes to an external system

Compare listener patterns (web services, database, trading partner, mail) on throughput, ordering, and failure recovery

Build a decision table that selects the right connector operation (GET, QUERY, CREATE, UPDATE, UPSERT) for common sync scenarios

Explain how Boomi atom queues, scheduling, and process-level concurrency settings affect message ordering

Publish a REST API component from an existing process and define its resource paths and operations

Apply authentication policies (basic, OAuth 2.0, API key) and justify the choice for a given consumer profile

Configure API gateway policies for rate limiting, request size, and response caching

Differentiate API management from API gateway responsibilities in the Boomi platform

Design an API versioning and deprecation strategy that avoids breaking existing consumers

Write an OpenAPI-style contract for one API and validate that the implemented resources match it

Plan environment promotion (test to production) for API components and their dependent processes

Identify how API gateway logs and metrics support troubleshooting and capacity decisions

Build a JSON-to-XML profile pair and a map that handles arrays, conditionals, and default values

Apply data process shapes (combine, split, flatten, deduplicate, sort, batch) to reshape a dataset

Design a document cache and cross-reference lookup strategy for enriching records during processing

Explain how Boomi handles document tracking, persistence, and archival for audit purposes

Model a master data pattern using cross-reference tables and a deduplication rule set

Describe how Boomi's AI features consume integration data and what data governance controls apply

Identify the data preparation steps (cleaning, normalization, schema alignment) required before data feeds an AI service

Evaluate data residency, retention, and privacy constraints for a pipeline that sends records to an external AI endpoint

Configure an integration process that calls an LLM or AI service and handles latency, token limits, and error responses

Design prompt and payload templates that keep structured data out of free-text fields where possible

Explain what an agent needs from an integration layer: tools, actions, state, and guardrails

Draft a tool schema an agent could invoke to trigger a Boomi process, including input validation and failure responses

Design an agentic workflow that chains two or more Boomi-exposed tools with a human approval checkpoint

Define observability for agent-driven processes: logging, tracing, and audit of autonomous actions

Review all five domains and close gaps using a self-scored checklist against the exam outline

Practice explaining architecture trade-offs aloud for each domain in under two minutes