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

（A）No timeout is possible to meet the upstream API's desired SLA; a different SLA must be negotiated with the first downstream API or invoke an alternative API

（B）Set a timeout of 50 ms; this times out more invocations of that API but gives additional room for retries

（C）Do not set a timeout; the Invocation of this API Is mandatory and so we must wait until it responds

（D）Set a timeout of 100 ms; that leaves 400 ms for the other two downstream APIs to complete

（A）When the API Implementation must write to a persistent Object Store

（B）When the API Implementation must invoke publicly exposed services that are deployed outside of CloudHub in a customer- managed AWS instance

（C）When the API implementation must be deployed to a production AWS VPC using the Mule Maven plugin

（D）When the API implementation must be accessible within a subnet of a restricted customer-hosted network that does not allow public access

（A）Spike control

（B）Rate limiting

（C）HTTP caching

（D）Rate limiting - SLA based

（A）API Consumer Engagement

（B）API Design and Development

（C）API Runtime Execution and Hosting

（D）API Operations and Management

（A）Redis distributed cache

（B）java.util.WeakHashMap

（C）File-based storage

（D）Persistent Object Store

（A）When the System API can be assigned to a bounded context with a corresponding data model

（B）When there is an existing Enterprise Data Model widely used across the organization

（C）When the corresponding backend system is expected to be replaced in the near future

（D）When a pragmatic approach with only limited isolation from the backend system is deemed appropriate

（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）Each modern API has its own software development lifecycle, which reduces the need for documentation and automation

（B）Each modern API must be REST and HTTP based

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

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

（A）Workers are randomly distributed across available AZs within that region

（B）An AZ is randomly selected for a Mule application, and all the Mule application's CloudHub workers are assigned to that one AZ

（C）AZs are selected as part of the Mule application's deployment configuration

（D）Workers belonging to a given environment are assigned to the same AZ within that region

（A）Build an Enterprise Data Model (Canonical Data Model) for each backend system and apply it to System APIs

（B）Document the API using an easily consumable asset like a RAML definition

（C）Model all API resources and methods to closely mimic the operations of the backend system

（D）Expose to API clients all technical details of the API implementation's interaction wifch the backend system