An organization has implemented a Customer Address API to retrieve customer address information. This API has been deployed to multiple environments and has been configured to enforce client IDs everywhere.A developer is writing a client application to allow a user to update their address. The developer has found the Customer Address API in Anypoint Exchange and wants to use it in their client application.What step of gaining access to the API can be performed automatically by Anypoint Platform?

Approve the client application request for the chosen SLA tier

Request access to the appropriate API Instances deployed to multiple environments using the client application's credentials

Modify the client application to call the API using the client application's credentials

Create a new application in Anypoint Exchange for requesting access to the API

What is a typical result of using a fine-grained rather than a coarse-grained API deployment model to implement a given business process?

A higher number of discoverable API-related assets in the application network

A decrease in the number of connections within the application network supporting the business process

A higher number of discoverable API-related assets in the application network

A better response time for the end user as a result of the APIs being smaller in scope and complexity

An overall tower usage of resources because each fine-grained API consumes less resources

What correctly characterizes unit tests of Mule applications?

They are typically written using MUnit to run in an embedded Mule runtime that does not require external connectivity

They test the validity of input and output of source and target systems

They must be run in a unit testing environment with dedicated Mule runtimes for the environment

They must be triggered by an external client tool or event source

They are typically written using MUnit to run in an embedded Mule runtime that does not require external connectivity

An organization is deploying their new implementation of the OrderStatus System API to multiple workers in CloudHub. This API fronts the organization's on-premises Order Management System, which is accessed by the API implementation over an IPsec tunnel.What type of error typically does NOT result in a service outage of the OrderStatus System API?

A CloudHub worker fails with an out-of-memory exception

API Manager has an extended outage during the initial deployment of the API implementation

The AWS region goes offline with a major network failure to the relevant AWS data centers

The Order Management System is Inaccessible due to a network outage in the organization's on-premises data center

An Order API must be designed that contains significant amounts of integration logic and involves the invocation of the Product API.The power relationship between Order API and Product API is one of 'Customer/Supplier', because the Product API is used heavily throughout the organization and is developed by a dedicated development team located in the office of the CTO.What strategy should be used to deal with the API data model of the Product API within the Order API?

Implement an anti-corruption layer in the Order API that transforms the Product API data model into internal data types of the Order API

Convince the development team of the Product API to adopt the API data model of the Order API such that the integration logic of the Order API can work with one consistent internal data model

Work with the API data types of the Product API directly when implementing the integration logic of the Order API such that the Order API uses the same (unchanged) data types as the Product API

Implement an anti-corruption layer in the Order API that transforms the Product API data model into internal data types of the Order API

Start an organization-wide data modeling initiative that will result in an Enterprise Data Model that will then be used in both the Product API and the Order API

An API implementation is being designed that must invoke an Order API, which is known to repeatedly experience downtime.For this reason, a fallback API is to be called when the Order API is unavailable.What approach to designing the invocation of the fallback API provides the best resilience?

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

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

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

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

How are an API implementation, API client, and API consumer combined to invoke and process an API?

The ApI consumer creates an API client, which sends API invocations to an API such that they are processed by an API implementation

The API consumer creates an API implementation, which receives API invocations from an API such that they are processed for an API client

The API client creates an API consumer, which receives API invocations from an API such that they are processed for an API implementation

The ApI consumer creates an API client, which sends API invocations to an API such that they are processed by an API implementation

The ApI client creates an API consumer, which sends API invocations to an API such that they are processed by an API implementation

When must an API implementation be deployed to an Anypoint VPC?

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

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

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

When the API Implementation must write to a persistent Object Store

What is true about API implementations when dealing with legal regulations that require all data processing to be performed within a certain jurisdiction (such as in the USA or the EU)?

They must te deployed to Anypoint Platform runtime planes that are managed by Anypoint Platform control planes, with both planes in the same Jurisdiction

They must avoid using the Object Store as it depends on services deployed ONLY to the US East region

They must use a Jurisdiction-local external messaging system such as Active MQ rather than Anypoint MQ

They must te deployed to Anypoint Platform runtime planes that are managed by Anypoint Platform control planes, with both planes in the same Jurisdiction

They must ensure ALL data is encrypted both in transit and at rest

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?

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

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

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

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

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

