MuleSoft Certified Integration Architect - Level 1 

Configure business groups, roles, and permissions within an Anypoint Platform organization

Select Anypoint Platform identity management vs client management for the correct purpose

Identify common and distinguishing features and usage scenarios for CloudHub VPCs and public worker cloud

Suggest the number of Mule runtimes needed for a Mule application given performance targets and HA requirements

Define a performant and HA deployment architecture for Mule applications in on-prem deployments

Select monitoring options for all available Anypoint Platform deployment options

Given a description of an integration problem, identify the most appropriate integration style

When designing an integration solution, select the most appropriate interface/data technology and interface definition language for all integration interfaces

Design parts of an integration solution using general message-based integration or event-driven architecture (EDA) using message brokers or streaming technologies

Recognize scenarios where message correlation is necessary

For a given organization and their preferences and constraints, select the most appropriate Anypoint Platform deployment option

Design parts of an integration solution using any SOA-based integration approach

Identify the information that should be included in any integration solution architecture document

Simplify a large-scale enterprise-wide integration architecture so that it can be effectively communicated to semi-technical stakeholders

Identify the persistence mechanism and durability used for watermarks in different Mule runtime deployment options

Identify integrations scenarios when to use batch

Design for short or long retries using reconnection strategies

Identify common and distinguishing features and usage scenarios for CloudHub DLBs and public CloudHub LBs

Recognize requirements that are best addressed using transactions (single-resource and XA)

Define transaction considerations where needed in a solution design including the requirement for an external transaction coordinator

Specify the connectors that can participate in the different types of transactions

Recognize the purpose of various fault-tolerance strategies for remote calls

Design parts of an integration solution using general batch-oriented integration or ETL to/from files or databases

Determine if horizontal scaling will help a Mule application meet its performance targets

Identify scenarios in which to use different storage mechanisms including persistent and non-persistent ObjectStore, in-memory ObjectStore, cluster-replicated in-memory OS, hashtables, and disk-persisted OS

Select suitable storage mechanisms for IDs (correlation IDs, message IDs, transaction IDs) in Mule applications deployed to CloudHub or on-premises

Use Mule 4 constructs to make effective use of Enterprise Integration Patterns

Use streaming to handle large payloads within Mule applications

Predict the runtime behavior of messages queued internally for processing for load balancing or to achieve reliability

Predict the runtime load-balancing behavior of messages sent to the public URL of a Mule application deployed to multiple CloudHub workers

For a given Mule 4 connector (Premium, Select, and MuleSoft Certified), identify its purpose, the network protocol it uses, and whether it supports incoming or outgoing types of connections

Specify the requirements that would require the use of domain-level connectors

Specify when a Mule application would require persistence and select an appropriate persistence solution

Identify possible failures when a component (such as an API client) invokes a remote component (such as an API implementation)