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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Salesforce Certified MuleSoft Developer (Mule-Dev-201) Exam - Topic 1 Question 8 Discussion

Refer to the exhibits.The mule application implements a REST API that accepts GET request from two URL's which are as follows1) http://acme.com/order/status2) http://acme.com/customer/statusWhat 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?
C) */status
A) *[order,customer]/status
B) ?[order,customer]/status
D) *status

Salesforce Certified MuleSoft Developer (Mule-Dev-201) Exam - Topic 1 Question 8 Discussion

Actual exam question for Salesforce's Salesforce Certified MuleSoft Developer (Mule-Dev-201) exam
Question #: 8
Topic #: 1
[All Salesforce Certified MuleSoft Developer (Mule-Dev-201) 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


by Sherrell at Jun 20, 2024, 12:29 AM

Limited Time Offer

25%

Off

Get Premium Salesforce Certified MuleSoft Developer (Mule-Dev-201) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Jin
6 months ago
Not sure about this, can someone explain why *[order,customer]/status is wrong?
upvoted 0 times
...
Junita
6 months ago
I think option C is definitely the way to go!
upvoted 0 times
...
Ilona
7 months ago
Wait, why can't we use *status? Seems too simple.
upvoted 0 times
...
Annette
7 months ago
Totally agree, *[order,customer]/status won't work.
upvoted 0 times
...
Alverta
7 months ago
The correct path value is */status.
upvoted 0 times
...
Vivan
7 months ago
I vaguely recall that using just */status could work, but I’m not entirely confident if that would cover both endpoints correctly.
upvoted 0 times
...
Terrilyn
8 months ago
I’m a bit confused about the syntax. Was it *[order,customer]/status or something else? I need to double-check my notes on that.
upvoted 0 times
...
Latia
8 months ago
I think we practiced a similar question where we had to configure multiple paths. I feel like the answer might involve using a wildcard for both order and customer.
upvoted 0 times
...
Tijuana
8 months ago
I remember we discussed using wildcards in the HTTP listener configuration, but I'm not sure if it's just a single asterisk or something more specific.
upvoted 0 times
...
Danica
8 months ago
I've got an idea - the path value should use a wildcard to match both the "order" and "customer" parts of the URL. Maybe something like "*[order,customer]/status"?
upvoted 0 times
...
Floyd
8 months ago
I'm a bit confused by the question. What exactly is the HTTP listener configuration, and how do I need to set the path value to handle these two URLs?
upvoted 0 times
...
Matthew
8 months ago
Okay, let me think this through step-by-step. I need to find a path value that can match both the "order/status" and "customer/status" URLs.
upvoted 0 times
...
Amie
8 months ago
Hmm, this looks like a tricky one. I'll need to carefully analyze the URL patterns and think about how to use a single listener to handle both of them.
upvoted 0 times
...
Daryl
8 months ago
Ah, I see now. The key is to use a wildcard that can match either "order" or "customer" in the path. I think option A looks like the best solution here.
upvoted 0 times
...
Melvin
8 months ago
Okay, let's see. The subscriber key needs to be a unique identifier that can be used to track the subscriber across channels. Email and CRM ID both seem like good options that would meet that criteria. I'll go with those two.
upvoted 0 times
...
Gabriele
8 months ago
Hmm, this is a tricky one. There are a lot of factors to consider here - the advance directive, Mr. Farrell's family, his physician, and the health plan. I'll need to carefully weigh each option to determine the legally correct answer.
upvoted 0 times
...
Stefany
2 years ago
Haha, well this is a no-brainer. C) */status is the answer, hands down. Mule makes it easy!
upvoted 0 times
...
Teddy
2 years ago
I'm going with C) */status. Can't beat the elegance of a single wildcard, am I right? *winks*
upvoted 0 times
Val
2 years ago
Wildcard paths are definitely the way to go for flexibility in handling multiple URLs.
upvoted 0 times
...
Micaela
2 years ago
I think A) *[order,customer]/status could work too, covering both URLs.
upvoted 0 times
...
Quentin
2 years ago
I agree with you! C) */status seems like the most efficient option.
upvoted 0 times
...
Catarina
2 years ago
I'm going with C) */status. Can't beat the elegance of a single wildcard, am I right? *winks*
upvoted 0 times
...
Werner
2 years ago
I agree with User1, A) *[order,customer]/status seems like the right choice.
upvoted 0 times
...
Gaynell
2 years ago
I think A) *[order,customer]/status is the correct path value.
upvoted 0 times
...
...
Brandon
2 years ago
I agree with Lavonne, setting it as *[order,customer]/status seems like the correct choice
upvoted 0 times
...
Fatima
2 years ago
C) */status is the way to go. Keeps it simple and flexible for any future URL additions.
upvoted 0 times
Tawna
2 years ago
C) */status is the way to go. Keeps it simple and flexible for any future URL additions.
upvoted 0 times
...
Marylyn
2 years ago
A) *[order,customer]/status
upvoted 0 times
...
...
Casie
2 years ago
Ah, tricky one. I'd go with C) */status. Covers all the bases with a single listener configuration.
upvoted 0 times
Lorean
2 years ago
Great choice, C) */status is the way to go for this scenario.
upvoted 0 times
...
Rosio
2 years ago
I would also choose C) */status for accepting requests from both URL's.
upvoted 0 times
...
Desirae
2 years ago
Agreed, that option covers both URL's with a single listener configuration.
upvoted 0 times
...
Emily
2 years ago
I think C) */status is the correct path value.
upvoted 0 times
...
...
Lavonne
2 years ago
But if we set it as *[order,customer]/status, it will accept requests from both URLs
upvoted 0 times
...
Erick
2 years ago
I disagree, I believe it should be set as */status
upvoted 0 times
...
Lavonne
2 years ago
I think the path value should be set as *[order,customer]/status
upvoted 0 times
...
Milly
2 years 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
2 years ago
Definitely, it's a more efficient way to configure the HTTP listener for those specific URLs.
upvoted 0 times
...
Lajuana
2 years ago
I think so too. Using a wildcard makes it easier to handle multiple paths with a single listener.
upvoted 0 times
...
Hildegarde
2 years ago
Agreed, C) */status seems like the correct choice. It will capture both URLs.
upvoted 0 times
...
...

Save Cancel