1. Home
  2. Salesforce
  3. MuleSoft-Integration-Architect-I Exam Syllabus

Salesforce Certified MuleSoft Platform Integration Architect (Mule-Arch-202) Exam Syllabus

Start Free Salesforce Certified MuleSoft Platform Integration Architect (Mule-Arch-202) Exam Practice After Reviewing the Topics

Before starting your Salesforce Certified MuleSoft Platform Integration Architect (Mule-Arch-202) exam preparation, it is recommended to review the complete Salesforce Certified MuleSoft Platform Integration Architect exam syllabus and carefully go through the exam objectives listed below. Once you understand the exam structure and objectives, you should practice using our free Salesforce Certified MuleSoft Platform Integration Architect (Mule-Arch-202) questions. We also provide premium Salesforce Certified MuleSoft Platform Integration Architect (Mule-Arch-202) practice test, fully updated according to the latest exam objectives, to help you accurately assess your preparedness for the actual exam.

Salesforce
Vendor
Salesforce Certified MuleSoft Platform Integration Architect (Mule-Arch-202)
Exam Code
273
Total Questions
10
Total Exam Domains

START FREE Salesforce Certified MuleSoft Platform Integration Architect (Mule-Arch-202) EXAM PRACTICE

NO SIGNUP REQUIRED  •  100% FREE TO START

MuleSoft-Integration-Architect-I EXAM QUESTIONS

Salesforce Certified MuleSoft Platform Integration Architect (Mule-Arch-202) Exam Objectives

Section 1: Initiating integration solutions on the Anypoint Platform
Weight:
8%
  • Differentiate between functional and non-functional requirements for integration solutions.
  • Select features of Anypoint Platform for designing and managing web and event-driven application programming interfaces (APIs).
  • Select deployment options of the Anypoint Platform control plane and runtime plane.
Section 2: Designing architecture using integration paradigms
Weight:
10%
  • Create high-level integration architectures using API-led Connectivity.
  • Create high-level integration architectures using web APIs and HTTP.
  • Create high-level integration architectures using event-driven APIs and message brokers.
  • Design Mule applications and integration solutions using common messaging patterns and technologies.
Section 3: Designing and developing Mule applications:
Weight:
15%
  • Select among available options for setting Mule application properties.
  • Select and use fundamental features available to all Mule applications.
  • Design Mule applications using core routers available to all Mule applications.
  • Describe the fundamental features of the Salesforce Connector.
  • Design Mule applications using common features of core connectors.
  • Select and use the available sources of metadata in the Transform Message component.
  • Design Mule applications and integration solutions using a Common/Canonical Data Model.
  • Correctly apply methods for validating data in Mule applications.
Section 4: Designing integration solutions to meet persistence requirements
Weight:
10%
  • Design Mule applications using Virtual Machine (VM) queues and the Anypoint VM Connector in all deployment options.
  • Design Mule applications using Object Stores (OSs), the OS Connector, and OS services in all deployment options.
  • Design Mule applications and integration solutions using stateful components that may be configured with an OS.
Section 5: Designing for the runtime plane technology architecture
Weight:
15%
  • Analyze the mode of operation of a Mule runtime cluster that differentiates it from other deployment options.
  • Design integration solutions deployed to CloudHub to address specific requirements using CloudHub's network features.
  • Choose Mule runtime domains and domain-shared configuration only for those requirements that clearly benefit from their capabilities.
  • Design Mule applications making effective use of the implications of the Mule 4 class loader isolation of Mule modules.
  • Describe the characteristics and implications of the Mule 4 reactive event processing model.
Section 6: Designing automated tests for Mule applications: 5%
Weight:
5%
  • Design unit test suites using MUnit and Studio's related features.
  • Identify test requirements and scenarios that are best addressed using integration testing or performance testing.
Section 7: Designing integration solutions to meet reliability requirements
Weight:
8%
  • Select alternatives to traditional transactions (local or XA) where appropriate and beneficial.
  • Recognize the purpose and characteristics of Until Successful scope, reconnection strategies, and redelivery policies.
  • Differentiate between disaster recovery and high availability and the basic approaches to achieving either in all deployment options.
  • Design Mule applications and integration solutions using local and XA transactions for all Mule connectors that support them.
Section 8: Designing integration solutions to meet performance requirements
Weight:
7%
  • Design Mule applications and integration solutions to meet performance and capacity goals.
  • Design Mule applications using available streaming features in Mule.
  • Design Mule applications to process large sequences/streams of messages.
Section 9: Designing integration solutions to meet security requirements:
Weight:
8%
  • Design secure access to the Anypoint Platform control plane and APIs.
  • Design secure edge access using Anypoint Security.
  • Analyze and counteract potential security vulnerabilities of Mule applications.
  • Recognize the audit logging capabilities of Anypoint Platform.
Section 10: Applying DevOps practices and operating integration solutions
Weight:
14%
  • Create the high-level design of continuous integration (CI) and continuous delivery (CD) pipelines for Mule applications using MuleSoft-provided Maven plugins.
  • Identify the features and characteristics for automating interactions with Anypoint Platform.
  • Design the logging configurations and options of Mule applications in all deployment options.
  • Identify the features and characteristics of Anypoint Monitoring in all deployment options.
Info