A.  

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

B.  

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

C.  

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

D.  

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

A.  

If an external identity provider is configured, the SAML 2.0 bearer tokens issued by the identity provider cannot be used for invocations of the Anypoint Platform web APIs

B.  

If an external client provider is configured, it must be configured at the Anypoint Platform organization level and cannot be assigned to individual business groups and environments

C.  

Anypoint Platform supports configuring one external identity provider

D.  

Both client management and identity management require an identity provider

A.  

3.0.2

B.  

4.0.0

C.  

3.1.0

D.  

3.0.1

A.  

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

B.  

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

C.  

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

D.  

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

A.  

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

B.  

The data model of the System APIs should make use of data types that approximately mirror those from 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 System APIs should expose all back-end system fields

A.  

The complexity of each API implementation

B.  

The number of discoverable assets related to APIs deployed in the application network

C.  

The number of possible connections between API implementations in the application network

D.  

The usage of network infrastructure resources by the application network

A.  

Increase the vCPU resources of the API implementation

B.  

Modify the API client to split the problematic request into smaller, less-demanding requests

C.  

Increase the number of replicas of the API implementation

D.  

Throttle the APT client to reduce the number of requests per minute

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.  

transfer ISON data to DynamoD for respective Objects

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.  

A fixed number of FQDNs are created, IRRESPECTIVE of the environment and VPC design

B.  

The FQDNs are determined by the application name chosen, IRRESPECTIVE of the region

C.  

The FQDNs are determined by the application name, but can be modified by an administrator after deployment

D.  

The FQDNs are determined by both the application name and the Anypoint Platform organization

A.  

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

B.  

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

C.  

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

D.  

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

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.  

Option A

B.  

Option B

C.  

Option C

D.  

Option D

A.  

Shut out bad actors by using HTTPS mutual authentication for all API invocations

B.  

Apply an IP blacklist policy to all APIs; the blacklist will Include all bad actors

C.  

Apply a Header injection and removal policy that detects the malicious data before it is used

D.  

Apply a JSON threat protection policy to all APIs to detect potential threat vectors

A.  

Add two new Experience APIs (EAPI-i and EAPI-2}.

Add Mobile PAPI-2 to expose the Intended subset of financial data as requested.

Both PAPIs access the Legacy Systems via SAPI-1 and SAP]-2.

B.  

Add two new Experience APIs (EAPI-i and EAPI-2}.

Add Mobile PAPI-2 to expose the Intended subset of financial data as requested.

Both PAPIs access the Legacy Systems via SAPI-1 and SAP]-2.

C.  

Create a new mobile Experince API (EAPI) chat exposes that subset of PAPI endpoints.

Add transformtion login to the mobile Experince API implementation to make mobile data compatible with the required PAPIs.

D.  

Develop and deploy is new PAPI implementation with data transformation and ... login to support this required endpoints of both mobile and web clients.

Deploy an API Proxy with an endpoint from API Manager that redirect the existing PAPI endpoints to the new PAPI.

A.  

Integration tests

B.  

Performance tests

C.  

Functional tests (Blackbox)

D.  

Unit tests (Whitebox)

A.  

When there are three CloudHub deployments of the API implementation to three separate CloudHub regions that must share the cache state

B.  

When there are two CloudHub deployments of the API implementation by two Anypoint Platform business groups to the same CloudHub region that must share the cache state

C.  

When there is one deployment of the API implementation to CloudHub and anottV deployment to a customer-hosted Mule runtime that must share the cache state

D.  

When there is one CloudHub deployment of the API implementation to three CloudHub workers that must share the cache state

A.  

The assignment of each HTTP request to a particular CloudHub worker

B.  

The logging configuration that enables log entries to be visible in Runtime Manager

C.  

The SSL certificates used by the API implementation to expose HTTPS endpoints

D.  

The number of DNS entries allocated to the API implementation

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.  

When the API invocations are sent directly to the internal DNS record of the API implementation

B.  

When the API invocations are not over-a- secure TLS/SSL communication channel

C.  

When the APL invecations originate from a geography different than the API

D.  

When the number of API invocations are below a threshold

A.  

Anypoint Runtime Fabric

B.  

Anypoint Platform for Pivotal Cloud Foundry

C.  

CloudHub

D.  

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

A.  

Customer SAPI

B.  

Customer Lookup PAPI

C.  

Mobile Account Management EAPI

D.  

Service SAPI

A.  

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

B.  

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

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.  

Persistent Object Store

B.  

Runtime Fabric Object Store

C.  

Non-persistent Object Store

D.  

In-memory Mule Object Store

A.  

Select the product details from a database in a Cache scope and return them within the API response

B.  

Select the product details from a database and put them in Anypoint MQ; the Anypoint MO subseriber will receive the product details and return them within the API response

C.  

Use an object store to store and retrieve the product details originally read from a database and return them within the API response

D.  

Select the product details from a database and return them within the API response

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.  

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.  

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

B.  

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

C.  

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

D.  

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

A.  

443

B.  

8081

C.  

8091

D.  

8082

A.  

API Versioning, API Runtime Execution and Hosting, API Invocation, API Consumer Engagement

B.  

API Design and Development, API Runtime Execution and Hosting, API Versioning, API Deprecation

C.  

API Design and Development, API Runtime Execution and Hosting, API Operations and Management, API Consumer Engagement

D.  

API Design and Development, API Deprecation, API Versioning, API Consumer Engagement

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.  

The API ID changes, but no changes are needed to the API implementation for the new asset version in the API Autediscovery global element because the API ID is automatically updated

B.  

The APL ID changes, so the API implementation must be updated with the latest API ID for the new asset version in the API Autodiscovery global element

C.  

The APLID does not change, so no changes to the APT implementation are needed for the new asset version in the API Autodiscovery global element

D.  

The APL ID does not change, but the API implementation must be updated in the AP] Autodiscovery global element to indicate the new asset version 2.0.4

A.  

The application scalability threshold is five requests per second regardless of the horizontal scaling

B.  

The total process execution time is now 100 milliseconds (.1 seconds)

C.  

The application scalability threshold is now 10 requests per second

D.  

Horizontal scaling cannot be applied to an already-running application

A.  

When cross-region load balancing is required between separate deployments of the same Mule application

B.  

When custom DNS names are required for API implementations deployed to customer-hosted Mule runtimes

C.  

When API invocations across multiple CloudHub workers must be load balanced

D.  

When server-side load-balanced TLS mutual authentication is required between API implementations and API clients

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.  

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.  

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

B.  

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

C.  

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

D.  

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

A.  

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

B.  

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

C.  

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

A.  

Implement a heartbeat/health check within the API and invoke it from outside the Anypoint Platform and alert when the heartbeat does not respond

B.  

Configure a "worker not responding" alert in Anypoint Runtime Manager

C.  

Handle API invocation exceptions within the calling API client and raise an alert from that API client when the API Is unavailable

D.  

Create an alert for when the API receives no requests within a specified time period

A.  

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

B.  

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

C.  

The test is triggered by an external HTTP request

D.  

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

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.  

Option A

B.  

Option B

C.  

Option C

D.  

Option D

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.  

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

B.  

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

C.  

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

D.  

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

A.  

To store an unlimited number of key-value pairs

B.  

To store payloads with an average size greater than 15MB

C.  

To store information in Mule 4 Object Store v1

D.  

To store key-value pairs with keys up to 300 characters

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