A.  

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.

B.  

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

C.  

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

D.  

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

A.  

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

B.  

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

C.  

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

D.  

When the API Implementation must write to a persistent Object Store

A.  

The number of production outage incidents reported in the last 24 hours

B.  

The number of API implementations that have a publicly accessible HTTP endpoint and are being managed by Anypoint Platform

C.  

The fraction of API implementations deployed manually relative to those deployed using a CI/CD tool

D.  

The number of API specifications in RAML or OAS format published to Anypoint Exchange

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.  

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

C.  

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

D.  

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

A.  

Manually provisioned customer-hosted runtime plane and customer-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.  

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

A.  

One production and one non-production Virtual Private Cloud (VPC). Use availability zones to differentiate between Business groups. Allocate maximum CIDR per VPCs to ensure HA across availability zones

B.  

One production and one non-production Virtual Private Cloud (VPC) per Business group. Minimize CIDR aligning with projected application total. Choose a MuleSoft CloudHub 1.0 region with multiple availability zones. Deploy multiple workers for HA,

C.  

One production and one non-production Virtual Private Cloud (VPC) per Business group. Minimize CIDR aligning with projected application total. Divide availability zones during deployment of APIs for HA.

D.  

One production and one non-production Virtual Private Claud (VPC). Configure subnet to differentiate between business groups. Allocate maximum CIDR per VPCs to make it easier to add Child groups. Span VPC to cover three availability zones.

A.  

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

B.  

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

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.  

Option A

B.  

Option B

C.  

Option C

D.  

Option D

A.  

Configure the HTTPS protocol in HTTP listener in the Mule application

B.  

Create a custom policy to apply to outgoing and incoming HTTP requests to control access to a configured API endpoint

C.  

Remove the entry from the VPC firewall rule

D.  

Configure the IP Blocklist policy to control access to a configured API endpoint from either a single IP address or a range of IP addresses.

E.  

Add the entry in the VPC firewall rule.

A.  

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

B.  

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

C.  

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

D.  

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

A.  

In the Orderltems process API implementation

B.  

In the Order API implementation

C.  

In the Inventory system API implementation

D.  

In the inventory database

A.  

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

B.  

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

C.  

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

D.  

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

A.  

The API administrator should configure the correct client discovery URL in both child business groups, and the API consumer should request access to the API in Ping Identity

B.  

The API administrator should grant access to the API consumers by creating contracts in the relevant API instances in API Manager

C.  

The APL consumer should create a client application and request access to the APT in Anypoint Exchange, and the API administrator should approve the request

D.  

The APT consumer should create a client application and request access to the API in Ping Identity, and the organization's Ping Identity workflow will grant access

A.  

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.

B.  

Request client’s AWS project team to replicate all the attributes and create Account and Case JSON table in DynamoD

B.  

C.  

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,

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.  

Customer SAPI

B.  

Customer Lookup PAPI

C.  

Mobile Account Management EAPI

D.  

Service SAPI

A.  

An SLA for the upstream API CANNOT be provided

B.  

The invocation of the downstream API will run to completion without timing out

C.  

A default timeout of 500 ms will automatically be applied by the Mule runtime in which the upstream API implementation executes

D.  

A toad-dependent timeout of less than 1000 ms will be applied by the Mule runtime in which the downstream API implementation executes

A.  

Create a custom policy that implements the circuit breaker and includes policy template expressions for the required settings

B.  

Create Anypoint Monitoring alerts for Circuit Open/Closed configurations, and then implement a retry strategy for Circuit Half-Open configuration

C.  

Add the Circuit Breaker policy to the API instance, and configure the required settings

D.  

Implement the strategy in a Mule application, and provide the settings in the YAML configuration

A.  

The settings of the Monitoring section in the control plane must be updated to enable detailed logging on the metrics to be captured

B.  

Monitoring Agent must be installed on each node in the cluster

C.  

Due to the potential performance impact on the runtime nodes, the Monitoring agent should be installed on a separate server

D.  

There is no action needed as the on-prem runtime automatically sends the performance data to the control plane

A.  

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

B.  

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

C.  

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

D.  

The API clients need to update the code on their side and need to do full regression

A.  

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

B.  

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

C.  

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

D.  

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

A.  

Anypoint Runtime Manager

B.  

Mule Maven plugin

C.  

Anypoint Platform CLI

D.  

Anypoint Platform REST APIs

A.  

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

B.  

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

C.  

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

D.  

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

A.  

None

B.  

Both

C.  

API Client

D.  

API Consumer

A.  

The APE Router component is pointing to the incorrect Exchange version of the APT

B.  

The Autodiscovery element is not present, in the deployed Mule application

C.  

