Salesforce Certified MuleSoft Integration Foundations 온라인 연습
최종 업데이트 시간: 2026년05월15일
당신은 온라인 연습 문제를 통해 Salesforce Mule-101 시험지식에 대해 자신이 어떻게 알고 있는지 파악한 후 시험 참가 신청 여부를 결정할 수 있다.
시험을 100% 합격하고 시험 준비 시간을 35% 절약하기를 바라며 Mule-101 덤프 (최신 실제 시험 문제)를 사용 선택하여 현재 최신 55개의 시험 문제와 답을 포함하십시오.
정답:
Explanation:
RESTful APIs: By definition, REST relies on the HTTP protocol (Hypertext Transfer Protocol). Security: When an API is "secured," it almost universally implies the use of TLS/SSL encryption, turning HTTP into HTTPS.
Load Balancers: Application Load Balancers (ALBs) operate at Layer 7 (Application Layer) and are
designed to route HTTP/HTTPS traffic.
Why others are incorrect:
SMTP: Simple Mail Transfer Protocol (Email).
SFTP: Secure File Transfer Protocol (Files).
LDAP: Lightweight Directory Access Protocol (Identity/User lookup).
None of these are used for standard REST API routing.
정답:
Explanation:
Orchestration: This refers to the logic where a central controller (the Process API) manages the interactions between multiple systems to achieve a business goal.
The Scenario: The API is "coordinating stateful interactions" (e.g., Step 1: Validate Customer -> Step 2: Check Inventory -> Step 3: Debit Payment -> Step 4: Create Shipment). This strictly sequential or logic-driven coordination is the definition of Orchestration.
Why others are incorrect:
Aggregation: Specifically refers to just gathering data from multiple sources (Scatter-Gather) and combining the results, usually without complex state management or sequential logic. Streaming: Refers to processing data in continuous chunks, not the logic of coordinating services.
정답:
Explanation:
The Requirement: The key phrase is "notification... of order management, warehouse, and billing systems." This describes a One-to-Many communication pattern (Fan-out).
Pub/Sub (Publish/Subscribe): This pattern decouples the sender (eCommerce Site) from the receivers (Warehouse, Billing).
The eCommerce site publishes a single "Order Created" event to a topic (e.g., Anypoint MQ or JMS).
Multiple subscribers (Warehouse, Billing, OMS) listen to that topic and process the message
independently and asynchronously.
Why others are incorrect:
ETL: Is typically batch-oriented and used for moving large data sets to a warehouse, not for near real-time event notifications.
MFT: Is for moving files, which is too slow and heavy for high-volume, individual order notifications.
정답:
Explanation:
PaaS (Platform as a Service): CloudHub is MuleSoft's managed integration platform. In the NIST cloud model, it falls under iPaaS, which is a specialized form of PaaS.
The Model:
MuleSoft manages: The underlying infrastructure (AWS EC2 instances), operating systems, updates, security patching, and the Java/Mule Runtime environment. Customer manages: The application code (Mule apps) and data.
Why it is not IaaS: In IaaS (like raw AWS EC2), the customer would be responsible for installing the OS, Java, and patching the server. In CloudHub, this is abstracted away.
정답:
Explanation:
Audit Logging: This feature in Anypoint Platform provides a searchable history of actions performed within the platform. It is designed specifically for governance and security compliance.
What it tracks: It records "who did what and when."
This includes changes to:
User permissions and roles (Access Management).
Environment configurations.
API Manager policies.
Why others are incorrect:
Anypoint Monitoring: Focuses on application performance (CPU, Memory, API analytics), not administrative actions.
Stack Traces: Are used for debugging runtime application errors, not auditing user permissions.
정답:
Explanation:
REST (Representational State Transfer): REST is an architectural style that allows resources to be represented in multiple formats (Media Types)5555.
Versatility: Unlike SOAP (which is strictly XML), a RESTful API can easily support both JSON and XML
representations of the same resource, often determined by the Accept or Content-Type headers.
Why others are incorrect:
SOAP: Strictly uses XML.
GraphQL: Typically uses JSON for both queries and responses.
gRPC: Uses Protocol Buffers (binary), not human-readable JSON/XML by default.
정답:
Explanation:
Content Negotiation: The HTTP Accept header is used by the client to tell the server what media type (format) it expects in the response4444.
application/json: This MIME type explicitly requests JSON (JavaScript Object Notation).
Analyzing the Options:
(B) {"status": "healthy"} is valid JSON format (Key-Value pair wrapped in braces).
(C) status>healthy</status> is XML.
(A) is YAML or Plain Text.
정답:
Explanation:
Control Plane vs. Runtime Plane:
Control Plane: The set of components that manage, monitor, and design APIs and applications. This includes API Manager, Runtime Manager (the console), Anypoint Exchange, and Design Center3. Runtime Plane: The infrastructure where the applications actually run (execute). This includes the Mule Runtime engine, Runtime Fabric, and CloudHub workers.
API Manager: It sits in the Control Plane and pushes policies (governance) down to the runtime engines (gateways).
정답:
Explanation:
The IT Delivery Gap: This question addresses the "IT Delivery Gap"―the widening gap between business demands and IT's capacity to deliver.
The Solution (New Operating Model): MuleSoft recommends shifting from a centralized factory
model to an Asset-Based consumption model.
Decoupling (Option A): By using API-led Connectivity:
Central IT builds reusable System APIs (unlocking core assets/systems of record) and governs them.
Lines of Business (LOB) consume these assets to build their own Process and Experience APIs
(Innovation)2.
Why others fail:
(B) Hiring doesn't scale linearly with exponential demand.
(C) Removing governance creates security risks ("Shadow IT").
(D) Code-first ignores reuse and leads to technical debt.
정답:
Explanation:
Definition of iPaaS: Gartner and MuleSoft define iPaaS (Integration Platform as a Service) as a suite of cloud services enabling the development, execution, and governance of integration flows connecting any combination of on-premises and cloud-based processes, services, applications, and data within individual or across multiple organizations.
The Key Characteristic: The "as a Service" suffix explicitly denotes a Cloud-based delivery model111111111.
MuleSoft Context: CloudHub is the iPaaS component of the Anypoint Platform. It is a fully managed, multi-tenant, cloud-based integration platform where you deploy API implementations without managing the underlying hardware.
정답:
Explanation:
HTTP Status Codes: Understanding these is fundamental to MuleSoft integration.
2xx (Success - Answer B): The request was received, understood, and accepted. (e.g., 200 OK, 201
Created, 202 Accepted).
3xx (Redirection): Further action needs to be taken to complete the request (e.g., 301 Moved Permanently).
4xx (Client Error): The request contains bad syntax or cannot be fulfilled (e.g., 400 Bad Request, 401 Unauthorized, 404 Not Found).
5xx (Server Error): The server failed to fulfill an apparently valid request (e.g., 500 Internal Server Error, 502 Bad Gateway).
Context: When a Mule flow makes an HTTP Request, it checks these status codes to determine if the On Error scope should be triggered. By default, 4xx and 5xx trigger errors; 2xx indicates success.
정답:
Explanation:
The Shared Goal: Both SOA (an older architectural style) and API-led Connectivity (MuleSoft's modern approach) aim to solve the problem of "Spaghetti Code" by breaking monolithic applications into smaller pieces.
Reusability: The core promise of both is Reusability.
SOA: Aimed to create reusable web services (often SOAP). API-led: Focuses on creating reusable Assets (System, Process, and Experience APIs) that can be discovered and self-served by other teams.
The Difference: While the goal (Reuse) is the same, SOA often failed due to heavy governance and lack of discoverability. API-led connectivity improves on this by emphasizing consumption and self-service via the Anypoint Exchange.
정답:
Explanation:
(Note: The question implies "What is the next step after design/validation?" or "How is the spec used?". Based on the answer key A, the context is how the spec drives development).

Shutterstock
Explore
API-Led Connectivity & Design-First: MuleSoft promotes a "Design-First" approach. You first write the
RAML or OAS specification.
MuleSoft scaffolding: Once the specification is designed and published to Exchange, the developer
imports it into Anypoint Studio. Studio then scaffolds (automatically generates) the Mule flows based
on the API Specification.
The Workflow:
Design: Create the API contract (RAML/OAS).
Publish: Publish to Exchange.
Build (Answer A): Use the API specification to generate the flow structure (APIkit Router) and
implement the logic.
This ensures the implementation strictly matches the design defined in the earlier phases.
정답: B
Explanation:
Request-Response: The HTTP protocol is inherently synchronous and follows the Request-Response pattern. The client sends a request (the GET command) and waits for the server to process the query and send back the data (the 200 OK response).
Synchronous Nature: The "Synchronous" keyword in the question is the biggest clue. The client processing is blocked or expects an immediate return of data before proceeding.
Why "Multicast" is incorrect: Multicast is a one-to-many pattern (usually asynchronous). It involves sending one message to multiple receivers (like a topic subscription), which contradicts the question's scenario of getting a "record from a single system." 8
정답:
Explanation:
The Interface: In system integration and MuleSoft terminology, the Interface is the contract that defines how two systems communicate. It specifies: Protocol: How data is transmitted (e.g., HTTP, FTP, AMQP).
Format: The structure of the data (e.g., JSON, XML, CSV).
Method: The specific action (e.g., GET, POST).
Why other options are incorrect:
Message: This refers to the actual data payload (the content) being sent, not the rules of communication.
Component: This usually refers to a specific building block within the Mule flow (like a Logger or a Database connector) or a software module, not the communication definition itself. Interaction: This describes the act of communicating, not the definition of the standard used.