MuleSoft Certified Integration Architect – Level 1 Exam

Demonstrate your ability to be responsible for Anypoint integration interfaces and implementations with the MuleSoft Certified Integration Architect – Level 1 exam.

About

MuleSoft Certified Integration Architect Exam

Showcase your MuleSoft integration skills with the MuleSoft Certified Integration Architect – Level 1 exam, around 10 percent of which is specific to Mule 4.

This exam tests your ability to drive and be responsible for Anypoint Platform implementations and the technical quality, governance, and operationalisation of the integration solutions.

As a MuleSoft Certified Integration Architect, you will have the knowledge and skills to work with technical and non-technical stakeholders to translate functional and non-functional requirements into integration interfaces and implementations.

Approach

Certification Objectives

Take the MuleSoft Certified Integration Architect – Level 1 exam to show your knowledge of:

  • creating the high-level design of integration solutions and guide implementation teams on the choice of Mule Components and patterns to use in the detailed design and implementation
  • selecting the deployment approach and configuration of the Anypoint Platform with any of the available deployment options (MuleSoft-hosted or customer-hosted control plane and runtime plane)
  • designing Mule applications for any of the available deployment options of the Anypoint Platform runtime plane
  • applying standard development methods covering the full development lifecycle (project preparation, analysis, design, development, testing, deployment, and support) to ensure solution quality
  • advising technical teams on performance, scalability, reliability, monitoring and other operational concerns of integration solutions on Anypoint Platform
  • designing reusable assets, components, standards, frameworks, and processes to support and facilitate API and integration projects

MuleSoft Certified Integration Architect – Level 1 Exam: Format

  • format: multiple-choice, closed book, proctored online or in a testing centre
  • length: 58 questions
  • duration: 120 minutes (two hours)
  • pass score: 70 percent
  • language: English
  • the MuleSoft Certified Integration Architect – Level 1 exam can be taken a maximum of five times, with a 24-hour wait between each attempt

Delivery Methods

You can choose to take the MuleSoft Certified Integration Architect – Level 1 exam in-person at a testing centre or online using a web camera, administered via the Kryterion Webassessor testing platform.

If you choose in-person at a Kryterion Testing Centre:

  • over 1000 locations worldwide
  • onsite instructions
  • a test-taker guide

If you choose online using the Kryterion Webassessor testing platform:

  • requires a webcam – a laptop webcam can be used, an external camera is not required
  • requires internet connectivity with 1 Mbps upload, 1 Mbps download, jitter <50ms, ping <200ms
  • use the tool to determine your internet speed and reliability
  • online instructions
  • a test-taker guide

If you think your connection might be unreliable, we recommend you choose a testing centre instead. An unreliable connection may cause you to be expelled from the exam.

Exam Preparation

  • MuleSoft Certified Integration Architect – Level 1 exam takers can best prepare by taking the instructor-led Anypoint Platform Architecture: Solution Design course
  • candidates should be familiar with all the course content and be able to apply it before taking the exam

Exam Topics

In the topics below, ARC:DES is the acronym for the Anypoint Platform Architecture: Solution Design course.

The MuleSoft Certified Integration Architect – Level 1 exam demonstrates proficiency in the following tasks:

Z

Configuring and Provisioning Anypoint Platform Resources

  • configure business groups, roles, and permissions within an Anypoint Platform organisation
  • 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 number of Mule runtimes 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
  • ARC:DES Module 6
  • ARC:DES Module 8
  • Anypoint Access Management
  • About Identity Management
  • About Client Management
  • CloudHub
  • Mule Runtime High Availability (HA) Cluster Overview
  • To Export Data to External Analytics
Z

Selecting Integration Styles

  • given a description of an integration problem, identify the most appropriate integration style
  • ARC:DES Module 4
  • ARC:DES Module 5
  • when designing an integration solution, select the most appropriate interface/data technology and interface definition language for all integration interfaces
  • About the JMS Connector
  • design parts of an integration solution using general message-based integration or event-driven architecture (EDA) using message brokers or streaming technologies
  • recognise scenarios where message correlation is necessary
Z

