About MuleSoft Certified Platform Architect - Level 1

A MuleSoft Certified Platform Architect 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.

Skills Acquired

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.

Exam 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.

Course Outline

The MuleSoft Certified Platform Architect - Level 1 Exam covers the following topics -

Explaining application network basics

• Explain MuleSoft’s proposal for closing the IT delivery gap.

• Describe the role and characteristics of the "modern API."

• Define and describe the benefits of API-led connectivity and application networks.

• Define outcome-based delivery (OBD).

• Correctly use the terms API, API implementation, API client, API consumer, and API invocation.

• Describe the capabilities and high-level components of Anypoint Platform.

Establishing organizational and platform foundations

• Describe the purpose and roles of a Center for Enablement (C4E).

• Identify KPIs to measure the success of a C4E.

• Given specific organizational requirements, preferences, and constraints, identify all suitable Anypoint Platform deployment options.

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

Designing APIs and API interactions

• Break down functional requirements into business-aligned APIs with effective granularity.

• Given a set of APIs and specific preferences and organizational characteristics, recommend the use of an Enterprise Data Model or Bounded Context Data Models.

• Identify changes to an API that would require or not require a major version increment.

• When asynchronous execution of API invocations is needed, select when to appropriately use polling or callbacks.

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

• Describe the creation and publication of reusable API-related assets using RAML and Anypoint Platform components.

Following API-led connectivity

• 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.

• Given specific requirements and organizational characteristics, recommend the most appropriate approach relating the API data model of System APIs to that of their backend system.

Governing APIs on Anypoint Platform

• Given specific preferences and constraints, select API policy enforcement with or without API proxies.

• Select appropriate API policies to enforce non-functional constraints on API invocations.

• Given an API policy with specific characteristics, identify any change required in the corresponding RAML definition.

• Given a layer of API-led connectivity, identify API policies that are typically applied to that layer and the scenarios needing custom policies.

• Identify which types of APIs and other remote interfaces are or are not amenable to management by API Manager.

Controlling access to APIs

• Describe when and how to pass client ID and secret to an API.

• Explain how to register an API client for access to an API version.

Delivering APIs

• Describe the automation capabilities of Anypoint Platform for DevOps, CI/CD, and testing.

• Compare unit and integration tests and specify where MUnit is best employed.

• Explain how to use autodiscovery to link an API implementation to an API instance managed with API Manager.

• Specify how and when to promote APIs with API Manager.

• Identify when redeployment of API implementations is necessary.

Gatekeeper Enhanced Security Reference

• Deploying Mule applications to CloudHub

• Describe the fundamentals of deployments, networking, and routing on CloudHub.

• Select CloudHub worker sizes and configuration as appropriate.

• Describe the scenarios for which Object Store should be used with CloudHub.

Architecting performant and resilient APIs

• Identify the factors involved in scaling API performance.

• Identify the differences between the CloudHub Shared and Dedicated Load Balancers.

• Identify single points of failure in typical CloudHub usage.

• Select strategies that help API clients guard against failures in API invocations.

Monitoring and analyzing application networks

• Identify the components of Anypoint Platform that generate data for monitoring and alerting.

• Describe the metrics collected by Anypoint Platform for API invocations.

• Describe and select between the options for performing API analytics within and outside of Anypoint Platform.

• Specify alerts to define for key metrics of API invocations for all layers of API-led connectivity.

• Specify alerts to define for API implementations.