合格させるMCPA-Level-1試験問題で実際テストエンジンPDFには154問題あります
最新をゲットせよ！MCPA-Level-1認定練習テスト問題の試験問題集
質問 # 30
What Mule application deployment scenario requires using Anypoint Platform Private Cloud Edition or Anypoint Platform for Pivotal Cloud Foundry?
- A. When regulatory requirements mandate on-premises processing of EVERY data item, including meta-data
- 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 it Is required to make ALL applications highly available across multiple data centers
正解：B
質問 # 31
What is the most performant out-of-the-box solution in Anypoint Platform to track transaction state in an asynchronously executing long-running process implemented as a Mule application deployed to multiple CloudHub workers?
- A. Persistent Object Store
- B. Redis distributed cache
- C. java.util.WeakHashMap
- D. File-based storage
正解：A
解説：
Persistent Object Store
*****************************************
>> Redis distributed cache is performant but NOT out-of-the-box solution in Anypoint Platform
>> File-storage is neither performant nor out-of-the-box solution in Anypoint Platform
>> java.util.WeakHashMap needs a completely custom implementation of cache from scratch using Java code and is limited to the JVM where it is running. Which means the state in the cache is not worker aware when running on multiple workers. This type of cache is local to the worker. So, this is neither out-of-the-box nor worker-aware among multiple workers on cloudhub. https://www.baeldung.com/java-weakhashmap
>> Persistent Object Store is an out-of-the-box solution provided by Anypoint Platform which is performant as well as worker aware among multiple workers running on CloudHub. https://docs.mulesoft.com/object-store/ So, Persistent Object Store is the right answer.
質問 # 32
What are 4 important Platform Capabilities offered by Anypoint Platform?
- A. API Design and Development, API Runtime Execution and Hosting, API Operations and Management, API Consumer Engagement
- B. API Design and Development, API Runtime Execution and Hosting, API Versioning, API Deprecation
- C. API Design and Development, API Deprecation, API Versioning, API Consumer Engagement
- D. API Versioning, API Runtime Execution and Hosting, API Invocation, API Consumer Engagement
正解：A
解説：
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
質問 # 33
A code-centric API documentation environment should allow API consumers to investigate and execute API client source code that demonstrates invoking one or more APIs as part of representative scenarios.
What is the most effective way to provide this type of code-centric API documentation environment using Anypoint Platform?
- A. Ensure the APIs are well documented through their Anypoint Exchange entries and API Consoles and share these pages with all API consumers
- B. Enable mocking services for each of the relevant APIs and expose them via their Anypoint Exchange entry
- C. Create API Notebooks and include them in the relevant Anypoint Exchange entries
- D. Make relevant APIs discoverable via an Anypoint Exchange entry
正解：C
解説：
Correct answer: Create API Notebooks and Include them in the relevant Anypoint exchange entries
*****************************************
>> API Notebooks are the one on Anypoint Platform that enable us to provide code-centric API documentation Reference:
質問 # 34
What are 4 important Platform Capabilities offered by Anypoint Platform?
- A. API Design and Development, API Runtime Execution and Hosting, API Operations and Management, API Consumer Engagement
- B. API Design and Development, API Runtime Execution and Hosting, API Versioning, API Deprecation
- C. API Design and Development, API Deprecation, API Versioning, API Consumer Engagement
- D. API Versioning, API Runtime Execution and Hosting, API Invocation, API Consumer Engagement
正解：A
解説：
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
質問 # 35
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 C
- B. Option A
- C. Option D
- D. Option B
正解：A
質問 # 36
What is true about where an API policy is defined in Anypoint Platform and how it is then applied to API instances?
- A. The API policy Is defined In Runtime Manager as part of the API deployment to a Mule runtime, and then ONLY applied to the specific API Instance
- B. The API policy is defined in API Manager, and then applied to ALL API instances in the specified environment
- C. The API policy Is defined In API Manager for a specific API Instance, and then ONLY applied to the specific API instance
- D. The API policy Is defined in API Manager and then automatically applied to ALL API instances
正解：C
解説：
The API policy is defined in API Manager for a specific API instance, and then ONLY applied to the specific API instance.
*****************************************
>> Once our API specifications are ready and published to Exchange, we need to visit API Manager and register an API instance for each API.
>> API Manager is the place where management of API aspects takes place like addressing NFRs by enforcing policies on them.
>> We can create multiple instances for a same API and manage them differently for different purposes.
>> One instance can have a set of API policies applied and another instance of same API can have different set of policies applied for some other purpose.
>> These APIs and their instances are defined PER environment basis. So, one need to manage them seperately in each environment.
>> We can ensure that same configuration of API instances (SLAs, Policies etc..) gets promoted when promoting to higher environments using platform feature. But this is optional only. Still one can change them per environment basis if they have to.
>> Runtime Manager is the place to manage API Implementations and their Mule Runtimes but NOT APIs itself. Though API policies gets executed in Mule Runtimes, We CANNOT enforce API policies in Runtime Manager. We would need to do that via API Manager only for a cherry picked instance in an environment.
So, based on these facts, right statement in the given choices is - "The API policy is defined in API Manager for a specific API instance, and then ONLY applied to the specific API instance".
質問 # 37
An online store's marketing team has noticed an increase in customers leaving online baskets without checking out. They suspect a technology issue is at the root cause of the baskets being left behind. They approach the Center for Enablement to ask for help identifying the issue. Multiple APIs from across all the layers of their application network are involved in the shopping application.
Which feature of the Anypoint Platform can be used to view metrics from all involved APIs at the same time?
- A. Functional monitoring
- B. Custom dashboards
- C. API Manager
- D. Built-in dashboards
正解：D
解説：
* Understanding the Need for Cross-API Monitoring:
* The Center for Enablement (C4E) needs to investigate potential technical issues across multiple APIs in the application network that may be causing customers to abandon their carts.
* This requires a solution that allows viewing metrics across several APIs in real-time to identify any performance issues or bottlenecks.
* Evaluating Anypoint Platform Features:
* Built-in Dashboards: Anypoint Platform provides built-in dashboards in Anypoint Monitoring, allowing teams to view metrics from multiple APIs in a single interface. This feature is designed to monitor API performance, latency, errors, and throughput, and is ideal for tracking performance across all layers of the application network.
* Custom Dashboards: While custom dashboards allow for more tailored views, the built-in dashboards already aggregate metrics for multiple APIs, making it unnecessary to build a custom solution for this scenario.
* Functional Monitoring: This feature is used to set up tests to monitor specific API functionality and uptime but is not suited for tracking metrics across multiple APIs in real-time.
* API Manager: API Manager primarily focuses on managing API policies, contracts, and access control rather than providing detailed, real-time metrics across the entire application network.
* Conclusion:
* Option B (Built-in dashboards) is the best choice because it provides a comprehensive view of metrics from all APIs involved, enabling the C4E team to quickly identify any issues that may be contributing to abandoned shopping carts.
Refer to MuleSoft's documentation on Anypoint Monitoring and built-in dashboards for more details on configuring and using these dashboards effectively.
質問 # 38
A Mule application exposes an HTTPS endpoint and is deployed to the CloudHub Shared Worker Cloud. All traffic to that Mule application must stay inside the AWS VPC.
To what TCP port do API invocations to that Mule application need to be sent?
- A. 0
- B. 1
- C. 2
- D. 3
正解：D
解説：
Correct answer: 8082
*****************************************
>> 8091 and 8092 ports are to be used when keeping your HTTP and HTTPS app private to the LOCAL VPC respectively.
>> Above TWO ports are not for Shared AWS VPC/ Shared Worker Cloud.
>> 8081 is to be used when exposing your HTTP endpoint app to the internet through Shared LB
>> 8082 is to be used when exposing your HTTPS endpoint app to the internet through Shared LB So, API invocations should be sent to port 8082 when calling this HTTPS based app.
References:
https://docs.mulesoft.com/runtime-manager/cloudhub-networking-guide
https://help.mulesoft.com/s/article/Configure-Cloudhub-Application-to-Send-a-HTTPS-Request-Directly-to-Another-Cloudhub-Application
https://help.mulesoft.com/s/question/0D52T00004mXXULSA4/multiple-http-listerners-on-cloudhub-one-with-port-9090
質問 # 39
An organization wants to make sure only known partners can invoke the organization's APIs. To achieve this security goal, the organization wants to enforce a Client ID Enforcement policyin API Manager so that only registered partner applications can invoke the organization's APIs. In what type of API implementation does MuleSoft recommend adding an API proxy to enforce the Client ID Enforcement policy, rather than embedding the policy directly in the application's JVM?
- A. A Mule 3 or Mule 4 application modified with custom Java code
- B. A Mule 4 application with an API specification
- C. A Non-Mule application
- D. A Mule 3 application using APIkit
正解：C
解説：
A Non-Mule application
*****************************************
>> All type of Mule applications (Mule 3/ Mule 4/ with APIkit/ with Custom Java Code etc) running on Mule Runtimes support the Embedded Policy Enforcement on them.
>> The only option that cannot have or does not support embedded policy enforcement and must have API Proxy is for Non-Mule Applications.
So, Non-Mule application is the right answer.
質問 # 40
What Mule application can have API policies applied by
Anypoint Platform to the endpoint exposed by that Mule application?
A)A Mule application that accepts requests over HTTP/1.x
B)A Mule application that accepts JSON requests over TCP but is NOT required to provide a response
C)A Mute application that accepts JSON requests over WebSocket
D)A Mule application that accepts gRPC requests over HTTP/2
- A. Option A
- B. Option D
- C. Option C
- D. Option B
正解：A
解説：
Option A
*****************************************
>> Anypoint API Manager and API policies are applicable to all types of HTTP/1.x APIs.
>> They are not applicable to WebSocket APIs, HTTP/2 APIs and gRPC APIs
質問 # 41
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. iPaaS provisioned customer-hosted runtime plane and MuleSoft-hosted control plane
- B. Manually provisioned customer-hosted runtime plane and customer-hosted control plane
- C. Manually provisioned customer-hosted runtime plane and MuleSoft-hosted control plane
- D. MuleSoft-hosted runtime plane and customer-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.
質問 # 42
What correctly characterizes unit tests of Mule applications?
- A. They must be run in a unit testing environment with dedicated Mule runtimes for the environment
- 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 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.
*****************************************
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
質問 # 43
Which two statements are true about the technology architecture of an Anypoint Virtual Private Cloud (VPC)?
Choose 2 answers
- A. Round-robin load balancing is used to distribute client requests across different applications
- B. By default, HTTP requests can be made from the public internet to workers at port 6091
- C. CIDR blacks are used
- D. Anypoint VPC is responsible for load balancing the applications
- E. Ports 8081 and 8082 are used
正解：B、C
解説：
An Anypoint Virtual Private Cloud (VPC) provides a secure and private networking environment for MuleSoft applications, using specific architectural elements:
* CIDR Blocks:
* Anypoint VPCs utilize CIDR blocks to define IP ranges, allowing organizations to control and segment the VPC's IP address space.
* Port 6091 for HTTP Requests:
* By default, HTTP requests can be made to workers on port 6091 from the public internet, providing an accessible entry point unless additional restrictions are applied.
* Explanation of Correct Answers (B, E):
* CIDR blocks enable IP range management for VPCs, and port 6091 is the default public entry port, which is part of Anypoint VPC's default settings.
* Explanation of Incorrect Options:
* Option A (Ports 8081 and 8082) is incorrect; these are not default public ports for Anypoint VPC.
* Option C (responsible for load balancing) is incorrect as load balancing requires a separate Dedicated Load Balancer (DLB).
* Option D (round-robin load balancing) applies to DLBs, not directly to VPCs.
ReferencesFor more on VPC setup and networking, refer to MuleSoft documentation on VPC configurations and default port settings.
質問 # 44
What best explains the use of auto-discovery in API implementations?
- A. It enables Anypoint Studio to discover API definitions configured in Anypoint Platform
- B. It enables Anypoint Exchange to discover assets and makes them available for reuse
- C. It makes API Manager aware of API implementations and hence enables it to enforce policies
- D. It enables Anypoint Analytics to gain insight into the usage of APIs
正解：C
解説：
Correct answer: It makes API Manager aware of API implementations and hence enables it to enforce policies.
*****************************************
>> API Autodiscovery is a mechanism that manages an API from API Manager by pairing the deployed application to an API created on the platform.
>> API Management includes tracking, enforcing policies if you apply any, and reporting API analytics.
>> Critical to the Autodiscovery process is identifying the API by providing the API name and version.
References:
https://docs.mulesoft.com/api-manager/2.x/api-auto-discovery-new-concept
https://docs.mulesoft.com/api-manager/1.x/api-auto-discovery
https://docs.mulesoft.com/api-manager/2.x/api-auto-discovery-new-concept
質問 # 45
What is true about the technology architecture of Anypoint VPCs?
- A. Traffic between Mule applications deployed to an Anypoint VPC and on-premises systems can stay within a private network
- B. VPC peering can be used to link the underlying AWS VPC to an on-premises (non AWS) private network
- C. The private IP address range of an Anypoint VPC is automatically chosen by CloudHub
- D. Each CloudHub environment requires a separate Anypoint VPC
正解：A
解説：
Traffic between Mule applications deployed to an Anypoint VPC and on-premises systems can stay within a private network
*****************************************
>> The private IP address range of an Anypoint VPC is NOT automatically chosen by CloudHub. It is chosen by us at the time of creating VPC using thr CIDR blocks.
CIDR Block: The size of the Anypoint VPC in Classless Inter-Domain Routing (CIDR) notation.
For example, if you set it to 10.111.0.0/24, the Anypoint VPC is granted 256 IP addresses from 10.111.0.0 to
10.111.0.255.
Ideally, the CIDR Blocks you choose for the Anypoint VPC come from a private IP space, and should not overlap with any other Anypoint VPC's CIDR Blocks, or any CIDR Blocks in use in your corporate network.
that each CloudHub environment requires a separate Anypoint VPC. Once an Anypoint VPC is created, we can choose a same VPC by multiple environments. However, it is generally a best and recommended practice to always have seperate Anypoint VPCs for Non-Prod and Prod environments.
>> We use Anypoint VPN to link the underlying AWS VPC to an on-premises (non AWS) private network.
NOT VPC Peering.
質問 # 46
In which layer of API-led connectivity, does the business logic orchestration reside?
- A. System Layer
- B. Process Layer
- C. Experience Layer
正解：B
解説：
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.
質問 # 47
What Anypoint Platform Capabilities listed below fall under APIs and API Invocations/Consumers category?
Select TWO.
- A. API Design and Development
- B. API Operations and Management
- C. API Runtime Execution and Hosting
- D. API Consumer Engagement
正解：A
解説：
Correct Answers: API Design and Development and API Runtime Execution and Hosting
*****************************************
>> 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
Explanation:
Correct Answers: API Operations and Management and 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
Bottom of Form
Top of Form
質問 # 48
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 an SLA-based rate limiting policy and assign a client application to a matching SLA tier based on its type
- B. Use a spike control policy that limits the number of requests for each client application type
- C. Use a cross-origin resource sharing (CORS) policy to limit resource sharing between client applications, configured by the client application type
- D. Use a rate limiting policy and a client ID enforcement policy, each configured by the client application type
正解：A
質問 # 49
......
MCPA-Level-1試験は、複数選択問題の知識テストと実践的なラボ試験に分かれています。複数選択テストは、MuleSoftのアーキテクチャ、データ統合、API管理、セキュリティなどのトピックをカバーしています。実践的なラボ試験では、候補者は与えられたシナリオに基づいてMuleSoftアプリケーションを構築する必要があります。ラボ試験は、候補者がAnypoint Studio、つまりMuleSoftの開発環境を使用してMuleSoftアプリケーションを設計および構築する能力を評価します。
MCPA-LEVEL-1認定試験は、Mulesoftのプラットフォームアーキテクチャにおける個人の習熟度の包括的な評価です。これは、統合でキャリアを促進しようとしている人にとって貴重な認証であり、資格のあるMuleSoftの専門家を特定するための信頼できる方法を組織に提供します。
Mulesoft MCPA-LEVEL-1（Mulesoft Certified Platform Architect-Level 1）認定試験は、MulesoftのAnyPointプラットフォームを使用して統合ソリューションの設計と構築に関する個人の専門知識を評価するために設計されたテストです。この認定は、Mulesoftのプラットフォームを深く理解し、複雑な統合プロジェクトを設計および実装できる経験豊富な建築家向けです。
MCPA-Level-1試験問題集でPDF問題とテストエンジン：https://www.jpntest.com/shiken/MCPA-Level-1-mondaishu