Firstly, strengthen your foundational knowledge about application networks. Go over on how to govern, deliver, and control access to API on the Anypoint Platform as well. The other tasks comprising the bulk of the exam are the following:

• Setting up organizational and platform foundation

  For you to select and establish the correct Anypoint Platform, make sure you understand the role and purpose of the Center for Enablement (C4E) and the different KPIs to gauge its success. Try your best to be able to specify all the possible Anypoint Platform deployment options.

• Designing performant and resilient APIs

  Describe the features in scaling API performance, the contrast between CloudHub Shared and Dedicated Load Balancers, and lastly, the single points of failure in Cloudhub usage. Make sure to be knowledgeable with the varying strategies in helping API clients prevent failures in API invocations.

• Tracking and evaluating application networks

  Over and over again, learning the elements of the Anypoint Platform by heart is a vital step for passing MCPA - Level 1. The tasks involved are all interrelated to this main platform. You should be skilled in monitoring, alerting, and analyzing the application networks.

• Defining the basics of application network

  This portion reiterates the essence of strengthening your foothold. Have a strong grasp of the “modern API”, application networks, outcome-based delivery (OBD), and most especially the Anypoint Platform. Learn as much as you can about their roles, characteristics, benefits, terms, and capabilities.

• Plotting APIs and their interactions

  Master the art of evaluating functional requirements and transforming these into business-aligned APIs. Know what situations require polling or callbacks, what specific changes need a major version increment, and when to propose the use of Enterprise Data Model or Bounded Context Data Models. For an optimistic concurrency, be familiar with idempotent HTTP methods and HTTP-native support as well as with reusable API-related assets.

• Overseeing API access

  You will be manning the control access to APIs. Hence, you should be able to explain how to register an API client for access as well as how and when to pass client ID and secret to API.

• Carrying out APIs

  This part involves your ability to deliver APIs in circumstances that would necessitate promotion of APIs with API manager or redeployment of API implementations. You must be skillful in using autodiscovery to link API implementation to API instances. Aside from that, know the automation capabilities of the Anypoint Platform and the integration tests.

• Managing APIs on the Anypoint Platform

  Acquaint yourself with API policies, policy enforcement, and proxies as you may be dealing with them more often in your future career. Understand which APIs and remote interfaces can be managed by the API manager.

• Establishing Mule applications to Cloudhub

  Since MuleSoft is all about integrating software to connect applications, data, and devices, this concept is absolutely necessary. Build your background on the basics of deployments, networking, and routing on CloudHub. Learn how to choose CloudHub worker sizes and configurations and when to use Object Store.

• Making use of API-led connectivity

  Once again, knowledge of the APIs will help you get through this area as you will be assigning them to layers of API-led connectivity. You will be basing this assignment upon ownership, functional focus, and rate of change. Back up your recommendations when choosing the most suitable approach in the API data model of System APIs.

Reference: https://training.mulesoft.com/exam/mcpa-level1

Topics of MuleSoft MCPA - Level 1: MuleSoft Certified Platform Architect - Level 1 Exam

Candidates must know the exam topics before they start preparation because it will help them in hitting the core. Our mcpa-level-1 practice exams will include the topics discussed in detail:

• Correctly use the terms API, API implementation, API client, API consumer, and API invocation
• Select Any point Platform identity management vs client management for the correct purpose
• Identify the components of Any point Platform that generate data for monitoring and alerting
• Given a layer of API-led connectivity, identify API policies that are typically applied to that layer and the scenarios needing custom policies
• Identify KPIs to measure the success of a C4E
• Define outcome-based delivery (OBD)
• Describe the purpose and roles of a Center for Enablement (C4E)
• When asynchronous execution of API invocations is needed, select when to appropriately use polling or callbacks
• Describe the capabilities and high-level components of Any point Platform
• Define and describe the benefits of API-led connectivity and application networks
• 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
• Specify alerts to define for API implementations
• Describe and select between the options for performing API analytics within and outside of Any point Platform
• Given specific preferences and constraints, select API policy enforcement with or without API proxies
• Identify idempotent HTTP methods and HTTP-native support for optimistic concurrency.
• Describe the metrics collected by Any point Platform for API invocations
• Describe the creation and publication of reusable API-related assets using RAML and Anypoint Platform components
• Given specific organizational requirements, preferences, and constraints, identify all suitable point Platform deployment options
• Specify alerts to define for key metrics of API invocations for all layers of API-led connectivity
• Identify changes to an API that would require or not require a major version increment.
• Explain MuleSoft's proposal for closing the IT delivery gap
• Describe the role and characteristics of the “modern API.”
• 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 which types of APIs and other remote interfaces are or are not amenable to management by API Manager