How we can scale deployed Mule application vertically on cloudhub?
A. Changing worker size
B. Adding multiple workers
C. Mule applications can be scaled only horizontally
D. Option 1 and 2 both can be used
Explanation: Mule applications can be scaled vertically by changing worker size. Mule applications can be scaled horizontally by adding more workers.
A Mule application contains two HTTP Listeners, each configured for different API
endpoints: http://acme.com/apis/orders and http: //acme .com/a pis/customers.
What base path value should be set in an HTT? Listener config element so that it can be
used to configure both HTTP Listeners?
A.
/apis/?
B.
/apis/
C.
/apis/orders|customers
D.
/apis/*
/apis/*
What asset cannot be created using Design Center?
A. Mule Applications
B. API fragments
C. API specifications
D. API portals
Explanation: API portal are created by API Exchange and cannot be created by Design Center
An organization's Center for enablement (C4E)has built foundational assets (API
specifications and implementation templates, common frameworks, and best practices
guides) and published them to Anypoint Exchange.
What is a metric related to these foundational assets that helps the organization measure
the success of it's C4E efforts?
A. Utilization counts of foundational assets in production applications
B. Correlation of each foundational asset with the counts of developers that download such asset
C. Correlation of key performance indicators (KPI) of production applications with foundational assets
D. Count how many Lines Of Business (LoBs) onsumed each foundational asset
Explanation:
Below are the Key performance indicators (KPIs), to measure and track the and success of
the C4E and its activities, as well as the growth and health of the application network. Most
of the metrics can be extracted automatically, through REST APIs, from Anypoint Platform.
• # of assets published to Anypoint Exchange
• # of interactions with Anypoint Exchange assets
• # of APIs managed by Anypoint Platform
• # of System APIs managed by Anypoint Platform
• # of API clients registered for access to APIs
• # of API implementations deployed to Anypoint Platform
• # of API invocations
• # or fraction of lines of code covered by automated tests in CI/CD pipeline
• Ratio of info/warning/critical alerts to number of API invocations
Refer to the exhibit.
How should the WHERE clause be changed to set the city and state values from the
configured input parameters?
A. Option A
B. Option B
C. Option C
D. Option D
Refer to the exhibit. 
What should be changed to fix the 415 error?
A.
set the response Content-Type header to text/plain
B.
set the response Content-Type header to application/json
C.
Set the request Content-Type header toapplication/] son
D.
set the request Content-Type header to text/plain
Set the request Content-Type header toapplication/] son
Refer to the exhibits.
A. Option A
B. Option B
C. Option C
D. Option D
Explanation: Correct answer is as below. After all processing routes have finished execution, the Scatter- Gather component creates a new Mule event that combines all resulting Mule events from each route, and then passes the new Mule event to the next component in the flow.
What MuleSoft API-led connectivity layer is intended to expose part of a backend database without business logic?
A. Data layer
B. Process layer
C. Experience layer
D. System layer
Explanation:
Correct answer is System layer
System APIs provide a means for insulating the data consumers from the complexity or
changes to the underlying backend systems.
MuleSoft recommends three-layered approach to API-led connectivity, highlighting the
three layers:
* System APIs
* Process APIs
* Experience APIs
System APIs are the core systems of record underlying core systems of record (e.g. ERPs,
key customer and billing systems, databases, etc.). Process APIs allow you to define a
common process which the organization can share, and these APIs perform specific
functions, provide access to non-central data, and may be built by either Central IT or Line
of Business IT. And finally, the Experience APIs are the means by which data can be
reconfigured so that it is most easily consumed by its intended audience, all from a
common data source.
The three-layered structure allows for a seamless flow of data from systems of record to
new experiences, and allows for reusability of assets rather than point to point connections.
This approach provides a distributed and tailored approach to architecture, greater
flexibility through loose coupling, and deeper operational visibility into what is being built.
| Page 1 out of 29 Pages |
Contact Us - Privacy Policy ... Copyright © - All Rights Reserved