2022年06月23日に更新された最新のリアルMCPA-Level-1問題集でMCPA-Level-1試験問題 [Q58-Q75]

4.6/5 - (5 votes)

2022年06月23日に更新された最新のPassTest MCPA-Level-1試験問題リアルMCPA-Level-1問題集で

MCPA-Level-1別格な問題集で最上級の成績にさせるMCPA-Level-1問題

MuleSoft MCPA-Level-1 認定試験の出題範囲：

トピック	出題範囲
トピック 1	対応するRAML定義で必要な変更を特定します Anypointプラットフォームの機能と高レベルのコンポーネントを説明します
トピック 2	メジャーバージョンのインクリメントを必要とする、または必要としないAPIへの変更を特定する「最新のAPI \|」の役割と特性を説明する
トピック 3	所有権、機能の焦点、変更率に応じてAPIをレイヤーに割り当てます Center forEnablementの目的と役割を説明します
トピック 4	APIマネージャーによる管理に適しているまたは対応していないAPIおよびその他のリモートインターフェイスのタイプを特定します IT配信のギャップを埋めるためのMuleSoftの提案を説明します
トピック 5	べき等HTTPメソッドと楽観的同時実行性のHTTPネイティブサポートを特定する API主導の接続とアプリケーションネットワークの利点を定義して説明する
トピック 6	API呼び出しの非同期実行が必要な場合は、ポーリングまたはコールバックを適切に使用するタイミングを選択します API、API実装、APIクライアント、APIコンシューマー、およびAPI呼び出しという用語を正しく使用します

新問題 58
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

Option A

Option B

Option C

Option D

新問題 59
What CANNOT be effectively enforced using an API policy in Anypoint Platform?

Guarding against Denial of Service attacks

Maintaining tamper-proof credentials between APIs

Logging HTTP requests and responses

Backend system overloading

新問題 60
An API implementation is updated. When must the RAML definition of the API also be updated?

When the API implementation changes the structure of the request or response messages

When the API implementation changes from interacting with a legacy backend system deployed on-premises to a modern, cloud-based (SaaS) system

When the API implementation is migrated from an older to a newer version of the Mule runtime

When the API implementation is optimized to improve its average response time

新問題 61
A System API is designed to retrieve data from a backend system that has scalability challenges.
What API policy can best safeguard the backend system?

IP whitelist

SLA-based rate limiting

OAuth 2 token enforcement

Client ID enforcement

新問題 62
An organization uses various cloud-based SaaS systems and multiple on-premises systems. The on-premises systems are an important part of the organization’s application network and can only be accessed from within the organization’s intranet.
What is the best way to configure and use Anypoint Platform to support integrations with both the cloud-based SaaS systems and on-premises systems?
A) Use CloudHub-deployed Mule runtimes in an Anypoint VPC managed by Anypoint Platform Private Cloud Edition control plane

B) Use CloudHub-deployed Mule runtimes in the shared worker cloud managed by the MuleSoft-hosted Anypoint Platform control plane

C) Use an on-premises installation of Mule runtimes that are completely isolated with NO external network access, managed by the Anypoint Platform Private Cloud Edition control plane

D) Use a combination of Cloud Hub-deployed and manually provisioned on-premises Mule runtimes managed by the MuleSoft-hosted Anypoint Platform control plane

Option A

Option B

Option C

Option D

新問題 63
What API policy would be LEAST LIKELY used when designing an Experience API that is intended to work with a consumer mobile phone or tablet application?

OAuth 2.0 access token enforcement

Client ID enforcement

JSON threat protection

IPwhitellst

新問題 64
An API implementation is being designed that must invoke an Order API, which is known to repeatedly experience downtime.
For this reason, a fallback API is to be called when the Order API is unavailable.
What approach to designing the invocation of the fallback API provides the best resilience?

Search Anypoint Exchange for a suitable existing fallback API, and then implement invocations to this fallback API in addition to the Order API

Create a separate entry for the Order API in API Manager, and then invoke this API as a fallback API if the primary Order API is unavailable

Redirect client requests through an HTTP 307 Temporary Redirect status code to the fallback API whenever the Order API is unavailable

Set an option in the HTTP Requester component that invokes the Order API to instead invoke a fallback API whenever an HTTP 4xx or 5xx response status code is returned from the Order API

新問題 65
An organization wants MuleSoft-hosted runtime plane features (such as HTTP load balancing, zero downtime, and horizontal and vertical scaling) in its Azure environment. What runtime plane minimizes the organization’s effort to achieve these features?

Anypoint Runtime Fabric

Anypoint Platform for Pivotal Cloud Foundry

CloudHub

A hybrid combination of customer-hosted and MuleSoft-hosted Mule runtimes

新問題 66
An API has been updated in Anypoint Exchange by its API producer from version 3.1.1 to 3.2.0 following accepted semantic versioning practices and the changes have been communicated via the API’s public portal.
The API endpoint does NOT change in the new version.
How should the developer of an API client respond to this change?

The update should be identified as a project risk and full regression testing of the functionality that uses this API should be run

The API producer should be contacted to understand the change to existing functionality

The API producer should be requested to run the old version in parallel with the new one