No… for client applications have been created of this API

D.  

One of the application’s CloudHub workers restarted

A.  

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

B.  

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.

C.  

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

D.  

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

A.  

When it Is required to make ALL applications highly available across multiple data centers

B.  

When it is required that ALL APIs are private and NOT exposed to the public cloud

C.  

When regulatory requirements mandate on-premises processing of EVERY data item, including meta-data

D.  

When ALL backend systems in the application network are deployed in the organization's intranet

A.  

By refining the resource definitions by adding a description of the rate limiting policy behavior

B.  

By refining the request definitions by adding a remaining Requests query parameter with description, type, and example

C.  

By refining the response definitions by adding the out-of-the-box Anypoint Platform rate-limit-enforcement securityScheme with description, type, and example

D.  

By refining the response definitions by adding the x-ratelimit-* response headers with description, type, and example

A.  

Configure a policy so that when the number of HTTP requests reaches a certain threshold the number of workers/replicas increases (horizontal scaling)

B.  

Configure two separate policies: When CPU and memory reach certain threshold, increase the worker/replica type (vertical sealing) and the number of workers/replicas (horizontal sealing)

C.  

Configure a policy based on CPU usage so that CloudHub auto-adjusts the number of workers/replicas (horizontal scaling)

D.  

Configure a policy so that when the response time reaches a certain threshold the worker/replica type increases (vertical scaling)

A.  

APIs 1, 3, 5

B.  

APIs 2, 4 ,6

C.  

APIs 1, 2, s5, 6

D.  

APIs 1, 2, 3, 4

A.  

API-led connectivity is not just an architecture or technology but also a way to organize people and processes for efficient IT delivery in the organization

B.  

API-led connectivity is a 3-layered architecture covering Experience, Process and System layers

C.  

API-led connectivity is a technology which enabled us to implement Experience, Process and System layer based APIs

A.  

Option A

B.  

Option B

C.  

Option C

D.  

Option D

A.  

The API policy Is defined In Runtime Manager as part of the API deployment to a Mule runtime, and then ONLY applied to the specific API Instance

B.  

The API policy Is defined In API Manager for a specific API Instance, and then ONLY applied to the specific API instance

C.  

The API policy Is defined in API Manager and then automatically applied to ALL API instances

D.  

The API policy is defined in API Manager, and then applied to ALL API instances in the specified environment

A.  

Web Service Definition Language(WSDL)

B.  

OpenAPI Specification (OAS)

C.  

YAML

D.  

AsyncAPI Specification

A.  

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

B.  

Alerts on the APT invocation and API implementation can be raised

C.  

No alert on the API invocations is raised but alerts on the API implementation can be raised

D.  

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

A.  

In parallel, invoke the system API deployed to the primary environment and the system API deployed to the DR environment, and ONLY use the first response

B.  

In parallel, invoke the system API deployed to the primary environment and the system API deployed to the DR environment using a scatter-gather configured with a timeout, and then merge the responses

C.  

Invoke the system API deployed to the primary environment, and if it fails, invoke the system API deployed to the DR environment

D.  

Invoke ONLY the system API deployed to the primary environment, and add timeout and retry logic to avoid intermittent failures

A.  

Custom dashboards

B.  

Built-in dashboards

C.  

Functional monitoring

D.  

API Manager

A.  

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

B.  

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

C.  

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

D.  

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.  

Redis distributed cache

B.  

java.util.WeakHashMap

C.  

Persistent Object Store

D.  

File-based storage

A.  

Runtime Fabric on VMs / Bare Metal for the runtime plane

B.  

Customer-hosted runtime plane

C.  

MuleSoft-hosted runtime plane (CloudHub)

D.  

Anypoint Runtime Fabric on Self-Managed Kubernetes for the runtime plane

A.  

TRUE

B.  

FALSE

A.  

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

B.  

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

C.  

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

D.  

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

A.  

Custom circuit breaker

B.  

Client ID enforcement

C.  

Rate limiting

D.  

JSON threat protection

A.  

Set up VPC peering with AWS VPC and a VPN tunnel to the customer's on-premises corporate data center

B.  

Set up VPC peering with AWS VPC and the customer's on-premises corporate data center

C.  

Setup a transit gateway to the customer's on-premises corporate data center through AWS VPC

D.  

Set up VPC peering with the customer's on-premises corporate data center and a VPN tunnel to AWS VPC

A.  

At the experience and process tiers

B.  

At the experience and system tiers

C.  

At the process and system tiers

D.  

At the experience, process, and system tiers

A.  

API Analytics

B.  

Anypoint Monitoring dashboards

C.  

APT Functional Monitoring

D.  

Anypoint Runtime Manager alerts