MuleSoft-Platform-Architect-I 無料問題集「Salesforce Certified MuleSoft Platform Architect I」

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

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

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

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

（A）They reduce the dependency on the underlying backend systems by helping unlock data from backend systems In a reusable and consumable way.

（B）They can compose data from various sources and combine them with orchestration logic to create higher level value.

（C）They provide an additional layer of resilience on top of the underlying backend system, thereby insulating clients from extended failure of these systems.

（D）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.

（A）Handle API invocation exceptions within the calling API client and raise an alert from that API client when the API Is unavailable

（B）Implement a heartbeat/health check within the API and invoke it from outside the Anypoint Platform and alert when the heartbeat does not respond

（C）Configure a "worker not responding" alert in Anypoint Runtime Manager

（D）Create an alert for when the API receives no requests within a specified time period

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

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

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

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

（A）Implement required changes to the Process API implementation so that whenever possible, the Process API's RAML definition remains unchanged

（B）Implement the Process API changes in a new API implementation, and have the old API implementation return an HTTP status code 301 - Moved Permanently to inform API clients they should be calling the new API implementation

（C）Postpone changes until API consumers acknowledge they are ready to migrate to a new Process API or API version

（D）Update the RAML definition of the current Process API and notify API client developers by sending them links to the updated RAML definition

（A）Modify properties of Mule applications deployed to the production Anypoint Platform environments to prevent access from non-production Mule applications

（B）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

（C）Create non-production and production environments in different Anypoint Platform business groups

（D）Create separate Anypoint VPCs for non-production and production environments, then configure connections to the backend systems in the corresponding customer-hosted environments

（A）Runtime Manager autoscaling

（B）The CloudHub shared load balancer

（C）A customer-hosted load balancer

（D）An API proxy

（A）Invoke the system API deployed to the primary environment; add retry logic to the process API to handle intermittent failures by invoking the system API deployed to the DR environment

（B）Invoke the system API deployed to the primary environment; add timeout and retry logic to the process API to avoid intermittent failures; if it still fails, invoke a copy of the process API deployed to the DR environment

（C）Invoke the system API deployed to the primary environment; add timeout and retry logic to the process API to avoid intermittent failures; if it still fails, invoke the system API deployed to the DR environment

（D）In parallel, invoke the system API deployed to the primary environment and the system API deployed to the DR environment; add timeout and retry logic to the process API to avoid intermittent failures; add logic to the process API to combine the results

（A）API Design and Development, API Runtime Execution and Hosting, API Versioning, API Deprecation

（B）API Versioning, API Runtime Execution and Hosting, API Invocation, API Consumer Engagement

（C）API Design and Development, API Deprecation, API Versioning, API Consumer Engagement

（D）API Design and Development, API Runtime Execution and Hosting, API Operations and Management, API Consumer Engagement

（A）4.0.0

（B）3.1.0

（C）3.0.1

（D）3.0.2