無料提供中のMCPA-Level-1試験問題集で（2025年最新のPDF問題集）信頼度の高いテストエンジン
MCPA-Level-1のPDFで最近更新された問題です集試験点数を伸ばそう
この試験は多肢選択式の質問で構成されており、候補者は2時間以内に試験を完了する必要があります。試験の合格スコアは70％であり、結果は試験の完了直後に利用可能です。
MCPA-Level-1試験は、MuleSoftのAnypoint Platformについて深い理解を持つ経験豊富なMuleSoft開発者またはアーキテクトを対象としています。この試験は、Anypoint Studio、Anypoint Platform、Mule Runtimeを含むさまざまなMuleSoft製品の知識を試験することを目的としています。また、MuleSoftの統合、API、コネクタの設計と実装能力も評価されます。
質問 # 10
An organization has implemented a Customer Address API to retrieve customer address information. This API has been deployed to multiple environments and has been configured to enforce client IDs everywhere.
A developer is writing a client application to allow a user to update their address. The developer has found the Customer Address API in Anypoint Exchange and wants to use it in their client application.
What step of gaining access to the API can be performed automatically by Anypoint Platform?
- A. Approve the client application request for the chosen SLA tier
- B. Request access to the appropriate API Instances deployed to multiple environments using the client application's credentials
- C. Modify the client application to call the API using the client application's credentials
- D. Create a new application in Anypoint Exchange for requesting access to the API
正解：A
質問 # 11
In an organization, the InfoSec team is investigating Anypoint Platform related data traffic.
- A. From various components of Anypoint Platform, such as the Shared Load Balancer, VPC, and Mule runtimes
- B. From the Mule runtime or the API Manager, depending on the type of data
- C. From the Mule runtime or the API implementation, depending on the deployment model
- D. From where does most of the data available to Anypoint Platform for monitoring and alerting originate?
- E. From the Mule runtime irrespective of the deployment model
正解：C
質問 # 12
What condition requires using a CloudHub Dedicated Load Balancer?
- A. When cross-region load balancing is required between separate deployments of the same Mule application
- B. When server-side load-balanced TLS mutual authentication is required between API implementations and API clients
- C. When custom DNS names are required for API implementations deployed to customer-hosted Mule runtimes
- D. When API invocations across multiple CloudHub workers must be load balanced
正解：B
解説：
Correct answer: When server-side load-balanced TLS mutual authentication is required between API implementations and API clients
*****************************************
Fact/ Memory Tip: Although there are many benefits of CloudHub Dedicated Load balancer, TWO important things that should come to ones mind for considering it are:
>> Having URL endpoints with Custom DNS names on CloudHub deployed apps
>> Configuring custom certificates for both HTTPS and Two-way (Mutual) authentication.
Coming to the options provided for this
>> We
CANNOT use DLB to perform cross-region load balancing between separate deployments of the same Mule application.
>> We can have mapping rules to have more than one DLB URL pointing to same Mule app. But vicevera (More than one Mule app having same DLB URL) is NOT POSSIBLE
>> It is true that DLB helps to setup custom DNS names for Cloudhub deployed Mule apps but NOT true for apps deployed to Customer-hosted Mule Runtimes.
>> It is true to that we can load balance API invocations across multiple CloudHub workers using DLB but it is NOT A MUST. We can achieve the same (load balancing) using SLB (Shared Load Balancer) too. We DO NOT necessarily require DLB for achieve it.
So the only right option that fits the scenario and requires us to use DLB is when TLS mutual authentication is required between API implementations and API clients.
質問 # 13
What do the API invocation metrics provided by Anypoint Platform provide?
- A. Measurements of the effectiveness of the application network based on the level of reuse
- B. Proactive identification of likely future policy violations that exceed a given threat threshold
- C. Data on past API invocations to help identify anomalies and usage patterns across various APIs
- D. ROI metrics from APIs that can be directly shared with business users
正解：C
質問 # 14
A company wants to move its Mule API implementations into production as quickly as possible. To protect access to all Mule application data and metadata, the company requires that all Mule applications be deployed to the company's customer-hosted infrastructure within the corporate firewall. What combination of runtime plane and control plane options meets these project lifecycle goals?
- A. Manually provisioned customer-hosted runtime plane and MuleSoft-hosted control plane
- B. Manually provisioned customer-hosted runtime plane and customer-hosted control plane
- C. MuleSoft-hosted runtime plane and customer-hosted control plane
- D. iPaaS provisioned customer-hosted runtime plane and MuleSoft-hosted control plane
正解：B
解説：
Manually provisioned customer-hosted runtime plane and customer-hosted control plane
*****************************************
There are two key factors that are to be taken into consideration from the scenario given in the question.
>> Company requires both data and metadata to be resided within the corporate firewall
>> Company would like to go with customer-hosted infrastructure.
Any deployment model that is to deal with the cloud directly or indirectly (Mulesoft-hosted or Customer's own cloud like Azure, AWS) will have to share atleast the metadata.
Application data can be controlled inside firewall by having Mule Runtimes on customer hosted runtime plane. But if we go with Mulsoft-hosted/ Cloud-based control plane, the control plane required atleast some minimum level of metadata to be sent outside the corporate firewall.
As the customer requirement is pretty clear about the data and metadata both to be within the corporate firewall, even though customer wants to move to production as quickly as possible, unfortunately due to the nature of their security requirements, they have no other option but to go with manually provisioned customer-hosted runtime plane and customer-hosted control plane.
質問 # 15
A Mule application exposes an HTTPS endpoint and is deployed to three CloudHub workers that do not use static IP addresses. The Mule application expects a high volume of client requests in short time periods. What is the most cost-effective infrastructure component that should be used to serve the high volume of client requests?
- A. A customer-hosted load balancer
- B. The CloudHub shared load balancer
- C. Runtime Manager autoscaling
- D. An API proxy
正解：B
解説：
The CloudHub shared load balancer
*****************************************
The scenario in this question can be split as below:
>> There are 3 CloudHub workers (So, there are already good number of workers to handle high volume of requests)
>> The workers are not using static IP addresses (So, one CANNOT use customer load-balancing solutions without static IPs)
>> Looking for most cost-effective component to load balance the client requests among the workers.
Based on the above details given in the scenario:
>> Runtime autoscaling is NOT at all cost-effective as it incurs extra cost. Most over, there are already 3 workers running which is a good number.
>> We cannot go for a customer-hosted load balancer as it is also NOT most cost-effective (needs custom load balancer to maintain and licensing) and same time the Mule App is not having Static IP Addresses which limits from going with custom load balancing.
>> An API Proxy is irrelevant there as it has no role to play w.r.t handling high volumes or load balancing.
So, the only right option to go with and fits the purpose of scenario being most cost-effective is - using a CloudHub Shared Load Balancer.
質問 # 16
A retail company with thousands of stores has an API to receive data about purchases and insert it into a single database. Each individual store sends a batch of purchase data to the API about every 30 minutes. The API implementation uses a database bulk insert command to submit all the purchase data to a database using a custom JDBC driver provided by a data analytics solution provider. The API implementation is deployed to a single CloudHub worker. The JDBC driver processes the data into a set of several temporary disk files on the CloudHub worker, and then the data is sent to an analytics engine using a proprietary protocol. This process usually takes less than a few minutes. Sometimes a request fails. In this case, the logs show a message from the JDBC driver indicating an out-of-file-space message. When the request is resubmitted, it is successful. What is the best way to try to resolve this throughput issue?
- A. Increase the number of CloudHub workers
- B. Use a CloudHub autoscaling policy to increase the size of the CloudHub worker
- C. se a CloudHub autoscaling policy to add CloudHub workers
- D. Increase the size of the CloudHub worker(s)
正解：A
解説：
Correct answer: Increase the size of the CloudHub worker(s)
*****************************************
The key details that we can take out from the given scenario are:
>> API implementation uses a database bulk insert command to submit all the purchase data to a database
>> JDBC driver processes the data into a set of several temporary disk files on the CloudHub worker
>> Sometimes a request fails and the logs show a message indicating an out-of-file-space message Based on above details:
>> Both auto-scaling options does NOT help because we cannot set auto-scaling rules based on error messages. Auto-scaling rules are kicked-off based on CPU/Memory usages and not due to some given error or disk space issues.
>> Increasing the number of CloudHub workers also does NOT help here because the reason for the failure is not due to performance aspects w.r.t CPU or Memory. It is due to disk-space.
>> Moreover, the API is doing bulk insert to submit the received batch data. Which means, all data is handled by ONE worker only at a time. So, the disk space issue should be tackled on "per worker" basis. Having multiple workers does not help as the batch may still fail on any worker when disk is out of space on that particular worker.
Therefore, the right way to deal this issue and resolve this is to increase the vCore size of the worker so that a new worker with more disk space will be provisioned.
質問 # 17
What Mule application deployment scenario requires using Anypoint Platform Private Cloud Edition or Anypoint Platform for Pivotal Cloud Foundry?
- A. When it Is required to make ALL applications highly available across multiple data centers
- B. When ALL backend systems in the application network are deployed in the organization's intranet
- C. When it is required that ALL APIs are private and NOT exposed to the public cloud
- D. When regulatory requirements mandate on-premises processing of EVERY data item, including meta-data
正解：D
解説：
When regulatory requirements mandate on-premises processing of EVERY data item, including meta-data.
*****************************************
We need NOT require to use Anypoint Platform PCE or PCF for the below. So these options are OUT.
>> We can make ALL applications highly available across multiple data centers using CloudHub too.
>> We can use Anypoint VPN and tunneling from CloudHub to connect to ALL backend systems in the application network that are deployed in the organization's intranet.
>> We can use Anypoint VPC and Firewall Rules to make ALL APIs private and NOT exposed to the public cloud.
Only valid reason in the given options that requires to use Anypoint Platform PCE/ PCF is - When regulatory requirements mandate on-premises processing of EVERY data item, including meta-data.
質問 # 18
Refer to the exhibit.
What is a valid API in the sense of API-led connectivity and application networks?
A) Java RMI over TCP
B) Java RMI over TCP
C) CORBA over HOP
D) XML over UDP
- A. Option D
- B. Option A
- C. Option B
- D. Option C
正解：C
質問 # 19
What is typically NOT a function of the APIs created within the framework called API-led connectivity?
- A. They can compose data from various sources and combine them with orchestration logic to create higher level value.
- B. They provide an additional layer of resilience on top of the underlying backend system, thereby insulating clients from extended failure of these systems.
- C. They allow for innovation at the user Interface level by consuming the underlying assets without being aware of how data Is being extracted from backend systems.
- D. They reduce the dependency on the underlying backend systems by helping unlock data from backend systems In a reusable and consumable way.
正解：B
解説：
Explanation
https://dzone.com/articles/api-led-connectivity-with-mule
質問 # 20
Which statement is true about identity management and client management on Anypoint Platform?
- A. Anypoint Platform supports configuring one external identity provider
- B. Both client management and identity management require an identity provider
- C. If an external identity provider is configured, the SAML 2.0 bearer tokens issued by the identity provider cannot be used for invocations of the Anypoint Platform web APIs
- D. If an external client provider is configured, it must be configured at the Anypoint Platform organization level and cannot be assigned to individual business groups and environments
正解：A
解説：
Anypoint Platform allows organizations to integrate one external identity provider (IdP) for identity and access management (IAM), supporting SSO and centralized user authentication.
* Identity Provider Limit:
* Anypoint Platform supports configuring a single IdP for the organization, which can be used to authenticate all users across business groups and environments within that Anypoint organization.
* Explanation of Correct Answer (C):
* Configuring one IdP ensures centralized and secure identity management, aligned with MuleSoft' s architecture.
* Explanation of Incorrect Options:
* Option A is incorrect because SAML 2.0 bearer tokens from external IdPs can indeed be used for invoking Anypoint Platform APIs.
* Option B is incorrect as client providers can be assigned to specific business groups and environments.
* Option D is incorrect since only identity management strictly requires an IdP; client management does not.
ReferencesFor further details on identity management options, consult MuleSoft documentation on Anypoint Platform's IAM capabilities.
質問 # 21
What are 4 important Platform Capabilities offered by Anypoint Platform?
- A. API Design and Development, API Deprecation, API Versioning, API Consumer Engagement
- B. API Design and Development, API Runtime Execution and Hosting, API Operations and Management, API Consumer Engagement
- C. API Versioning, API Runtime Execution and Hosting, API Invocation, API Consumer Engagement
- D. API Design and Development, API Runtime Execution and Hosting, API Versioning, API Deprecation
正解：B
解説：
Correct answer: API Design and Development, API Runtime Execution and Hosting, API Operations and Management, API Consumer Engagement
*****************************************
>> API Design and Development - Anypoint Studio, Anypoint Design Center, Anypoint Connectors
>> API Runtime Execution and Hosting - Mule Runtimes, CloudHub, Runtime Services
>> API Operations and Management - Anypoint API Manager, Anypoint Exchange
>> API Consumer Management - API Contracts, Public Portals, Anypoint Exchange, API Notebooks
質問 # 22
Due to a limitation in the backend system, a system API can only handle up to 500 requests per second. What is the best type of API policy to apply to the system API to avoid overloading the backend system?
- A. Spike control
- B. Rate limiting - SLA based
- C. Rate limiting
- D. HTTP caching
正解：A
解説：
Spike control
*****************************************
>> First things first, HTTP Caching policy is for purposes different than avoiding the backend system from overloading. So this is OUT.
>> Rate Limiting and Throttling/ Spike Control policies are designed to limit API access, but have different intentions.
>> Rate limiting protects an API by applying a hard limit on its access.
>> Throttling/ Spike Control shapes API access by smoothing spikes in traffic.
That is why, Spike Control is the right option.
質問 # 23
An API experiences a high rate of client requests (TPS) vwth small message paytoads. How can usage limits be imposed on the API based on the type of client application?
- A. Use a cross-origin resource sharing (CORS) policy to limit resource sharing between client applications, configured by the client application type
- B. Use a spike control policy that limits the number of requests for each client application type
- C. Use a rate limiting policy and a client ID enforcement policy, each configured by the client application type
- D. Use an SLA-based rate limiting policy and assign a client application to a matching SLA tier based on its type
正解：D
解説：
Correct answer: Use an SLA-based rate limiting policy and assign a client application to a matching SLA tier based on its type.
*****************************************
>> SLA tiers will come into play whenever any limits to be imposed on APIs based on client type
質問 # 24
An organization is deploying their new implementation of the OrderStatus System API to multiple workers in CloudHub. This API fronts the organization's on-premises Order Management System, which is accessed by the API implementation over an IPsec tunnel.
What type of error typically does NOT result in a service outage of the OrderStatus System API?
- A. The Order Management System is Inaccessible due to a network outage in the organization's on-premises data center
- B. API Manager has an extended outage during the initial deployment of the API implementation
- C. A CloudHub worker fails with an out-of-memory exception
- D. The AWS region goes offline with a major network failure to the relevant AWS data centers
正解：A
質問 # 25
Refer to the exhibit. An organization needs to enable access to their customer data from both a mobile app and a web application, which each need access to common fields as well as certain unique fields.
The data is available partially in a database and partially in a 3rd-party CRM system.
What APIs should be created to best fit these design requirements?
A) A Process API that contains the data required by both the web and mobile apps, allowing these applications to invoke it directly and access the data they need thereby providing the flexibility to add more fields in the future without needing API changes
B) One set of APIs (Experience API, Process API, and System API) for the web app, and another set for the mobile app
C) Separate Experience APIs for the mobile and web app, but a common Process API that invokes separate System APIs created for the database and CRM system
D) A common Experience API used by both the web and mobile apps, but separate Process APIs for the web and mobile apps that interact with the database and the CRM System
- A. Option B
- B. Option D
- C. Option C
- D. Option A
正解：C
質問 # 26
Refer to the exhibit.
What is the best way to decompose one end-to-end business process into a collaboration of Experience, Process, and System APIs?
A) Handle customizations for the end-user application at the Process API level rather than the Experience API level
B) Allow System APIs to return data that is NOT currently required by the identified Process or Experience APIs
C) Always use a tiered approach by creating exactly one API for each of the 3 layers (Experience, Process and System APIs)
D) Use a Process API to orchestrate calls to multiple System APIs, but NOT to other Process APIs
- A. Option D
- B. Option A
- C. Option B
- D. Option C
正解：C
質問 # 27
An organization is implementing a Quote of the Day API that caches today's quote.
What scenario can use the GoudHub Object Store via the Object Store connector to persist the cache's state?
- A. When there are three CloudHub deployments of the API implementation to three separate CloudHub regions that must share the cache state
- B. When there is one CloudHub deployment of the API implementation to three CloudHub workers that must share the cache state
- C. When there is one deployment of the API implementation to CloudHub and anottV deployment to a customer-hosted Mule runtime that must share the cache state
- D. When there are two CloudHub deployments of the API implementation by two Anypoint Platform business groups to the same CloudHub region that must share the cache state
正解：C
質問 # 28
A Mule application implements an API. The Mule application has an HTTP Listener whose connector configuration sets the HTTPS protocol and hard-codes the port value. The Mule application is deployed to an Anypoint VPC and uses the CloudHub 1.0 Shared Load Balancer (SLB) for all incoming traffic.
Which port number must be assigned to the HTTP Listener's connector configuration so that the Mule application properly receives HTTPS API invocations routed through the SLB?
- A. 0
- B. 1
- C. 2
- D. 3
正解：A
解説：
When using CloudHub 1.0's Shared Load Balancer (SLB) for a Mule application configured with HTTPS in an Anypoint VPC, specific ports must be configured for the application to correctly route incoming traffic:
* Port Requirement for SLB:
* The CloudHub Shared Load Balancer for HTTPS traffic requires that applications listen on port 8092 for secure (HTTPS) communication. This port is reserved specifically for SSL traffic when using SLB with Anypoint VPCs.
* Why Option B is Correct:
* Setting the HTTP Listener's connector configuration to 8092 aligns with CloudHub requirements for HTTPS via the Shared Load Balancer.
* Explanation of Incorrect Options:
* Option A (8082) is used for non-HTTPS (HTTP) traffic.
* Option C (80) and Option D (443) are standard web ports but are not applicable within CloudHub SLB's internal configuration for VPC routing.
ReferencesFor more information on the Shared Load Balancer port configurations, refer to MuleSoft's documentation on CloudHub and VPC load balancer requirements.
質問 # 29
What correctly characterizes unit tests of Mule applications?
- A. They must be triggered by an external client tool or event source
- B. They are typically written using MUnit to run in an embedded Mule runtime that does not require external connectivity
- C. They test the validity of input and output of source and target systems
- D. They must be run in a unit testing environment with dedicated Mule runtimes for the environment
正解：B
解説：
Correct answer: They are typically written using MUnit to run in an embedded Mule runtime that does not require external connectivity.
*****************************************
Below TWO are characteristics of Integration Tests but NOT unit tests:
>> They test the validity of input and output of source and target systems.
>> They must be triggered by an external client tool or event source.
It is NOT TRUE that Unit Tests must be run in a unit testing environment with dedicated Mule runtimes for the environment.
MuleSoft offers MUnit for writing Unit Tests and they run in an embedded Mule Runtime without needing any separate/ dedicated Runtimes to execute them. They also do NOT need any external connectivity as MUnit supports mocking via stubs.
https://dzone.com/articles/munit-framework
質問 # 30
What is true about automating interactions with Anypoint Platform using tools such as Anypoint Platform REST APIs, Anypoint CU, or the Mule Maven plugin?
- A. Access to Anypoint Platform APIs and Anypoint CU can be controlled separately through the roles and permissions in Anypoint Platform, so that specific users can get access to Anypoint CLI white others get access to the platform APIs
- B. API policies can be applied to the Anypoint Platform APIs so that ONLY certain LOBs have access to specific functions
- C. Anypoint Platform APIs can ONLY automate interactions with CloudHub, while the Mule Maven plugin is required for deployment to customer-hosted Mule runtimes
- D. By default, the Anypoint CLI and Mule Maven plugin are NOT included in the Mule runtime, so are NOT available to be used by deployed Mule applications
正解：D
解説：
By default, the Anypoint CLI and Mule Maven plugin are NOT included in the Mule runtime, so are NOT available to be used by deployed Mule applications
*****************************************
>> We CANNOT apply API policies to the Anypoint Platform APIs like we can do on our custom written API instances. So, option suggesting this is FALSE.
>> Anypoint Platform APIs can be used for automating interactions with both CloudHub and customer-hosted Mule runtimes. Not JUST the CloudHub. So, option opposing this is FALSE.
>> Mule Maven plugin is NOT mandatory for deployment to customer-hosted Mule runtimes. It just helps your CI/CD to have smoother automation. But not a compulsory requirement to deploy. So, option opposing this is FALSE.
>> We DO NOT have any such special roles and permissions on the platform to separately control access for some users to have Anypoint CLI and others to have Anypoint Platform APIs. With proper general roles
/permissions (API Owner, Cloudhub Admin etc..), one can use any of the options (Anypoint CLI or Platform APIs). So, option suggesting this is FALSE.
Only TRUE statement given in the choices is that - Anypoint CLI and Mule Maven plugin are NOT included in the Mule runtime, so are NOT available to be used by deployed Mule applications.
Maven is part of Studio or you can use other Maven installation for development.
CLI is convenience only. It is one of many ways how to install app to the runtime.
These are definitely NOT part of anything except your process of deployment or automation.
質問 # 31
What are 4 important Platform Capabilities offered by Anypoint Platform?
- A. API Design and Development, API Deprecation, API Versioning, API Consumer Engagement
- B. API Design and Development, API Runtime Execution and Hosting, API Operations and Management, API Consumer Engagement
- C. API Versioning, API Runtime Execution and Hosting, API Invocation, API Consumer Engagement
- D. API Design and Development, API Runtime Execution and Hosting, API Versioning, API Deprecation
正解：B
解説：
API Design and Development, API Runtime Execution and Hosting, API Operations and Management, API Consumer Engagement
*****************************************
>> API Design and Development - Anypoint Studio, Anypoint Design Center, Anypoint Connectors
>> API Runtime Execution and Hosting - Mule Runtimes, CloudHub, Runtime Services
>> API Operations and Management - Anypoint API Manager, Anypoint Exchange
>> API Consumer Management - API Contracts, Public Portals, Anypoint Exchange, API Notebooks
質問 # 32
In which layer of API-led connectivity, does the business logic orchestration reside?
- A. Experience Layer
- B. System Layer
- C. Process Layer
正解：C
解説：
Correct answer: Process Layer
*****************************************
>> Experience layer is dedicated for enrichment of end user experience. This layer is to meet the needs of different API clients/ consumers.
>> System layer is dedicated to APIs which are modular in nature and implement/ expose various individual functionalities of backend systems
>> Process layer is the place where simple or complex business orchestration logic is written by invoking one or many System layer modular APIs So, Process Layer is the right answer.
質問 # 33
......
MCPA-Level-1完全版問題集には無料PDF問題で合格させる：https://www.jpntest.com/shiken/MCPA-Level-1-mondaishu