The API client code ONLY needs to be changed if it needs to take advantage of new features

新問題 67
An organization uses various cloud-based SaaS systems and multiple on-premises systems. The on-premises systems are an important part of the organization’s application network and can only be accessed from within the organization’s intranet.
What is the best way to configure and use Anypoint Platform to support integrations with both the cloud-based SaaS systems and on-premises systems?
A) Use CloudHub-deployed Mule runtimes in an Anypoint VPC managed by Anypoint Platform Private Cloud Edition control plane

B) Use CloudHub-deployed Mule runtimes in the shared worker cloud managed by the MuleSoft-hosted Anypoint Platform control plane

C) Use an on-premises installation of Mule runtimes that are completely isolated with NO external network access, managed by the Anypoint Platform Private Cloud Edition control plane

D) Use a combination of Cloud Hub-deployed and manually provisioned on-premises Mule runtimes managed by the MuleSoft-hosted Anypoint Platform control plane

Option A

Option B

Option C

Option D

新問題 68
The responses to some HTTP requests can be cached depending on the HTTP verb used in the request.
According to the HTTP specification, for what HTTP verbs is this safe to do?

PUT, POST, DELETE

GET, HEAD, POST

GET, PUT, OPTIONS

GET, OPTIONS, HEAD

新問題 69
What is most likely NOT a characteristic of an integration test for a REST API implementation?

The test needs all source and/or target systems configured and accessible

The test runs immediately after the Mule application has been compiled and packaged

The test is triggered by an external HTTP request

The test prepares a known request payload and validates the response payload

新問題 70
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?

Enable mocking services for each of the relevant APIs and expose them via their Anypoint Exchange entry

Ensure the APIs are well documented through their Anypoint Exchange entries and API Consoles and share these pages with all API consumers

Create API Notebooks and include them in the relevant Anypoint Exchange entries

Make relevant APIs discoverable via an Anypoint Exchange entry

新問題 71
An Order API must be designed that contains significant amounts of integration logic and involves the invocation of the Product API.
The power relationship between Order API and Product API is one of “Customer/Supplier”, because the Product API is used heavily throughout the organization and is developed by a dedicated development team located in the office of the CTO.
What strategy should be used to deal with the API data model of the Product API within the Order API?

Convince the development team of the Product API to adopt the API data model of the Order API such that the integration logic of the Order API can work with one consistent internal data model

Work with the API data types of the Product API directly when implementing the integration logic of the Order API such that the Order API uses the same (unchanged) data types as the Product API

Implement an anti-corruption layer in the Order API that transforms the Product API data model into internal data types of the Order API

Start an organization-wide data modeling initiative that will result in an Enterprise Data Model that will then be used in both the Product API and the Order API

新問題 72
What should be ensured before sharing an API through a public Anypoint Exchange portal?

The visibility level of the API instances of that API that need to be publicly accessible should be set to public visibility

The users needing access to the API should be added to the appropriate role in Anypoint Platform

The API should be functional with at least an initial implementation deployed and accessible for users to interact with

The API should be secured using one of the supported authentication/authorization mechanisms to ensure that data is not compromised

新問題 73
Refer to the exhibit. An organization is running a Mule standalone runtime and has configured Active Directory as the Anypoint Platform external Identity Provider. The organization does not have budget for other system components.

What policy should be applied to all instances of APIs in the organization to most effecuvelyKestrict access to a specific group of internal users?

Apply a basic authentication – LDAP policy; the internal Active Directory will be configured as the LDAP source for authenticating users

Apply a client ID enforcement policy; the specific group of users will configure their client applications to use their specific client credentials

Apply an IP whitelist policy; only the specific users’ workstations will be in the whitelist

Apply an OAuth 2.0 access token enforcement policy; the internal Active Directory will be configured as the OAuth server

新問題 74
Refer to the exhibit.

Three business processes need to be implemented, and the implementations need to communicate with several different SaaS applications.
These processes are owned by separate (siloed) LOBs and are mainly independent of each other, but do share a few business entities. Each LOB has one development team and their own budget In this organizational context, what is the most effective approach to choose the API data models for the APIs that will implement these business processes with minimal redundancy of the data models?
A) Build several Bounded Context Data Models that align with coherent parts of the business processes and the definitions of associated business entities

B) Build distinct data models for each API to follow established micro-services and Agile API-centric practices

C) Build all API data models using XML schema to drive consistency and reuse across the organization

D) Build one centralized Canonical Data Model (Enterprise Data Model) that unifies all the data types from all three business processes, ensuring the data model is consistent and non-redundant

Option A

Option B

Option C

Option D

新問題 75
An organization makes a strategic decision to move towards an IT operating model that emphasizes consumption of reusable IT assets using modern APIs (as defined by MuleSoft).
What best describes each modern API in relation to this new IT operating model?

Each modern API has its own software development lifecycle, which reduces the need for documentation and automation.

Each modern API must be treated like a product and designed for a particular target audience (for instance, mobile app developers)

Each modern API must be easy to consume, so should avoid complex authentication mechanisms such as SAML or JWT.

Each modern API must be REST and HTTP based.