MCIA-Level-1問題集と練習テスト（246問題） [Q113-Q137]

（2023)MCIA-Level-1問題集と練習テスト（246問題)

ガイド（2023年最新)リアルなMuleSoft MCIA-Level-1試験問題

Mulesoftは、統合ソフトウェアを専門とする大手ソフトウェア会社です。同社のソフトウェアであるMuleは、開発者がアプリケーション、データ、デバイスを接続できる軽量のオープンソース統合フレームワークです。ラバを使用すると、開発者はカスタムコードを作成することなく、迅速かつ簡単に統合を構築できます。 Mulesoftは、専門家がMuleを使用するために必要なスキルと知識を確保するために、Mulesoft Certified Integration Architect-レベル1（MCIA-LEVEL-1）試験など、いくつかの認定試験を提供しています。

MCIA-LEVEL-1試験は、ラバアプリケーションの設計、構築、管理の経験がある専門家向けに設計されています。試験では、MulesoftのAnyPointプラットフォームに関する候補者の理解をテストします。これには、ラバアプリケーションを設計および展開し、APIを構成および管理し、一般的な問題のトラブルシューティングを行う機能が含まれます。 MCIA-Level-1試験は、統合アーキテクチャ、開発、展開など、幅広いトピックをカバーする包括的な試験です。 MCIA-Level-1試験に合格することで、専門家はMulesoftのAnyPointプラットフォームで専門知識を実証し、統合業界でのキャリアの見通しを強化できます。

MuleSoft MCIA-Level-1 試験は、60問からなる選択式の試験です。候補者には120分間が与えられ、合格には70％以上のスコアが必要です。この試験は、英語、日本語、簡体字中国語の3つの言語で提供されています。

 

質問 # 113
An organization's security policies mandate complete control of the login credentials used to log in to Anypoint Platform. What feature of Anypoint Platform should be used to meet this requirement?

• A. Federated Identity Management
• B. Federated Client Management
• C. Client ID Secret
• D. Enterprise Security Module

正解：A

質問 # 114
An organization has deployed both Mule and non-Mule API implementations to integrate its customer and order management systems. All the APIs are available to REST clients on the public internet.
The organization wants to monitor these APIs by running health checks: for example, to determine if an API can properly accept and process requests. The organization does not have subscriptions to any external monitoring tools and also does not want to extend its IT footprint.
What Anypoint Platform feature provides the most idiomatic (used for its intended purpose) way to monitor the availability of both the Mule and the non-Mule API implementations?

• A. Anypoint Visualizer
• B. API Functional Monitoring
• C. Runtime Manager
• D. API Manager

正解：A

質問 # 115
Refer to the exhibit.

A shopping cart checkout process consists of a web store backend sending a sequence of API invocations to an Experience API, which in turn invokes a Process API. All API invocations are over HTTPS POST. The Java web store backend executes in a Java EE application server, while all API implementations are Mule applications executing in a customer -hosted Mule runtime.
End-to-end correlation of all HTTP requests and responses belonging to each individual checkout Instance is required. This is to be done through a common correlation ID, so that all log entries written by the web store backend, Experience API implementation, and Process API implementation include the same correlation ID for all requests and responses belonging to the same checkout instance.
What is the most efficient way (using the least amount of custom coding or configuration) for the web store backend and the implementations of the Experience API and Process API to participate in end-to-end correlation of the API invocations for each checkout instance?
A)
The web store backend, being a Java EE application, automatically makes use of the thread-local correlation ID generated by the Java EE application server and automatically transmits that to the Experience API using HTTP-standard headers No special code or configuration is included in the web store backend, Experience API, and Process API implementations to generate and manage the correlation ID

B)
The web store backend generates a new correlation ID value at the start of checkout and sets it on the X-CORRELATlON-lt HTTP request header In each API invocation belonging to that checkout No special code or configuration is included in the Experience API and Process API implementations to generate and manage the correlation ID

