MuleSoft Certified Platform Architect – Level 1

Certification Exam

Summary
A MuleSoft Certified Platform Architect – Level 1 should be able to define and be responsible for an
organization’s Anypoint Platform strategy. The MCPA – Level 1 exam validates that an architect has
the required knowledge and skills to direct the emergence of an effective application network out of
individual integration solutions following API-led connectivity across an organization using Anypoint
Platform. Certified candidates should be able to:

 Optimize and shape the Anypoint Platform deployment in the specific organizational context —
working with business, infrastructure, InfoSec, and other teams.
 Define how Anypoint Platform is used in conjunction with other tools and applications in the
organization.
 Define the usage of Anypoint Platform and the corresponding organizational and process
changes needed to help the platform be sustainable.
 Provide guidance and drive the creation of standards, reusable assets, and automation required
for scale and multi-LoB adoption.

Format
 Format: Multiple-choice, closed book, proctored
 Length: 60 questions
 Duration: 120 minutes (2 hours)
 Pass score: 70%
 Language: English
You can take the exam a maximum of 5 times, with a 24-hour wait between each attempt.

Cost
You can purchase the exam with one of the following. Each includes one free retake.

 $375
 1.5 MuleSoft Training Credits (MTC)
Additional retakes (i.e. attempts 3 to 5) are $250 or 1 MTC and do not come with a free retake.

Two free exam attempts are also included with the purchase of the instructor-led Anypoint Platform
Architecture: Application Networks course.
Validity
The certification expires two years from the date you pass the exam. To extend the certification validity
after this date, you can take the MuleSoft Certified Platform Architect – Level 1 MAINTENANCE exam.

Preparation
You can best prepare for the exam by taking the instructor-led Anypoint Platform Architecture:
Application Networks course. Candidates should be familiar with all of the content in the course and be
able to apply the concepts.

The following resources are available to help you prepare:

 Instructor-led training: Anypoint Platform Architecture: Application Networks

o Recommended as the most effective and efficient method of preparation
o 3-day class
o Private, public, onsite, and online classes available
o Includes two free attempts for this exam
 Practice exam
o Same format, length, and duration as the certification exam
o Questions are the same style and degree of difficulty as the exam

Topics
The exam validates that you can perform the following tasks.
Note: ARC: NET is the acronym for the Anypoint Platform Architecture: Application Networks course.

Explaining application network basics Resources

 Identify and differentiate between technologies typically used  ARC: NET Module 1
to implement API-led connectivity.
 ARC: NET Module 2
 Describe the role and characteristics of web APIs.
 What is API-led Connectivity?
 Correctly assign APIs to tiers according to ownership,
 What is Full Lifecycle API
functional focus, and rate of change.
Management?
 Describe the capabilities and high-level components of
 Anypoint Monitoring Overview
Anypoint Platform.

Establishing organizational and platform foundations

 Advise on establishing a Center for Enablement (C4E) and  ARC: NET Module 1
identify KPIs to measure its success.
 ARC: NET Module 3
 Describe the high-level structure and benefits of MuleSoft
 Catalyst
Catalyst.
 Choose between options for hosting and managing Anypoint  Accelerating innovation
Platform control and runtime planes. through a new API operating
model
 Compare and contrast Identity Management and Client
Management options on Anypoint Platform.  Introduction to Catalyst
 Identify data residency of different kinds of data (e.g.  MuleSoft C4E Overview
payload, metrics, and others) Webinar - Part 1
 Tokenization

Designing and sharing APIs

 Identify dependencies between an API, its API specification,  ARC: NET Module 1
its implementation, and its clients.
 ARC: NET Module 4
 Identify changes to an API that would require or not require
 ARC: NET Module 6
changing the major/minor/patch component of its semantic
version.  Rest Connect Connector
Generation
 Given a specific power relationship between two Bounded
Contexts, choose the most appropriate strategy for mapping  Common API Mistakes
between the API data models of these Bounded Contexts.  What are idempotent and/or
 Identify idempotent HTTP methods and HTTP-native support safe methods?
for optimistic concurrency.
 Recognize the important features and functionality of API
designer to design API specifications.

Designing APIs using system, process, and experience

layers

 Identify appropriate web APIs to implement a business  ARC: NET Module 4