Mule applications that implement a number of REST APIs are deployed to their own subnet that is inaccessible from outside the organization.External business-partners need to access these APIs, which are only allowed to be invoked from a separate subnet dedicated to partners - called Partner-subnet. This subnet is accessible from the public internet, which allows these external partners to reach it.Anypoint Platform and Mule runtimes are already deployed in Partner-subnet. These Mule runtimes can already access the APIs.What is the most resource-efficient solution to comply with these requirements, while having the least impact on other applications that are currently using the APIs?

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

Redeploy the API implementations to the same servers running the Mule runtimes

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

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

When could the API data model of a System API reasonably mimic the data model exposed by the corresponding backend system, with minimal improvements over the backend system's data model?

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

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

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

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

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

Refer to the exhibit. An organization uses one specific CloudHub (AWS) region for all CloudHub deployments.How are CloudHub workers assigned to availability zones (AZs) when the organization's Mule applications are deployed to CloudHub in that region?

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

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

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

Workers are randomly distributed across available AZs within that region

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

What is most likely NOT a characteristic of an integration test for a REST API implementation?

The test runs immediately after the Mule application has been compiled and packaged

The test needs all source and/or target systems configured and accessible

The test runs immediately after the Mule application has been compiled and packaged

The test is triggered by an external HTTP request

The test prepares a known request payload and validates the response payload

An API implementation is updated. When must the RAML definition of the API also be updated?

When the API implementation changes the structure of the request or response messages

When the API implementation changes from interacting with a legacy backend system deployed on-premises to a modern, cloud-based (SaaS) system

When the API implementation is migrated from an older to a newer version of the Mule runtime

When the API implementation is optimized to improve its average response time

A REST API is being designed to implement a Mule application.What standard interface definition language can be used to define REST APIs?

Web Service Definition Language(WSDL)

A retail company is using an Order API to accept new orders. The Order API uses a JMS queue to submit orders to a backend order management service. The normal load for orders is being handled using two (2) CloudHub workers, each configured with 0.2 vCore. The CPU load of each CloudHub worker normally runs well below 70%. However, several times during the year the Order API gets four times (4x) the average number of orders. This causes the CloudHub worker CPU load to exceed 90% and the order submission time to exceed 30 seconds. The cause, however, is NOT the backend order management service, which still responds fast enough to meet the response SLA for the Order API. What is the MOST resource-efficient way to configure the Mule application's CloudHub deployment to help the company cope with this performance challenge?

Use a horizontal CloudHub autoscaling policy that triggers on CPU utilization greater than 70%

Permanently increase the size of each of the two (2) CloudHub workers by at least four times (4x) to one (1) vCore

Use a vertical CloudHub autoscaling policy that triggers on CPU utilization greater than 70%

Permanently increase the number of CloudHub workers by four times (4x) to eight (8) CloudHub workers

Use a horizontal CloudHub autoscaling policy that triggers on CPU utilization greater than 70%

A company has started to create an application network and is now planning to implement a Center for Enablement (C4E) organizational model. What key factor would lead the company to decide upon a federated rather than a centralized C4E?

When development is already organized into several independent initiatives or groups

When there are a large number of existing common assets shared by development teams

When various teams responsible for creating APIs are new to integration and hence need extensive training

When development is already organized into several independent initiatives or groups

When the majority of the applications in the application network are cloud based

An organization wants MuleSoft-hosted runtime plane features (such as HTTP load balancing, zero downtime, and horizontal and vertical scaling) in its Azure environment. What runtime plane minimizes the organization's effort to achieve these features?

Anypoint Platform for Pivotal Cloud Foundry

A hybrid combination of customer-hosted and MuleSoft-hosted Mule runtimes

Say, there is a legacy CRM system called CRM-Z which is offering below functions:1. Customer creation2. Amend details of an existing customer3. Retrieve details of a customer4. Suspend a customer

Implement different system APIs named createCustomer, amendCustomer, retrieveCustomer and suspendCustomer as they are modular and has seperation of concerns

Implement a system API named customerManagement which has all the functionalities wrapped in it as various operations/resources

Implement different system APIs named createCustomer, amendCustomer, retrieveCustomer and suspendCustomer as they are modular and has seperation of concerns

Implement different system APIs named createCustomerInCRMZ, amendCustomerInCRMZ, retrieveCustomerFromCRMZ and suspendCustomerInCRMZ as they are modular and has seperation of concerns

An Anypoint Platform organization has been configured with an external identity provider (IdP) for identity management and client management. What credentials or token must be provided to Anypoint CLI to execute commands against the Anypoint Platform APIs?

The credentials provided by the IdP for identity management

The credentials provided by the IdP for client management