C)
The Experience API implementation generates a correlation ID for each incoming HTTP request and passes it to the web store backend in the HTTP response, which includes it in all subsequent API invocations to the Experience API.
The Experience API implementation must be coded to also propagate the correlation ID to the Process API in a suitable HTTP request header

D)
The web store backend sends a correlation ID value in the HTTP request body In the way required by the Experience API The Experience API and Process API implementations must be coded to receive the custom correlation ID In the HTTP requests and propagate It in suitable HTTP request headers

• A. Option A
• B. Option C
• C. Option D
• D. Option B

正解：D

質問 # 116
What is maximum vCores can be allocated to application deployed to CloudHub?

• A. 16 vCores
• B. 1 vCores
• C. 2 vCores
• D. 4 vCores

正解：A

質問 # 117
A Mule application is being designed To receive nightly a CSV file containing millions of records from an external vendor over SFTP, The records from the file need to be validated, transformed. And then written to a database. Records can be inserted into the database in any order.
In this use case, what combination of Mule components provides the most effective and performant way to write these records to the database?

• A. Use a Scatter-Gather to bulk insert records into the database
• B. Use a Parallel for Each scope to Insert records one by one into the database
• C. Use a Batch job scope to bulk insert records into the database.
• D. Use a DataWeave map operation and an Async scope to insert records one by one into the database.

正解：C

解説：
Correct answer is Use a Batch job scope to bulk insert records into the database
* Batch Job is most efficient way to manage millions of records.
A few points to note here are as follows :
Reliability: If you want reliabilty while processing the records, i.e should the processing survive a runtime crash or other unhappy scenarios, and when restarted process all the remaining records, if yes then go for batch as it uses persistent queues.
Error Handling: In Parallel for each an error in a particular route will stop processing the remaining records in that route and in such case you'd need to handle it using on error continue, batch process does not stop during such error instead you can have a step for failures and have a dedicated handling in it.
Memory footprint: Since question said that there are millions of records to process, parallel for each will aggregate all the processed records at the end and can possibly cause Out Of Memory.
Batch job instead provides a BatchResult in the on complete phase where you can get the count of failures and success. For huge file processing if order is not a concern definitely go ahead with Batch Job

質問 # 118
An API client makes an HTTP request to an API gateway with an Accept header containing the value'' application''.
What is a valid HTTP response payload for this request in the client requested data format?

