MuleSoft Certified Platform Architect - Level 1 

Identify and differentiate between technologies typically used to implement API-led connectivity

Describe the role and characteristics of web APIs

Correctly assign APIs to tiers according to ownership, functional focus, and rate of change

Describe the capabilities and high-level components of Anypoint Platform

Advise on establishing a Center for Enablement (C4E) and identify KPIs to measure its success

Describe the high-level structure and benefits of MuleSoft Catalyst

Compare and contrast Identity Management and Client Management options on Anypoint Platform

Identify data residency of different kinds of data (payload, metrics, and others)

Identify dependencies between an API, its API specification, its implementation, and its clients

Describe the creation and publication of reusable API-related assets using API specifications and Anypoint Platform components

Identify changes to an API that would require or not require changing the major/minor/patch component of its semantic version

Given a specific power relationship between two Bounded Contexts, choose the most appropriate strategy for mapping between the API data models of these Bounded Contexts

Identify idempotent HTTP methods and HTTP-native support for optimistic concurrency

Recognize the important features and functionality of API Designer to design API specifications

Identify appropriate APIs to implement a business process and assign them to layers of API-led connectivity

Assign APIs to layers according to ownership, functional 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

Make appropriate use of API instances and environments in API manager taking into account the nature of the API and the underlying data and system

Select appropriate API policies and other components of the AP to support specific non-functional requirements (NFRs)

Identify any change(s) required to an API specification to reflect the application of an API policy with specific characteristics

Select an approach to API policy enforcement based on specific preferences and constraints, including, but not limited to, API proxies/API gateways and Anypoint Service 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