An OAuth 2.0 token generated using the credentials provided by the IdP for client management

An OAuth 2.0 token generated using the credentials provided by the IdP for identity management

What is the main change to the IT operating model that MuleSoft recommends to organizations to improve innovation and clock speed?

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

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

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

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 company wants to move its Mule API implementations into production as quickly as possible. To protect access to all Mule application data and metadata, the company requires that all Mule applications be deployed to the company's customer-hosted infrastructure within the corporate firewall. What combination of runtime plane and control plane options meets these project lifecycle goals?

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

MuleSoft-hosted runtime plane and customer-hosted control plane

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

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

Which of the below, when used together, makes the IT Operational Model effective?

Create resuable assets, make them discoverable so that LOB teams can self-serve and browse the APIs

Create reusable assets, Do marketing on the created assets across organization, Arrange time to time LOB reviews to ensure assets are being consumed or not

Create reusable assets, Make them discoverable so that LOB teams can self-serve and browse the APIs, Get active feedback and usage metrics

Create resuable assets, make them discoverable so that LOB teams can self-serve and browse the APIs

Which of the following sequence is correct?

API Consumer requests access to API >> API Client implementes logic to call an API >> API routes the request to >> API Implementation

API Client implementes logic to call an API >> API Consumer requests access to API >> API Implementation routes the request to >> API

API Consumer requests access to API >> API Client implementes logic to call an API >> API routes the request to >> API Implementation

API Consumer implementes logic to call an API >> API Client requests access to API >> API Implementation routes the request to >> API

API Client implementes logic to call an API >> API Consumer requests access to API >> API routes the request to >> API Implementation

An organization has created an API-led architecture that uses various API layers to integrate mobile clients with a backend system. The backend system consists of a number of specialized components and can be accessed via a REST API. The process and experience APIs share the same bounded-context model that is different from the backend data model. What additional canonical models, bounded-context models, or anti-corruption layers are best added to this architecture to help process data consumed from the backend system?

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

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

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

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

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

An API client calls one method from an existing API implementation. The API implementation is later updated. What change to the API implementation would require the API client's invocation logic to also be updated?

When a new required field is added to the method called by the API client

When the data type of the response is changed for the method called by the API client

When a new method is added to the resource used by the API client

When a new required field is added to the method called by the API client

When a child method is added to the method called by the API client

Traffic is routed through an API proxy to an API implementation. The API proxy is managed by API Manager and the API implementation is deployed to a CloudHub VPC using Runtime Manager. API policies have been applied to this API. In this deployment scenario, at what point are the API policies enforced on incoming API client requests?

At both the API proxy and the API implementation

At a MuleSoft-hosted load balancer

A system API is deployed to a primary environment as well as to a disaster recovery (DR) environment, with different DNS names in each environment. A process API is a client to the system API and is being rate limited by the system API, with different limits in each of the environments. The system API's DR environment provides only 20% of the rate limiting offered by the primary environment. What is the best API fault-tolerant invocation strategy to reduce overall errors in the process API, given these conditions and constraints?

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

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

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

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

A company uses a hybrid Anypoint Platform deployment model that combines the EU control plane with customer-hosted Mule runtimes. After successfully testing a Mule API implementation in the Staging environment, the Mule API implementation is set with environment-specific properties and must be promoted to the Production environment. What is a way that MuleSoft recommends to configure the Mule API implementation and automate its promotion to the Production environment?

Bundle properties files for each environment into the Mule API implementation's deployable archive, then promote the Mule API implementation to the Production environment using Anypoint CLI or the Anypoint Platform REST APIsB.

Modify the Mule API implementation's properties in the API Manager Properties tab, then promote the Mule API implementation to the Production environment using API Manager

Modify the Mule API implementation's properties in Anypoint Exchange, then promote the Mule API implementation to the Production environment using Runtime Manager

Use an API policy to change properties in the Mule API implementation deployed to the Staging environment and another API policy to deploy the Mule API implementation to the Production environment

An organization wants to make sure only known partners can invoke the organization's APIs. To achieve this security goal, the organization wants to enforce a Client ID Enforcement policy in API Manager so that only registered partner applications can invoke the organization's APIs. In what type of API implementation does MuleSoft recommend adding an API proxy to enforce the Client ID Enforcement policy, rather than embedding the policy directly in the application's JVM?

A Mule 3 application using APIkit

A Mule 3 or Mule 4 application modified with custom Java code

A Mule 4 application with an API specification

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?

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

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

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

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

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