# API Led Connectivity Technologies

*MuleSoft Platform Architect Study Guide · Explaining application network basics · Last updated November 13, 2026 · https://www.certifyforce.com/study-guide/mulesoft-platform-architect/explaining-application-network-basics/api-led-connectivity-technologies*

Separate API descriptions, implementation building blocks and runtime management, then use metadata deliberately when designing Mule integrations.

- Certification: Salesforce MuleSoft Platform Architect
- Exam section: Explaining application network basics
- Study guide: https://www.certifyforce.com/study-guide/mulesoft-platform-architect

**Official exam objective:**

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

## What the exam expects

- Distinguish interface descriptions from executable integrations and management controls.
- Identify how connectors, transformations and messaging contribute to an application network.
- Separate design conformance, discovery and request enforcement.
- Explain why metadata helps developers without replacing implementation decisions.

An **API contract** describes an interface; a **connector** integrates with an external resource; **DataWeave** expresses data manipulation; **DataSense** supplies design-time metadata; a **policy** controls managed API interactions. These responsibilities cooperate across the lifecycle ([API management](https://docs.mulesoft.com/general/learning-map-api-management), [Mule development](https://docs.mulesoft.com/mule-runtime/4.6/mule-app-dev)).

## Key facts

| Fact | Detail | Source |
|---|---|---|
| Implementation choice | Management can include APIs built and deployed elsewhere. | [API management](https://docs.mulesoft.com/general/learning-map-api-management) |
| Contract formats | API assets include OAS, RAML and WSDL. | [API Manager](https://docs.mulesoft.com/api-manager/latest/latest-overview-concept) |
| Flow entry | A source creates the event that processors handle. | [Mule development](https://docs.mulesoft.com/mule-runtime/4.6/mule-app-dev) |
| Mapping assistance | DataSense supplies structures; developers configure mappings. | [DataSense](https://docs.mulesoft.com/studio/datasense-concept) |
| Shared configuration | Domains share resources rather than processing behaviour. | [Shared resources](https://docs.mulesoft.com/mule-runtime/4.6/shared-resources) |
| Editor discovery | Payload completion exposes available properties and methods. | [DataSense](https://docs.mulesoft.com/studio/datasense-concept) |
| Metadata contracts | Flow and subflow contracts describe required and returned event shapes. | [DataSense](https://docs.mulesoft.com/studio/datasense-concept) |

## Check yourself

- Why can an explicit type on Transform Message obscure useful design information?
- When declaring a reusable subflow's metadata contract, which two event shapes should be stated?
- How can a developer inspect payload property names in a Logger after an unfamiliar connector?

## Sources

- [Getting Started with API Management](https://docs.mulesoft.com/general/learning-map-api-management)
- [API Manager Overview](https://docs.mulesoft.com/api-manager/latest/latest-overview-concept)
- [DataSense](https://docs.mulesoft.com/studio/datasense-concept)
- [Shared Resources in Mule 4.6](https://docs.mulesoft.com/mule-runtime/4.6/shared-resources)
- [Mule Application Development 4.6](https://docs.mulesoft.com/mule-runtime/4.6/mule-app-dev)

## About the full unit

The "Core concepts", "Exam traps" and "Worked scenario" sections of this unit, its 5 linked practice questions, and unlimited timed mock exams are included with the MuleSoft Platform Architect pack (USD $19): https://www.certifyforce.com/practice-exams