Salesforce Exam Salesforce MuleSoft Developer I Topic 2 Question 17 Discussion

Actual exam question for Salesforce's Salesforce MuleSoft Developer I exam

Question #: 17
Topic #: 2

[All Salesforce 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?

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'

Show Suggested 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)

by James at Sep 13, 2024, 09:42 PM

Limited Time Offer

25%

Off

Get Premium Salesforce MuleSoft Developer I Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Alisha

2 months ago

Ah, the classic HTTP:METHOD_NOT_ALLOWED error. Happens to the best of us. Option C is the way to go, unless you want to be 'shipp-ing' your troubles to someone else.

upvoted 0 times

...

Marjory

2 months ago

Wait, what if the client is trying to send a GET request? Then Option C wouldn't work. Better keep it flexible with Option A, who knows what the client might try next?

upvoted 0 times

Lavonda

2 months ago

Alease is right, let's keep it flexible with Option A.

upvoted 0 times

...

Alease

2 months ago

But what if the client is trying to send a GET request?

upvoted 0 times

...

Kristal

2 months ago

I think we should change the method attribute value to '*'.

upvoted 0 times

...

Lorenza

2 months ago

Option D is definitely not the right choice here. HTTPS is for secure communication, not fixing a method mismatch. I agree with the other candidates, Option C is the way to go.

upvoted 0 times

Tom

1 months ago

I see your point, but I still think Option C is the best choice, changing the allowed method attributes value to 'POST'.

upvoted 0 times

...

Lorean

1 months ago

I disagree, Option B seems more appropriate, changing the path attribute value to '/api/ship'.

upvoted 0 times

...

France

2 months ago

I think Option A might work too, changing the method attribute value to '*'.

upvoted 0 times

...

Ronnie

3 months ago

I think changing the allowed method attributes value to 'POST' might also work, as it specifies the method allowed for the request.

upvoted 0 times

...

Catarina

3 months ago

Hmm, I'm not sure about that. Changing the method attribute to '*' might work, but it's a bit of a broad solution. I'd lean towards Option C to be more specific.

upvoted 0 times