Tracks: MuleSoft Platform Architect

Meeting API quality goals

Design, describe, and differentiate between scenarios that use an OS or caching

Select resilience strategies that help web API clients guard against failures when invoking APIs

Describe when horizontal scaling of an API implementation is or is not likely to benefit response time and throughput as seen by API clients

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

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

Specify alerts to define for Mule applications

Explaining application network basics

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

Establishing organizational and platform foundations

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

Describe the high-level structure and benefits of MuleSoft Catalyst

Choose between options for hosting and managing Anypoint Platform control and runtime planes

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

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

Designing and sharing APIs

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

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

Designing APIs using System, Process, and Experience Layers

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

Select DataGraph only for suitable roles in an application network, according to its high-level features

Governing web APIs on Anypoint Platform

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 API 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

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 (IdPs), AP Business Groups, and API clients in the context of OAuth 2.0

Architecting and deploying API implementations

Explain how to use auto-discovery to link a web API implementation to an API instance managed with API Manager

Identify requirements that call for the use of an Anypoint Virtual Private Cloud (VPC)

Compare and contrast options for hosting and managing Anypoint Platform runtime planes

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

Explain options for automated building, testing, and deployment of API implementations and related artifacts in a DevOps setting

Deploying API implementations to CloudHub

Describe the scenarios for which Object Store (OS) should be used with CloudHub

Select CloudHub worker sizes and configuration as appropriate

Given an app deployed to the CloudHub shared worker cloud in one or more regions, describe and predict its reliability and performance characteristics

Identify the defining differences between the CloudHub Shared and Dedicated Load Balancers

Compare and contrast the options for CloudHub networking in the presence of customer-owned Amazon VPCs and on-premises data centers

Identify and avoid single points of failure in CloudHub deployments of API implementations