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

（A）Duplicate the APIs as Mule applications, then deploy them to the Mule runtimes

（B）Implement (or generate) an API proxy Mule application for each of the APIs, then deploy the API proxies to the Mule runtimes

（C）Add an additional endpoint to each API for partner-enablement consumption

（D）Redeploy the API implementations to the same servers running the Mule runtimes

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

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

（C）Apply a basic authentication - LDAP policy; the internal Active Directory will be configured as the LDAP source for authenticating users

（D）Apply an IP whitelist policy; only the specific users' workstations will be in the whitelist

（A）To invoke OAuth 2.0-protected APIs managed by Anypoint Platform, API clients must submit access tokens issued by that same Identity Provider

（B）APIs managed by Anypoint Platform must be protected by SAML 2.0 policies

（C）Single sign-on is required to sign in to Anypoint Platform

（D）The application network must include System APIs that interact with the Identity Provider

（A）The System APIs should expose all back-end system fields

（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 data model should define its own naming convention, and not follow the same naming as the back-end systems

（D）The data model of the System APIs should make use of data types that approximately mirror those from the back-end systems

（A）Use a Process API to-orchestrate calls to multiple System APIs but not to other Process APIs:

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

（C）Allow System APIs to return data that is not currently required by the identified Process or Experience APIs

（D）Handle customizations for the end-user application at the Process layer rather than at the Experience layer

（A）Guarding against Denial of Service attacks

（B）Backend system overloading

（C）Logging HTTP requests and responses

（D）Maintaining tamper-proof credentials between APIs

（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）No alert on the API invocations is raised but alerts on the API implementation can be raised

（B）Alerts on the APT invocation and API implementation can be raised

（C）No alert on the API invocations and APT implementation can be raised

（D）Alerts on the API invocations are raised but no alerts on the API implementation can be raised

（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）At a MuleSoft-hosted load balancer

（B）At the API proxy

（C）At the API implementation

（D）At both the API proxy and the API implementation