process and assign them to layers of API-led connectivity.
 ARC: NET Module 6
 Assign APIs to layers according to ownership, functional
 API-led Connectivity
focus, and rate of change.
 Recommend the most appropriate approach relating the API
data model of System APIs to that of their backend system
based on specific requirements and organizational
characteristics.

Governing web APIs on Anypoint Platform

 Make appropriate use of API instances and environments in  ARC: NET Module 3
API manager taking into account the nature of the API and
 ARC: NET Module 5
the underlying data and system.
 Create an API Instance
 Select appropriate API policies and other components of the
AP to support specific non-functional requirements (NFRs).  JSON Threat Protection
 Identify any change(s) required to an API specification to  Client ID Enforcement Policy
reflect the application of an API policy with specific  Configuring API Specifications
characteristics.
 Message Logging
 Select an approach to API policy enforcement based on
specific preferences and constraints, including, but not  Policies
 limited to, API proxies/API gateways and Anypoint Service  About Identity Management
Mesh.
 Secure web APIs using API policies appropriately chosen for
the API's tier (System, Process, Experience).
 Describe in what circumstances and how to pass client ID
and secret to a web API.
 Explain how to request access to an API version for an API
client, and how that access is approved and revoked.
 Select appropriate API policies to enforce non-functional
security constraints on web API invocations.
 Explain the relationships of Anypoint Platform, external
Identity Providers, AP Business Groups, and API clients in
the context of OAuth 2.0.
 Identify scenarios needing custom API policies.

Architecting & deploying API implementations

 Explain how to use auto-discovery to link a web API  ARC: NET Module 3
implementation to an API instance managed with API
 ARC: NET Module 7
Manager.
 ARC: NET Module 9
 Identify requirements that call for the use of an Anypoint
VPC.  Dedicated Load Balancer
Architecture
 Compare and contrast options for hosting and managing
Anypoint Platform runtime planes.  Configuring Public and Private
Mule Applications Behind DLB
 Compare unit and integration tests and specify where MUnit
is best employed.  Build an HTTP Service
 Explain options for automated build, test, and deploy of API  VPC Firewall Rules
implementations and related artifacts in a DevOps setting.  Command Line Tools
 Deploy On Premises
 Getting started with MuleSoft
Platform APIs and Postman
automation
 Deploy Mule Applications
 Mule Maven Plugin

Deploying API implementations to CloudHub

 Describe the scenarios for which the Object Store should be  ARC: NET Module 7
used with CloudHub.
 About Object Store v2
 Select CloudHub worker sizes and configuration as
 Autoscaling in CloudHub
appropriate.
 CloudHub High Availability
 Given an app deployed to the CloudHub shared worker
cloud in one or more regions, describe and predict its  Dedicated Load Balancers
reliability and performance characteristics.
  Identify the defining differences between the CloudHub  Transit Gateway Attachments
Shared and Dedicated Load Balancers.
 Provision a VPC
 Compare and contrast the options for CloudHub networking
 How to choose the CIDR
in the presence of customer-owned Amazon VPCs and on-
block for your VPC
premises data centers.
 Identify and avoid single points of failure in CloudHub
deployments of API implementations.

Meeting API quality goals

 Design, describe, and differentiate between scenarios that  ARC: NET Module 6
use the Object Store or caching.
 ARC: NET Module 7
 Select resilience strategies that help web API clients guard
 ARC: NET Module 9
against failures when invoking APIs.
 Cache Scope and Object
 Describe when horizontal scaling of an API implantation is or
Store in Mule 4
is not likely to benefit response time and throughput as seen
by API clients.  Effectively Using Caching
While Developing APIs in
Mule: Part 1
 Cache Scope
 Horizontal Scaling vs Vertical
Scaling of Mule Workers
 Reasons to Scale Horizontally

Monitoring and analyzing application networks

 Identify the components of Anypoint Platform that generate  ARC: NET Module 10
data for monitoring and alerting.
 Configure and Enable
 Describe the metrics collected by Anypoint Platform for API Anypoint Monitoring for Mule
invocations. Apps (CloudHub)
 Specify alerts to define for key metrics of API invocations for  Log Tokenization
all layers of API-led connectivity.
 API Functional Monitoring in
 Specify alerts to define for Mule applications. Anypoint Monitoring
 Custom Application Alerts

More information
For more information, visit http://help.learn.mulesoft.com.