MENU
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?
Suggested Answer: C
Get Premium Salesforce Certified MuleSoft Developer (Mule-Dev-201) Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
Correct answer is */status as it is the correct way to use wildcards while configuring path value in HTTP listener
40 comments · newest first
JI
Jin
11 months ago
Not sure about this, can someone explain why *[order,customer]/status is wrong?
JU
Junita
11 months ago
I think option C is definitely the way to go!
IL
Ilona
12 months ago
Wait, why can't we use *status? Seems too simple.
AN
Annette
12 months ago
Totally agree, *[order,customer]/status won't work.
AL
Alverta
1 year ago
The correct path value is */status.
VI
Vivan
1 year ago
I vaguely recall that using just */status could work, but I’m not entirely confident if that would cover both endpoints correctly.
TE
Terrilyn
1 year 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.
LA
Latia
1 year 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.
TI
Tijuana
1 year 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.
DA
Danica
1 year 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"?
FL
Floyd
1 year 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?
MA
Matthew
1 year 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.
AM
Amie
1 year 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.
DA
Daryl
1 year 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.
ME
Melvin
1 year 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.
GA
Gabriele
1 year 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.
ST
Stefany
2 years ago
Haha, well this is a no-brainer. C) */status is the answer, hands down. Mule makes it easy!
TE
Teddy
2 years ago
I'm going with C) */status. Can't beat the elegance of a single wildcard, am I right? *winks*
VA
Val
2 years ago
Wildcard paths are definitely the way to go for flexibility in handling multiple URLs.
MI
Micaela
2 years ago
I think A) *[order,customer]/status could work too, covering both URLs.
QU
Quentin
2 years ago
I agree with you! C) */status seems like the most efficient option.
CA
Catarina
2 years ago
I'm going with C) */status. Can't beat the elegance of a single wildcard, am I right? *winks*
WE
Werner
2 years ago
I agree with User1, A) *[order,customer]/status seems like the right choice.
GA
Gaynell
2 years ago
I think A) *[order,customer]/status is the correct path value.
BR
Brandon
2 years ago
I agree with Lavonne, setting it as *[order,customer]/status seems like the correct choice
FA
Fatima
2 years ago
C) */status is the way to go. Keeps it simple and flexible for any future URL additions.
TA
Tawna
2 years ago
C) */status is the way to go. Keeps it simple and flexible for any future URL additions.
MA
Marylyn
2 years ago
A) *[order,customer]/status
CA
Casie
2 years ago
Ah, tricky one. I'd go with C) */status. Covers all the bases with a single listener configuration.
LO
Lorean
2 years ago
Great choice, C) */status is the way to go for this scenario.
RO
Rosio
2 years ago
I would also choose C) */status for accepting requests from both URL's.
DE
Desirae
2 years ago
Agreed, that option covers both URL's with a single listener configuration.
EM
Emily
2 years ago
I think C) */status is the correct path value.
LA
Lavonne
2 years ago
But if we set it as *[order,customer]/status, it will accept requests from both URLs
ER
Erick
2 years ago
I disagree, I believe it should be set as */status
LA
Lavonne
2 years ago
I think the path value should be set as *[order,customer]/status
MI
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'.
AR
Ardella
2 years ago
Definitely, it's a more efficient way to configure the HTTP listener for those specific URLs.
LA
Lajuana
2 years ago
I think so too. Using a wildcard makes it easier to handle multiple paths with a single listener.
HI
Hildegarde
2 years ago
Agreed, C) */status seems like the correct choice. It will capture both URLs.