最新のMule-Arch-201問題集で試験を準備する

Salesforce Mule-Arch-201 試験概要:

Salesforce Mule-Arch-201 試験シラバストピック:

Salesforce Certified MuleSoft Platform Architect 認定 Mule-Arch-201 試験問題：

問題 #1

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 APIs public portal. The API endpoint does NOT change in the new version. How should the developer of an API client respond to this change?

A. The API clients need to update the code on their side and need to do full regression
B. The API producer should be requested to run the old version in parallel with the new one
C. The API client code only needs to be changed if it needs to take advantage of the new features
D. The API producer should be contacted to understand the change to existing functionality

問題 #2

Refer to the exhibits.

Which architectural constraint is compatible with the API-led connectivity architectural style?

A. Handle customizations for the end-user application at the Process layer rather than at the Experience layer
B. Use a Process API to-orchestrate calls to multiple System APIs but not to other Process APIs:
C. Allow System APIs to return data that is not currently required by the identified Process or Experience APIs

D. Always use a tiered approach by creating exactly one API for each of the three layers (Experience, Process, and System)

問題 #3

A company requires Mule applications deployed to CloudHub to be isolated between non-production and production environments. This is so Mule applications deployed to non-production environments can only access backend systems running in their customer-hosted non-production environment, and so Mule applications deployed to production environments can only access backend systems running in their customer-hosted production environment. How does MuleSoft recommend modifying Mule applications, configuring environments, or changing infrastructure to support this type of per-environment isolation between Mule applications and backend systems?

A. Create non-production and production environments in different Anypoint Platform business groups
B. Create separate Anypoint VPCs for non-production and production environments, then configure connections to the backend systems in the corresponding customer-hosted environments
C. Configure firewall rules in the infrastructure inside each customer-hosted environment so that only IP addresses from the corresponding Anypoint Platform environments are allowed to communicate with corresponding backend systems
D. Modify properties of Mule applications deployed to the production Anypoint Platform environments to prevent access from non-production Mule applications

問題 #4

An enterprise is embarking on the API-led digital transformation journey, and the central IT team has started to define System APIs. Currently there is no Enterprise Data Model being defined within the enterprise, and the definition of a clean Bounded Context Data Model requires too much effort.
According to MuleSoft's recommended guidelines, how should the System API data model be defined?

A. The data model of the System APIs should make use of data types that approximately mirror those from the back-end systems
B. If there are misspellings of the data fields in the back-end system, Systerm APIs should not correct it, and expose it as-is to mirror the back-end systems
C. The System APIs should expose all back-end system fields
D. The data model should define its own naming convention, and not follow the same naming as the back-end systems

問題 #5

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?

A. The API producer should be requested to run the old version in parallel with the new one
B. The API client code ONLY needs to be changed if it needs to take advantage of new features
C. The API producer should be contacted to understand the change to existing functionality
D. The update should be identified as a project risk and full regression testing of the functionality that uses this API should be run

解説：