Designing and Documenting Enterprise Integration Architecture

  • for a given organisation 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 for which the use of batch would be beneficial
  • design for short or long retries using reconnection strategies
  • identify common and distinguishing features and usage scenarios for CloudHub DLBs and public CloudHub LBs
  • ARC:DES Module 3
  • ARC:DES Module 4
  • Deployment Strategies
  • Mule Object Stores
  • Managing Application Data Storage with Object Stores
  • Object Store Connector
  • Anypoint Object Store V2
  • About Batch Processors
  • Migration Reconnection Strategies
  • About Reconnection Strategies
  • About Load Balancers (CloudHub)
Z

Architecting Resilient and Performant Integration Solutions

  • recognise 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
  • recognise 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
  • ARC:DES Module 3
  • ARC:DES Module 5
  • ARC:DES Module 6
  • Transaction Management
  • XA Transactions
  • About Batch Processors
  • Database Connector
  • About the File Connector
  • About the FTPS Connector
  • CloudHub Fabric
  • Mule Runtime High Availability (HA) Cluster Overview
Z

Handling Events and Messages

  • 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-prem
  • 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 behaviour of messages sent to the public URL of a Mule application deployed to multiple CloudHub workers
  • ARC:DES Module 5
  • ARC:DES Module 6
  • Mule Object Stores
  • Managing Application Data Storage with Object Stores
  • Object Store Connector
  • Anypoint Object Store V2
  • About Mule Components
  • About Streaming
  • Anypoint Runtime Fabric
Z

Designing Applications with Anypoint Connectors

  • 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)
  • ARC:DES Module 3
  • ARC:DES Module 5
  • Connectors and Modules (for Mule 4)
  • Shared Resources
  • Mule Object Stores
  • Managing Application Data Storage with Object Stores
  • Object Store Connector
  • Anypoint Object Store V2
  • Let’s Talk About Resilience
Z

Designing Networks for Anypoint Connectors

  • for a given connector, recognise whether it will typically connect to/from an external system across organisational boundaries
  • use transport protocols and connectors correctly and coherently when and where applicable
  • match protocols with networking constraints and API layers
  • when incoming and outgoing HTTPS connections with mutual authentication are used, identify what certificates are needed in what stores in different environments
  • ARC:DES Module 6
  • ARC:DES Module 8
  • Connectors and Modules (for Mule 4)
  • About TLS
Z

Handling Integration Implementation Lifecycles

  • identify the Anypoint Platform components where various types of API-related assets and artefacts are maintained or published
  • recognise the advantages and disadvantages of storing and managing properties in properties files in Mule applications
  • for a given API or integration, identify the steps that need to be taken in order for testing to occur
  • ARC:DES Module 3
  • ARC:DES Module 5
  • Create and Publish an API Spec or API Fragment
  • Secure Configuration Properties
  • MUnit
Z

Implementing DevOps

  • specify the purpose of various MuleSoft products in the area of DevOps/CI/CD
  • identify differences, advantages, and disadvantages of DevOps based on deployable Mule applications versus container images
  • formulate an effective source code management strategy including branching and merging
  • specify testing strategies that use both mocking and invoking of external dependencies
  • ARC:DES Module 5
  • MUnit Maven Support
  • About the Mule Maven Plugin
  • Learn Kubernetes Basics
Z

Operating and Monitoring Integration Solutions

  • specify the type of metrics for API invocations and API implementations that can be monitored with Anypoint Platform
  • identify metrics and operations exposed by default via JMX
  • identify differences in monitoring and alerting between customer-hosted and MuleSoft-hosted Anypoint Platform
  • identify ways of transmitting IDs between components in remote interactions and capture this in the interface design of the remote interaction
  • Viewing API Analytics
  • JMX Management
  • To Export Data to External Analytics Tools (Hybrid)

About Influential Software

The Influential Software team has been delivering quality business software, services, and training for over 25 years. As a certified MuleSoft Partner, we are experts in data integration and the key technologies used in MuleSoft Anypoint Platform.

Our UK teams work on- and off-site for enterprises of all sizes, from FTSE 100/250 companies to SMEs. The result is hundreds of successful projects and long-term client partnerships.

find out more

* Required

By using this form you agree with the storage and handling of your data by this website.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Call Us

0203 507 1728

City of London Office

Floor 3, 8 Devonshire Square
London EC2M 4PL

Kent Office

Floor 2, Maidstone House
King Street, Maidstone
Kent ME15 6JQ

Hours

M-F: 9am - 5.30pm
S-S: Closed