Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam Salesforce-MuleSoft-Developer-I Topic 2 Question 17 Discussion

Actual exam question for Salesforce's Salesforce Certified MuleSoft Developer I exam
Question #: 17
Topic #: 2
[All Salesforce Certified MuleSoft Developer I Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: C

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)


Contribute your Thoughts:

Currently there are no comments in this discussion, be the first to comment!


Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77