MCD-LEVEL-1 · Question #207
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…
The correct answer is C. Change the allowed method attributes value to "POST". 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…
Question
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?
Exhibit
Options
- AChange the method attribute value to "*''
- BChange the path attribute value to "/api/ship"
- CChange the allowed method attributes value to "POST"
- DChange the protocol attribute value to "HTTPS"
How the community answered
(26 responses)- A12% (3)
- B4% (1)
- C81% (21)
- D4% (1)
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)
Topics
Community Discussion
No community discussion yet for this question.