What attribute you would change in ClientRequestFlow to make this implementation work successfully?

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"

Answer: C

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)