Salesforce Certified MuleSoft Platform Architect I - MuleSoft-Platform-Architect-I Exam Practice Test

A. Backend system overloading

B. Logging HTTP requests and responses

C. Guarding against Denial of Service attacks

D. Maintaining tamper-proof credentials between APIs

A. In the Orderltems process API implementation

B. In the Order API implementation

C. In the inventory database

D. In the Inventory system API implementation

A. AZs are selected as part of the Mule application's deployment configuration

B. Workers belonging to a given environment are assigned to the same AZ within that region

C. Workers are randomly distributed across available AZs within that region

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

A. 1. Decrease the IT delivery gap
2. Meet various business demands without increasing the IT capacity
3. Focus on creation of reusable assets first. Upon finishing creation of all the possible assets then inform the LOBs in the organization to start using them

B. 1. Decrease the IT delivery gap
2. Meet various business demands by increasing the IT capacity and forming various IT departments
3. Make consumption of assets at the rate of production

C. 1. Decrease the IT delivery gap
2. Meet various business demands without increasing the IT capacity
3. Make consumption of assets at the rate of production

A. In a clustered environment, the Rate Limiting.and Spike Control policies are applied to each node in the cluster

B. To protect Experience APIs by limiting resource consumption, Rate Limiting policy must be applied

C. In order to apply Rate Limiting and Spike Control policies, a contract to bind client application and API is needed for both

D. All requests are rejected after the limit is reached in Rate Limiting policy, whereas the requests are queued in Spike Control policy after the limit is reached

A. Start implementing an Enterprise Data Model by defining enterprise Account and Case Objects and implement SAPI and DynamoDB tables based on the Enterprise Data Model,

B. Request client's AWS project team to replicate all the attributes and create Account and Case JSON table in DynamoDB. Then create separate entities for Account and Case Objects by mimicking all the attributes in SAPI to transfer ISON data to DynamoD for respective Objects

C. Create separate entities for Account and Case Objects by mimicking all the attributes in SAPI, which are combined by the PAPI and filtered to provide JSON output containing 13 attributes.

D. Create separate entities for Account with five attributes and Case with eight attributes in SAPI, which are combined by the PAPI to provide JSON output containing 13 attributes.

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

B. 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

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

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

A. iPaaS provisioned customer-hosted runtime plane and MuleSoft-hosted control plane

B. MuleSoft-hosted runtime plane and customer-hosted control plane

C. Manually provisioned customer-hosted runtime plane and MuleSoft-hosted control plane

D. Manually provisioned customer-hosted runtime plane and customer-hosted control plane

A. Drive consumption as much as production of assets; this enables developers to discover and reuse assets from other projects and encourages standardization

B. Implement SOA for reusable APIs to focus on production over consumption; this standardizes on XML and WSDL formats to speed up decision making

C. Expose assets using a Master Data Management (MDM) system; this standardizes projects and enables developers to quickly discover and reuse assets from other projects

D. Create a lean and agile organization that makes many small decisions everyday; this speeds up decision making and enables each line of business to take ownership of its projects

A. Combining the insurance policy information from the administration systems

B. Querying the data from the administration systems

C. Authenticating and maintaining connections to each of the back-end administration systems

D. Presenting the SOAP-based response to the UI

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

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

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

D. Each modern API must be REST and HTTP based

A. To expedite this project, central IT should extend the CRM system and back-end systems to connect to one another using built in integration interfaces

B. Invite the business analyst to create a business process model to specify the canonical data model between the two systems

C. Determine if the new CRM system supports the creation of custom: REST APIs, establishes 4 private network with CloudHub, and supports GAuth 2.0 authentication

D. Create a System API to unlock the data on the back-end system using a REST API

A. Create a bounded-context model for the system layer to closely match the backend data model, and add an anti-corruption layer to let the different bounded contexts cooperate across the system and process layers

B. Create an anti-corruption layer for every API to perform transformation for every data model to match each other, and let data simply travel between APIs to avoid the complexity and overhead of building canonical models

C. Create a canonical model that combines the backend and API-led models to simplify and unify data models, and minimize data transformations.

D. Create a bounded-context model for every layer and overlap them when the boundary contexts overlap, letting API developers know about the differences between upstream and downstream data models