Refer to the exhibits.
What is the response when a client submits a request to http://localhost:8081?
A. After
B. null
C. Before
D. Validation error
Here’s specifically what is happening here:
1) Payload is successfully set to “Before”
2) Is null validation is used which will pass the message only if payload is null. In this case
as payload is not null, it creates an Error Object. Flow execution stops
#[error.description] = “Validation error”
3) Because no error handler is defined, the Mule default error handler handles the error
4) “Validation error” is the error message returned to the requestor in the body of the HTTP
request with HTTP Status Code: 500
Reference diagram:
Refer to the exhibits.
The Mule Application is being debugged in Anypoint Studio and stops at breakpoint. What
is the value of payload displayed in debugger at this breakpoint?
A. Processing
B. Begin
C. Finished
Refer to the exhibits.
Client sends the request to ClientRequestFlow which calls
ShippingFlow using HTTP Request activity.
During E2E testing it is found that that HTTP:METHOD_NOT_ALLOWED error is thrown
whenever client sends request to this flow.
What attribute you would change in ClientRequestFlow to make this implementation work
successfully?
A. Change the method attribute value to "*’’
B. Change the path attribute value to "/api/ship"
C. Change the allowed method attributes value to "POST"
D. Change the protocol attribute value to "HTTPS"
Explanation:
Correct answer is Change the method attributes value to "POST".
It can be fixed in either of the two ways as below.
1) Changing method attribute to POST in ClientRequestFlow
2) Setting allowedMethods as PUT in ShippingFlow (but doesn't fit as question mentions
about changing ClientRequestFlow)
Refer to the exhibits.
How many private flows does APIKIt generate from RAML specification?
A. 1
B. 2
C. 3
D. 4
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 exhibit.
What payload is returned from a request to http//localhost.8081/
Refer to the exhibits, what payload is returned from a request tohttp://localhost;8081/?
A.
1
B.
2
C.
3
D.
4
3
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 happens to the attributes of a Mule event in a flow after an outbound HTTP Request is made?
A. Attributes are replaced with new attributes from the HTTP Request response (which might be null)
B. New attributes may be added from the HTTP response headers, but no headers are ever removed
C. Attributes do not change
D. Previous attributes are passed unchanged
Explanation:
Attributes are replaced with new attributes from the HTTP Request response.
Attributes include everything apart from Payload/body. For ex: Headers, query parameters,
URI parameters.
So, when outbound HTTP request is made, new attributes need to pass the outbound
HTTP request and old attributes are replaced.
I have created below diagram to make it easy for you to understand:
| Page 1 out of 29 Pages |
Contact Us - Privacy Policy ... Copyright © - All Rights Reserved