Salesforce MuleSoft Developer flashcards
Salesforce MuleSoft Developer · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- API specification
- A machine-readable contract describing an API's resources, operations, parameters, responses, and data types, used to generate documentation, mocks, and implementation scaffolding.
- RAML 1.0 header
- A RAML document begins with the line #%RAML 1.0, followed by title, version, baseUri, and resource definitions.
- OpenAPI 3.0 structure
- An OpenAPI 3.0 document uses openapi, info, servers, paths, and components; each path holds HTTP operations with parameters and responses.
- API-led connectivity layers
- System APIs expose systems of record, process APIs orchestrate and combine data, and experience APIs tailor responses for specific channels.
- Mocking Service
- An Anypoint Platform feature that creates a callable mock endpoint from a published API specification, letting consumers test requests before the real implementation exists.
- Exchange asset
- A versioned, discoverable package published to Anypoint Exchange, such as an API specification, connector, template, or reusable fragment.
- API fragment
- A reusable piece of an API specification, such as RAML traits or resourceTypes or OpenAPI components, shared through Exchange.
- CloudHub deployment target
- A MuleSoft-hosted runtime where applications run on workers in the cloud, managed through Runtime Manager and API Manager.
- Autodiscovery
- A flow element that binds a deployed Mule application to an API instance in API Manager, enabling policies and analytics for that API.
- API Manager policy
- A runtime rule applied to an API instance, such as rate limiting, SLA tier enforcement, OAuth 2.0, or JWT validation, independent of flow code.
- Runtime Manager
- The Anypoint Platform console for deploying and monitoring applications, viewing logs and metrics, and managing servers, workers, and alerts.
- Secure properties
- Encrypted configuration values in a Mule application, decrypted at runtime using the secure properties tool and an encryption key.
- Mule application JAR
- The deployable artifact built from a Mule project, containing flows, dependencies, and configuration, deployed to a runtime target.
- APIkit Router
- A Mule component that reads a RAML or OpenAPI specification and routes incoming requests to generated flows based on resource path and HTTP method.
- HTTP Listener
- A Mule source that receives inbound HTTP requests and exposes request data through attributes such as headers, queryParams, uriParams, and method.
- HTTP Request connector
- A Mule operation that sends outbound HTTP calls, configurable by method, URI, query parameters, headers, and response validation.
- Choice router
- A Mule router that evaluates DataWeave conditions in order and sends the event to the first matching route, with an optional default route.
- Scatter-Gather
- A Mule scope that executes multiple routes in parallel and aggregates their results; by default an error in any route fails the whole scope.
- Flow Reference
- A Mule component that synchronously invokes another flow by name, allowing logic reuse without an external network call.
- DataWeave header
- A DataWeave script begins with %dw 2.0, followed by input and output directives; the body starts after the --- separator.
- map function
- A DataWeave array function that applies an expression to each element and returns a new array of the same length.
- mapObject function
- A DataWeave function that transforms each key-value pair of an object and returns a new object.
- filter function
- A DataWeave function that returns only the array elements for which a Boolean expression is true.
- reduce function
- A DataWeave function that collapses an array into a single value by applying an accumulator expression across elements.
- as operator
- A DataWeave coercion operator that converts a value to a target type, such as String, Number, or Array; invalid conversions raise an error.
- default operator
- A DataWeave operator that returns a fallback value when the left operand is null or absent, written as value default fallback.
- On Error Propagate
- An error handler that processes the error and then rethrows it, so the flow fails and the error reaches the caller or outer handler.
- On Error Continue
- An error handler that processes the error and returns a fallback result, allowing the flow to complete successfully instead of failing.
- Try scope
- A Mule scope that isolates components and applies its own error handler, limiting error handling to that block without affecting the rest of the flow.
- Raise Error
- A Mule component that throws a custom Mule error with a specified type and description, useful for enforcing business rules.
- error object
- The Mule error structure exposing type, description, errorMessage, cause, and childErrors for use in error handlers.
- Until Successful
- A Mule scope that retries its child components until they succeed or a configured maximum number of retries is reached.