Cyber Monday 2024! 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 1 Question 8 Discussion

Actual exam question for Salesforce's Salesforce MuleSoft Developer I exam
Question #: 8
Topic #: 1
[All Salesforce MuleSoft Developer I Questions]

Refer to the exhibits.

The mule application implements a REST API that accepts GET request from two URL's which are as follows

1) http://acme.com/order/status

2) http://acme.com/customer/status

What path value should be set in HTTP listener configuration so that requests can be accepted for both these URL's using a single HTTP listener event source?

Show Suggested Answer Hide Answer
Suggested Answer: C

Correct answer is */status as it is the correct way to use wildcards while configuring path value in HTTP listener


Contribute your Thoughts:

Stefany
5 months ago
Haha, well this is a no-brainer. C) */status is the answer, hands down. Mule makes it easy!
upvoted 0 times
...
Teddy
5 months ago
I'm going with C) */status. Can't beat the elegance of a single wildcard, am I right? *winks*
upvoted 0 times
Val
3 months ago
Wildcard paths are definitely the way to go for flexibility in handling multiple URLs.
upvoted 0 times
...
Micaela
3 months ago
I think A) *[order,customer]/status could work too, covering both URLs.
upvoted 0 times
...
Quentin
4 months ago
I agree with you! C) */status seems like the most efficient option.
upvoted 0 times
...
Catarina
4 months ago
I'm going with C) */status. Can't beat the elegance of a single wildcard, am I right? *winks*
upvoted 0 times
...
Werner
4 months ago
I agree with User1, A) *[order,customer]/status seems like the right choice.
upvoted 0 times
...
Gaynell
4 months ago
I think A) *[order,customer]/status is the correct path value.
upvoted 0 times
...
...
Brandon
5 months ago
I agree with Lavonne, setting it as *[order,customer]/status seems like the correct choice
upvoted 0 times
...
Fatima
5 months ago
C) */status is the way to go. Keeps it simple and flexible for any future URL additions.
upvoted 0 times
Tawna
4 months ago
C) */status is the way to go. Keeps it simple and flexible for any future URL additions.
upvoted 0 times
...
Marylyn
4 months ago
A) *[order,customer]/status
upvoted 0 times
...
...
Casie
5 months ago
Ah, tricky one. I'd go with C) */status. Covers all the bases with a single listener configuration.
upvoted 0 times
Lorean
4 months ago
Great choice, C) */status is the way to go for this scenario.
upvoted 0 times
...
Rosio
5 months ago
I would also choose C) */status for accepting requests from both URL's.
upvoted 0 times
...
Desirae
5 months ago
Agreed, that option covers both URL's with a single listener configuration.
upvoted 0 times
...
Emily
5 months ago
I think C) */status is the correct path value.
upvoted 0 times
...
...
Lavonne
5 months ago
But if we set it as *[order,customer]/status, it will accept requests from both URLs
upvoted 0 times
...
Erick
6 months ago
I disagree, I believe it should be set as */status
upvoted 0 times
...
Lavonne
6 months ago
I think the path value should be set as *[order,customer]/status
upvoted 0 times
...
Milly
6 months ago
Hmm, I think the answer is C) */status. Makes sense to use a single wildcard to capture both '/order/status' and '/customer/status'.
upvoted 0 times
Ardella
5 months ago
Definitely, it's a more efficient way to configure the HTTP listener for those specific URLs.
upvoted 0 times
...
Lajuana
5 months ago
I think so too. Using a wildcard makes it easier to handle multiple paths with a single listener.
upvoted 0 times
...
Hildegarde
5 months ago
Agreed, C) */status seems like the correct choice. It will capture both URLs.
upvoted 0 times
...
...

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