1. Home
  2. Salesforce
  3. Salesforce-MuleSoft-Developer-II Exam Syllabus

Salesforce Certified MuleSoft Developer II (Mule-Dev-301) Exam Syllabus

Start Free Salesforce Certified MuleSoft Developer II (Mule-Dev-301) Exam Practice After Reviewing the Topics

Before starting your Salesforce Certified MuleSoft Developer II (Mule-Dev-301) exam preparation, it is recommended to review the complete Salesforce Certified MuleSoft Developer II 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 Developer II (Mule-Dev-301) questions. We also provide premium Salesforce Certified MuleSoft Developer II (Mule-Dev-301) 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 Developer II (Mule-Dev-301)
Exam Code
60
Total Questions
5
Total Exam Domains

START FREE Salesforce Certified MuleSoft Developer II (Mule-Dev-301) EXAM PRACTICE

NO SIGNUP REQUIRED  •  100% FREE TO START

Salesforce-MuleSoft-Developer-II EXAM QUESTIONS

Salesforce Certified MuleSoft Developer II (Mule-Dev-301) Exam Objectives

Section 1: Expose production-ready Anypoint Platform-managed APIs from Mule applications
Weight:
13%
  • Implement versioning of specific API-related artifacts.
  • Configure custom or out-of-the-box (OOTB) API policies.
  • Implement server-side caching of API invocations using API policies.
  • Implement HTTP callbacks (webhooks).
  • Code API implementations to perform API auto-discovery.
Section 2: Implement maintainable and modular Mule applications and their Maven builds
Weight:
25%
  • Modularize and optimize Mule application Maven build configurations.
  • Implement Maven-based automated deployment to Mule runtimes.
  • Execute MUnit tests with Maven.
  • Build custom API policies.
  • Encapsulate common Mule application functionality in libraries.
  • Implement custom message processors using the Mule SDK or XML SDK.
Section 3: Implement monitorable Mule applications
Weight:
15%
  • Expose Health Check endpoints from a Mule application.
  • Implement effective logging.
  • Change log levels and aggregate and analyze logs.
  • Monitor Mule applications and Mule runtimes using Anypoint Platform or external tools.
  • Implement message correlation, including persistence and propagation of correlation IDs over HTTP.
Section 4: Implement performant and reliable Mule applications
Weight:
27%
  • Implement ObjectStore persistence for all Mule deployment options.
  • Implement fault-tolerant, performant, and traceable message passing with the VM and AnypointMQ connectors.
  • Implement fault-tolerant invocations of HTTP-based APIs, reacting correctly to HTTP status codes.
  • Validate assertions using the Validation module.
  • Validate messages against XML- or JSON-Schema documents.
  • Parallelize integration logic using scatter-gather.
  • Implement compensating transactions for partially failed scatter-gather.
  • Implement client-side caching of API invocations for performance.
Section 5: Secure data at rest and in transit
Weight:
20%
  • Implement secure, environment-dependent properties management.
  • Create, package, and distribute keys and certificates.
  • Expose and invoke APIs over HTTPS.
  • Implement transport layer security (TLS) mutual authentication on the client and server side.
  • Implement API invocations authenticated by Basic Auth or OAuth2 with HTTP or REST connectors.
Info