Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Tibco Exam TCP-BW6 Topic 4 Question 79 Discussion

Actual exam question for Tibco's TCP-BW6 exam
Question #: 79
Topic #: 4
[All TCP-BW6 Questions]

You need to create a RESTful service in TIBCO ActiveMatrix BusinessWorks for an employee resource that has the following fields: ID, FirstName, LastName, Salary. How should you configure the resource Service Path for a service that returns the employee resource by ID?

Show Suggested Answer Hide Answer
Suggested Answer: B, E

Contribute your Thoughts:

Leonor
1 months ago
Option D is the clear winner here. Curly braces are the way to go, unless you want your API to look like it was designed by a caveman.
upvoted 0 times
Elza
15 days ago
User 3: Definitely, option D is the best choice for the service path
upvoted 0 times
...
Izetta
16 days ago
User 2: I agree, curly braces make it clear that it's a variable
upvoted 0 times
...
Mila
21 days ago
User 1: I think the answer is D) /employee/{id}
upvoted 0 times
...
...
Kimberely
1 months ago
I'm going with option D. Curly braces are the industry-standard for representing dynamic parameters in REST APIs.
upvoted 0 times
Micaela
4 days ago
Curly braces make it clear that the ID in the service path is a dynamic parameter that will be replaced with the actual ID value.
upvoted 0 times
...
Tamra
9 days ago
Curly braces make it clear that the ID in the service path is a dynamic parameter that will be replaced with the actual ID value.
upvoted 0 times
...
Britt
16 days ago
I agree, using curly braces for the ID parameter is the standard practice in RESTful services.
upvoted 0 times
...
Lashon
16 days ago
Option D is the correct choice. It's important to use curly braces for dynamic parameters in REST APIs.
upvoted 0 times
...
Matthew
21 days ago
I agree, using curly braces for the ID parameter is the standard practice in RESTful services.
upvoted 0 times
...
Laurene
1 months ago
Option D is the correct choice. It's important to use curly braces for dynamic parameters in REST APIs.
upvoted 0 times
...
...
Joaquin
2 months ago
Option D is the way to go. Curly braces are the standard for representing dynamic parameters in RESTful service paths.
upvoted 0 times
Aimee
19 days ago
Thanks for the clarification, I will make sure to use curly braces for dynamic parameters in my RESTful service paths.
upvoted 0 times
...
Shanice
22 days ago
I agree, using curly braces for dynamic parameters is a common practice in RESTful services.
upvoted 0 times
...
Gail
1 months ago
Option D is the way to go. Curly braces are the standard for representing dynamic parameters in RESTful service paths.
upvoted 0 times
...
...
Alida
2 months ago
Option A looks good to me. Using square brackets to enclose the ID makes it clear that it's a dynamic parameter.
upvoted 0 times
...
Alison
2 months ago
I'm not sure about the answer. Can someone explain why using curly braces is better than other options like square brackets or parentheses?
upvoted 0 times
...
Brett
2 months ago
I agree with Johanna. Using curly braces for the ID parameter in the service path makes it clear that it's a variable that will be replaced with the actual ID.
upvoted 0 times
...
Johanna
2 months ago
I think the correct answer is D) /employee/{id}. It's a common practice to use curly braces for dynamic parameters in RESTful services.
upvoted 0 times
...
Gertude
2 months ago
I think option D is the correct answer. The resource path should use curly braces to represent the dynamic ID parameter.
upvoted 0 times
Royal
1 months ago
Yes, option D is the right choice for configuring the resource Service Path.
upvoted 0 times
...
Royal
1 months ago
I agree, option D is the correct answer.
upvoted 0 times
...
Johnetta
2 months ago
Yes, option D with curly braces for the dynamic ID parameter.
upvoted 0 times
...
Johnetta
2 months ago
I agree, option D is the correct answer.
upvoted 0 times
...
...
Blythe
2 months ago
I'm not sure, but I think A) /employee/[id] could also work since it specifies the ID parameter in square brackets.
upvoted 0 times
...
Shawnee
2 months ago
I agree with Flo, using curly braces for the ID parameter is the standard RESTful convention.
upvoted 0 times
...
Flo
3 months ago
I think the correct answer is D) /employee/{id)
upvoted 0 times
...

Save Cancel