• A. <status>healthy</status>
• B. {"status" "healthy"}
• C. status: healthy
• D. status('healthy")

正解：B

質問 # 119
What operation can be performed through a JMX agent enabled in a Mule application?

• A. Deploy a Mule application
• B. Replay an unsuccessful message
• C. View object store entries
• D. Set a particular tog4J2 log level to TRACE

正解：C

質問 # 120
The ABC company has an Anypoint Runtime Fabric on VMs/Bare Metal (RTF-VM) appliance installed on its own customer-hosted AWS infrastructure.
Mule applications are deployed to this RTF-VM appliance. As part of the company standards, the Mule application logs must be forwarded to an external log management tool (LMT).
Given the company's current setup and requirements, what is the most idiomatic (used for its intended purpose) way to send Mule application logs to the external LMT?

• A. In each Mule application, configure custom Log4j settings
• B. In RTF-VM, install and configure the external LTM's log-forwarding agent
• C. In RTF-VM. configure the out-of-the-box external log forwarder
• D. In RTF-VM, edit the pod configuration to automatically install and configure an Anypoint Monitoring agent

正解：B

質問 # 121
A marketing organization is designing a Mule application to process campaign dat a. The Mule application will periodically check for a file in a SFTP location and process the records in the file. The size of the file can vary from 10MB to 5GB. Due to the limited availabiltty of vCores, the Mule application is deployed to a single CloudHub worker configured with vCore size 0.2.
The application must transform and send different formats of this file to three different downstream SFTP locations.
What is the most idiomatic (used for its intended purpose) and performant way to configure the SFTP operations or event sources to process the large files to support these deployment requirements?

• A. Use an in-memory repeatable stream
• B. Use a file-stored non-repeatable stream
• C. Use an in-memory non-repeatable stream
• D. Use a file-stored repeatable stream

正解：A

質問 # 122
A team would like to create a project skeleton that developers can use as a starting point when creating API Implementations with Anypoint Studio. This skeleton should help drive consistent use of best practices within the team.
What type of Anypoint Exchange artifact(s) should be added to Anypoint Exchange to publish the project skeleton?

• A. An example of an API implementation following best practices
• B. A custom asset with the default API implementation
• C. A RAML archetype and reusable trait definitions to be reused across API implementations
• D. a Mule application template with the key components and minimal integration logic

正解：D

解説：
* Sharing Mule applications as templates is a great way to share your work with other people who are in your organization in Anypoint Platform. When they need to build a similar application they can create the mule application using the template project from Anypoint studio.
* Anypoint Templates are designed to make it easier and faster to go from a blank canvas to a production application. They're bit for bit Mule applications requiring only Anypoint Studio to build and design, and are deployable both on-premises and in the cloud.
* Anypoint Templates are based on five common data Integration patterns and can be customized and extended to fit your integration needs. So even if your use case involves different endpoints or connectors than those included in the template, they still offer a great starting point.
Some of the best practices while creating the template project: - Define the common error handler as part of template project, either using pom dependency or mule config file - Define common logger/audit framework as part of the template project - Define the env specific properties and secure properties file as per the requirement - Define global.xml for global configuration - Define the config file for connector configuration like Http,Salesforce,File,FTP etc - Create separate folders to create DWL,Properties,SSL certificates etc - Add the dependency and configure the pom.xml as per the business need - Configure the mule-artifact.json as per the business need

質問 # 123
An organization uses a set of customer-hosted Mule runtimes that are managed using the Mulesoft-hosted control plane. What is a condition that can be alerted on from Anypoint Runtime Manager without any custom components or custom coding?

• A. When an SSL certificate used by one of the deployed Mule applications is about to expire
• B. When a Mule runtime's customer-hosted server is about to run out of disk space
• C. When the Mute runtime license installed on a Mule runtime is about to expire
• D. When a Mule runtime on a given customer-hosted server is experiencing high memory consumption during certain periods

正解：D

解説：
Correct answer is When a Mule runtime on a given customer-hosted server is experiencing high memory consumption during certain periods Using Anypoint Monitoring, you can configure two different types of alerts: Basic alerts for servers and Mule apps Limit per organization: Up to 50 basic alerts for users who do not have a Titanium subscription to Anypoint Platform You can set up basic alerts to trigger email notifications when a metric you are measuring passes a specified threshold. You can create basic alerts for the following metrics for servers or Mule apps: For on-premises servers and CloudHub apps: * CPU utilization * Memory utilization * Thread count Advanced alerts for graphs in custom dashboards in Anypoint Monitoring. You must have a Titanium subscription to use this feature. Limit per organization: Up to 20 advanced alerts

質問 # 124
An Order microservice and a Fulfillment microservice are being designed to communicate with their dients through message-based integration (and NOT through API invocations).
The Order microservice publishes an Order message (a kind of command message) containing the details of an order to be fulfilled. The intention is that Order messages are only consumed by one Mute application, the Fulfillment microservice.
The Fulfilment microservice consumes Order messages, fulfills the order described therein, and then publishes an OrderFulfilted message (a kind of event message). Each OrderFulfilted message can be consumed by any interested Mule application, and the Order microservice is one such Mute application.
What is the most appropriate choice of message broker(s) and message destination(s) in this scenario?

• A. Order messages are sent to a JMS queue. OrderFulfilled messages are sent to a JMS topic Both microservices interact with the same JMS provider (message broker) instance, which must therefore scale to support the load of both microservices
• B. Order messages are sent directly to the Fulfillment microservices. OrderFulfilled messages are sent directly to the Order microservice The Order microservice interacts with one AMQP-compatible message broker and the Fulfillment microservice interacts with a different AMQP-compatible message broker, so that both message brokers can be chosen and scaled to best support the load of each microservice
• C. Order messages are sent to an Anypoint MQ exchange OrderFulfilled messages are sent to an Anypoint MQ queue Both microservices interact with Anypoint MQ as the message broker, which must therefore scale to support the load of both microservices
• D. Order messages are sent to a JMS queue. OrderFulfilled messages are sent to a JMS topic The Order microservice interacts with one JMS provider (message broker) and the Fulfillment microservice interacts with a different JMS provider, so that both message brokers can be chosen and scaled to best support the load of each microservice

正解：A

解説：
* If you need to scale a JMS provider/ message broker, - add nodes to scale it horizontally or - add memory to scale it vertically
* Cons of adding another JMS provider/ message broker: - adds cost. - adds complexity to use two JMS brokers - adds Operational overhead if we use two brokers, say, ActiveMQ and IBM MQ
* So Two options that mention to use two brokers are not best choice. * It's mentioned that "The Fulfillment microservice consumes Order messages, fulfills the order described therein, and then publishes an OrderFulfilled message. Each OrderFulfilled message can be consumed by any interested Mule application."
- When you publish a message on a topic, it goes to all the subscribers who are interested - so zero to many subscribers will receive a copy of the message.
- When you send a message on a queue, it will be received by exactly one consumer. * As we need multiple consumers to consume the message below option is not valid choice: "Order messages are sent to an Anypoint MQ exchange. OrderFulfilled messages are sent to an Anypoint MQ queue.
Both microservices interact with Anypoint MQ as the message broker, which must therefore scale to support the load of both microservices" * Order messages are only consumed by one Mule application, the Fulfillment microservice, so we will publish it on queue and OrderFulfilled message can be consumed by any interested Mule application so it need to be published on Topic using same broker.
* Correct:

質問 # 125
Refer to the exhibit.
A Mule application is being designed to expose a SOAP web service to its clients.
What language is typically used inside the web service's interface definition to define the data structures that the web service Is expected to exchange with its clients?

• A. JSON Schema
• B. RAMI
• C. WSDL
• D. XSD

正解：C

質問 # 126
According to MuleSoft, what Action should an IT organization take regarding its technology assets in order to close the IT delivery.

• A. Make assets easily discoverable via a central repository
• B. Create weekly meetings that all members of IT attend to present justification and request approval to use existing assets
• C. Hire additional staff to meet the demand for asset creation required for approved projects and timelines
• D. Focus project delivery efforts on custom assets that meet the specific requirements of each individual line of business

正解：D

質問 # 127
An Integration Mule application is being designed to synchronize customer data between two systems. One system is an IBM Mainframe and the other system is a Salesforce Marketing Cloud (CRM) instance. Both systems have been deployed in their typical configurations, and are to be invoked using the native protocols provided by Salesforce and IBM.
What interface technologies are the most straightforward and appropriate to use in this Mute application to interact with these systems, assuming that Anypoint Connectors exist that implement these interface technologies?

• A. IBM: DB access CRM:gRPC
• B. IBM: ActiveMQ CRM: REST
• C. IBM:QCS CRM: SOAP
• D. IBM: REST CRM:REST

正解：A

質問 # 128
An Order microservice and a Fulfillment microservice are being designed to communicate with their dients through message-based integration (and NOT through API invocations).
The Order microservice publishes an Order message (a kind of command message) containing the details of an order to be fulfilled. The intention is that Order messages are only consumed by one Mute application, the Fulfillment microservice.
The Fulfilment microservice consumes Order messages, fulfills the order described therein, and then publishes an OrderFulfilted message (a kind of event message). Each OrderFulfilted message can be consumed by any interested Mule application, and the Order microservice is one such Mute application.
What is the most appropriate choice of message broker(s) and message destination(s) in this scenario?

• A. Older messages are sent directly to the Fulfillment microservices
  OrderFulfilled messages are sent directly to the Order microservice
  The Order microservice Interacts with one AMQP-compatible message broker and the Fulfillment microservice Interacts with a different AMQP-compatible message broker, so that both message brokers can be chosen and scaled to best support the toad each microservice
• B. Order messages are sent to an Anypoint MQ exchange
  OrderFulfilted messages are sent to an Anypoint MQ queue
  Both microservices interact with Anypoint MQ as the message broker, which must therefore scale to support the toad of both microservices
• C. Order messages are sent to a JMS queue OrderFulfilled messages are sent to a JMS topic The Order microservice Interacts with one JMS provider (message broker) and the Fulfillment microservice interacts with a different JMS provider, so that both message brokers can be chosen and scaled to best support the load of each microservice
• D. Order messages are sent to a JMS queue OrderFulfilled messages are sent to a JMS topic Both microservices Interact with the same JMS provider (message broker) Instance, which must therefore scale to support the load of both microservices

正解：C

質問 # 129
Refer to the exhibit.

A Mule 4 application has a parent flow that breaks up a JSON array payload into 200 separate items, then sends each item one at a time inside an Async scope to a VM queue.
A second flow to process orders has a VM Listener on the same VM queue. The rest of this flow processes each received item by writing the item to a database.
This Mule application is deployed to four CloudHub workers with persistent queues enabled.
What message processing guarantees are provided by the VM queue and the CloudHub workers, and how are VM messages routed among the CloudHub workers for each invocation of the parent flow under normal operating conditions where all the CloudHub workers remain online?

• A. ALL Item VM messages are processed AT LEAST ONCE by the SAME CloudHub worker where the parent flow was invoked This one CloudHub worker processes ALL 200 item VM messages
• B. EACH item VM message is processed AT MOST ONCE by ONE CloudHub worker, with workers chosen in a deterministic round-robin fashion Each of the four CloudHub workers can be expected to process 1/4 of the Item VM messages (about 50 items)
• C. ALL item VM messages are processed AT MOST ONCE by ONE ARBITRARY CloudHub worker This one CloudHub worker processes ALL 200 item VM messages
• D. EACH item VM message is processed AT LEAST ONCE by ONE ARBITRARY CloudHub worker Each of the four CloudHub workers can be expected to process some item VM messages

正解：D

質問 # 130
A Mule application currently writes to two separate SQL Server database instances across the internet using a single XA transaction. It is proposed to split this one transaction into two separate non-XA transactions with no other changes to the Mule application.
What non-functional requirement can be expected to be negatively affected when implementing this change?

• A. Consistency
• B. Throughput
• C. Availability
• D. Response time

正解：A

質問 # 131
During a planning session with the executive leadership, the development team director presents plans for a new API to expose the data in the company's order database. An earlier effort to build an API on top of this data failed, so the director is recommending a design-first approach.
Which characteristics of a design-first approach will help make this API successful?

• A. Building MUnit tests so administrators can confirm code coverage percentage during deployment
• B. Developing a specification so consumers can test before the implementation is built
• C. Publishing the fully implemented API to Exchange so all developers can reuse the API
• D. Adding global policies to the API so all developers automatically secure the implementation before coding anything

正解：B

質問 # 132
An API has been unit tested and is ready for integration testing. The API is governed by a Client ID Enforcement policy in all environments.
What must the testing team do before they can start integration testing the API in the Staging environment?

• A. They must access the API portal and create an API notebook using the Client ID and Client Secret supplied by the API portal in the Staging environment
• B. They must request access to the API instance in the Staging environment and obtain a Client ID and Client Secret to be used for testing the API
• C. They must be assigned as an API version owner of the API in the Staging environment
• D. They must request access to the Staging environment and obtain the Client ID and Client Secret for that environment to be used for testing the API

正解：B

解説：
* It's mentioned that the API is governed by a Client ID Enforcement policy in all environments.
* Client ID Enforcement policy allows only authorized applications to access the deployed API implementation.
* Each authorized application is configured with credentials: client_id and client_secret.
* At runtime, authorized applications provide the credentials with each request to the API implementation.
MuleSoft Reference: https://docs.mulesoft.com/api-manager/2.x/policy-mule3-client-id-based-policies

質問 # 133
Refer to the exhibit.

This Mule application is deployed to multiple Cloudhub workers with persistent queue enabled. The retrievefile flow event source reads a CSV file from a remote SFTP server and then publishes each record in the CSV file to a VM queue. The processCustomerRecords flow's VM Listner receives messages from the same VM queue and then processes each message separately.
How are messages routed to the cloudhub workers as messages are received by the VM Listener?

• A. Each message is routed to ONE of the Cloudhub workers in a DETERMINSTIC round robin fashion thereby EXACTLY BALANCING messages among the cloudhub workers
• B. Each messages routes to ONE of the available Clouhub workers in a NON- DETERMINSTIC non round-robin fashion thereby APPROXIMATELY BALANCING messages among the cloudhub workers
• C. Each message is routed to the SAME Cloudhub worker that retrieved the file, thereby BINDING ALL messages to ONLY that ONE Cloudhub worker
• D. Each message is duplicated to ALL of the Cloudhub workers, thereby SHARING EACH message with ALL the Cloudhub workers.

正解：B

質問 # 134
A MuteSoft developer must implement an API as a Mule application, run the application locally, and execute unit tests against the Running application.
Which Anypoint Platform component can the developer use to full all of these requirements?

• A. Anypoint Studio
• B. Anypoint CLI
• C. API Designer
• D. API Manager

正解：A

質問 # 135
Refer to the exhibit.

A shopping cart checkout process consists of a web store backend sending a sequence of API invocations to an Experience API, which in turn invokes a Process API. All API invocations are over HTTPS POST. The Java web store backend executes in a Java EE application server, while all API implementations are Mule applications executing in a customer -hosted Mule runtime.
End-to-end correlation of all HTTP requests and responses belonging to each individual checkout Instance is required. This is to be done through a common correlation ID, so that all log entries written by the web store backend, Experience API implementation, and Process API implementation include the same correlation ID for all requests and responses belonging to the same checkout instance.
What is the most efficient way (using the least amount of custom coding or configuration) for the web store backend and the implementations of the Experience API and Process API to participate in end-to-end correlation of the API invocations for each checkout instance?

• A. The web store backend sends a correlation ID value in the HTTP request body In the way required by the Experience API The Experience API and Process API implementations must be coded to receive the custom correlation ID In the HTTP requests and propagate It in suitable HTTP request headers
• B. The Experience API implementation generates a correlation ID for each incoming HTTP request and passes it to the web store backend in the HTTP response, which includes it in all subsequent API invocations to the Experience API.
  The Experience API implementation must be coded to also propagate the correlation ID to the Process API in a suitable HTTP request header
• C. The web store backend, being a Java EE application, automatically makes use of the thread-local correlation ID generated by the Java EE application server and automatically transmits that to the Experience API using HTTP-standard headers No special code or configuration is included in the web store backend, Experience API, and Process API implementations to generate and manage the correlation ID
• D. The web store backend generates a new correlation ID value at the start of checkout andsets it on the X-CORRELATlON-ltHTTP request header In each API invocation belonging to that checkout No special code or configuration is included in the Experience API and Process API implementations to generate and manage the correlation ID

正解：D

質問 # 136
A travel company wants to publish a well-defined booking service API to be shared with its business partners. These business partners have agreed to ONLY consume SOAP services and they want to get the service contracts in an easily consumable way before they start any development. The travel company will publish the initial design documents to Anypoint Exchange, then share those documents with the business partners. When using an API-led approach, what is the first design document the travel company should deliver to its business partners?

• A. Create a RAML API specification using any text editor
• B. Create a SOAP API specification in Design Center
• C. Create a WSDL specification using any XML editor
• D. Create an OAS API specification in Design Center

正解：C

解説：
SOAP API specifications are provided as WSDL. Design center doesn't provide the functionality to create WSDL file. Hence WSDL needs to be created using XML editor

質問 # 137
......

MCIA-Level-1試験問題集パスできる2023年最新の認証された試験問題：https://jp.fast2test.com/MCIA-Level-1-premium-file.html