Refer to the exhibits.
The main flow contains an HTTP Request. The HTTP Listeners and HTTP Request use default configurations.
A web client sends a GET request to the main flow's HTTP Listener that includes a modelName query parameter.
What values are accessible in the child flow?
When using an HTTP Request connector to invoke another flow, only the payload and attributes are passed to the child flow, not the variables. In the given scenario, the payload is certainly accessible in the child flow. The modelName query parameter, which is an attribute, would not be available because the variables do not get transferred, hence option A is correct as only the payload would be accessible.
A is correct
Answer should be B When passing from parent flow to child flow using HTTP Request, attributes, and payload are passed to child flow but variables are not passed as HTTP request has only attributes and payload in its body.
B IS Correct ... "payload modelName query param" , In HTTREQUEST node --- ayload and queryparameters gets passsed to the other flow , however variables do not get passed, where as in case of a simple flowreference, Variables too gets passed along with queryparams and payload [ which means entire mule Event] ... Here anwer is Option B..... Try a simple flow, u will understand better. Thanks!
It is A, checked on the practice exam you can do. Query parameters follow in flow references, not http requests, same with variables
B because QueryParam also go
we can access only payload in child flow ,i test in my studio also. option 'a' is correct....
WE CAN ONLY ABLE TO ACCESS THE PAYLOAD SINCE ITS A POST REQUEST
A is correct, queryParam doesnt go to child flow.
A is correct. D contradicts the answer to Question 2 : What does to the attributes of a Mule event happen in a flow after an outbound HTTP Request is made?
Attributes do not survive scope boundaries. The HTTP Request is a new scope
A correct
Key is "A web client sends a GET request to the main flow's HTTP Listener that includes a modelName query parameter." Send to main flows, so, child canot access to modelName query parameter. Correct is: A
A is correct
A is correct , i have executed and verified
A is correct, query param go in case of flow reference to child flow
A is correct Attributes never move to child flow when using a HTTP Request connector. Only in case of Flow reference
A is correct,query param go in case of flow reference to child flow