An API implementation has been deployed to CloudHub and now needs to be governed. IT
will not allocate additional vCore for a new Mule application to act as an API proxy.
Whatis the next step to preseive the current vCore usage, but still allow the Mule
application to be managed by API Manager?
A.
Register the same API implementation in Runtime Manager to connect to API Manager
B.
Modify the API implementation to useauto-discovery to register with API Manager
C.
Upload the Mule application's JAR file to the API instance in API Manager
D.
Deploy the same API implementation behind a VPC and configure the VPC to connect
to API Manager
Modify the API implementation to useauto-discovery to register with API Manager
Refer to the exhibit.
The main flow contains a Flow Reference for the child flow.
What values are accessible in the child flow after a webclient submits a request to
http://localhost:8Q81/order? color=red?
A.
payload
B.
payload
quantity var
C.
payload
color query param
D.
payload
quantity var color query param
payload
quantity var color query param
Refer to the exhibits.
The Mule application configures and uses two HTTP Listener global configuration
elements.
Mule application is run in Anypoint Studio.
If the mule application starts correctly, what URI and port numbers can receive web client
requests? If the mule applications fails to start , what is the reason for the failure?
A. The mule application fails to start. There is URL path conflict because both HTTP Listeners are configured with same path
B. The mule application start successfully Web client requests can only be received at URI on port 2222 but not on port 3333
C. The mule application fails to start because of the port binding conflict as HTTP request also use same port i.e. 3333
D. The mule application start successfully Web client requests can be received at URI on port 2222 and on port 3333.
In this case both the flows can start without any error and requests can be received on both ports. Flow names httpListener1 can call other flow using HTTP request without any issues.
A Utlility.dwl is located in a Mule project at src/main/resources/modules. The Utility.dwl file defines a function named encryptString that encrypts a String What is the correct DataWeave to call the encryptString function in a Transform Message component?
A. 1. %dw 2.0
2. output application/json
3. import modules::Utility
4. ---
5. Utility::encryptString( "John Smith" )
B. 1. %dw 2.0
2. output application/json
3. import modules::Utility
4. ---
5. encryptString( "John Smith" )
C. 1. %dw 2.0
2. output application/json
3. import modules.Utility
4. ---
5. encryptString( "John Smith" )
D. 1. %dw 2.0
2. output application/json
3. import modules.Utility
4. ---
5. Utility.encryptString( "John Smith" )
Explanation:
Correct answer is
%dw 2.0
output application/json
import modules::Utility
---
Utility::encryptString( "John Smith" )
DataWeave 2.0 functions are packaged in modules. Before you begin, note that
DataWeave 2.0 is for Mule 4 apps. For Mule 3 apps, refer to DataWeave Operators in the
Mule 3.9 documentation. For other Mule versions, you can use the version selector for the
Mule Runtime table of contents.
Functions in the Core (dw::Core) module are imported automatically into your DataWeave
scripts. To use other modules, you need to import the module or functions you want to use
by adding the import directive to the head of your DataWeave script, for example:
import dw::core::Strings
import camelize, capitalize from dw::core::Strings
import * from dw::core::Strings
The way you import a module impacts the way you need to call its functions from a
DataWeave script. If the directive does not list specific functions to import or use * from to
import all functions from a function module, you need to specify the module when you call
the function from your script. For example, this import directive does not identify any
functions to import from the String module, so it calls the pluralize function like this:
Strings::pluralize("box").
Transform
%dw 2.0
import dw::core::Strings
output application/json
---
{ 'plural': Strings::pluralize("box") }
Refer to the exhibit.
A Mule event is composed of ahierarchy of objects. Where in the hierarchy are variables
stored?
A.
Mule event
B.
Mule message payload
C.
Mule message
D.
Mule message attributes
Mule message
An On Table Row Database listener retrieves data from a table that contains record_id, an
increasing numerical column.
How should the listener be configured so it retrieves new rows at most one time?
A.
Set the target tostore the last retrieved record_id value
B.
Set the ObjectStore to store the last retrieved record_id value
C.
Set the target to the record_id column
D.
Set the watermark column to the record id column
Set the watermark column to the record id column
Refer to the exhibits.
What payload and quantity are logged at the end of the main flow?
A. [[1,2,3,4], 14]
B. [[order1, order2, order3, order4], 14]
C. [[1,2,3,4], 10]
D. [orderlorder2order3order4,14]
Mule application contains ActiveMQ JMS dependency. Mule application was compiled and run successfully in Anypoint Studio. The mule application must now be exported from Anypoint Studio and shared with other developer. What export options should be selected to create the smallest JAR file that can be imported into other developer's Anypoint Studio and run successfully?
A. Select only Attach Project Sources only
B. Select both Attach Project Sources and Include project modules and dependencies option
C. Select the Include project modules and dependencies option only
D. De-select both Attach Project Sources and Include project modules and dependencies option
Explanation:
Correct answer is Select only Attach Project Sources only.
You must keep the Attach Project Sources option selected to be able to import the
packaged JAR file back into a Studio workspace.
Deselect the Include project modules and dependencies option.
This option skips bundling the actual modules and external dependencies required to run
the Mule application in a Mule runtime engine, creating a lightweight JAR file package that
does not include any dependencies specified in the Mule application’s pom.xml file.
The generated JAR file is not a functional deployable archive and cannot be deployed to a
Mule runtime engine, but instead offers a way to archive only the source files that make up
the Mule application. This is the same as using the -lightWeightPackage flag when
packaging using the Mule Maven Plugin and is useful if you want to distribute your project
to other Studio installations because it only keeps a reference to all its dependencies.
When you import a lightweight package into Studio, all your dependencies are
automatically downloaded.
| Page 1 out of 29 Pages |
Contact Us - Privacy Policy ... Copyright © - All Rights Reserved