Tibco TCP-BW6 Exam - Topic 4 Question 79 Discussion

Actual exam question for Tibco's TCP-BW6 exam

Question #: 79
Topic #: 4

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?

A/employee/[id]

B/employee/id

C/employee/(id)

D/employee/{id}

Show Suggested Answer

Suggested Answer: B, E

by Brett at Dec 27, 2023, 12:32 PM

Limited Time Offer

25%

Off

Get Premium TCP-BW6 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Gilma

6 months ago

Is it really that straightforward? What about versioning?

upvoted 0 times

...

Angelo

7 months ago

I’m surprised they didn’t include a more descriptive path.

upvoted 0 times

...

Chauncey

7 months ago

Wait, why not A? It looks pretty valid too.

upvoted 0 times

...

Francisca

7 months ago

Totally agree, D makes the most sense!

upvoted 0 times

...

Patria

7 months ago

I think option D is the correct one. It uses curly braces for path parameters.

upvoted 0 times

...

Shelba

7 months ago

I’m a bit confused about the syntax. I thought it could be either curly braces or parentheses, but I guess D is the most common format?

upvoted 0 times

...

Ranee

8 months ago

I feel like I've seen a similar question before, and I think the placeholder for the ID should be in curly braces, so option D sounds right to me.

upvoted 0 times

...

Gail

8 months ago

I'm not entirely sure, but I remember something about using square brackets in RESTful paths. Maybe option A is correct?

upvoted 0 times

...

Casandra

8 months ago

I think the correct format for the service path should include curly braces for the ID, like in option D. It seems to match what we practiced.

upvoted 0 times

...

Penney

8 months ago

I'm pretty confident that the correct answer is D. The service path should use a dynamic path parameter to represent the employee ID, following the RESTful conventions.

upvoted 0 times

...

Quentin

8 months ago

I'm a bit unsure about this one. Is the ID supposed to be part of the path or just a query parameter? I'll need to double-check the RESTful best practices.

upvoted 0 times

...

Alita

8 months ago

Hmm, this looks like a tricky one. I'll need to think carefully about how to structure the service path to match the RESTful design principles.

upvoted 0 times

...

Weldon

8 months ago

Okay, I think I've got this. The key is to use a dynamic path parameter for the employee ID, so the answer is D. /employee/{id}.

upvoted 0 times

...

Brunilda

8 months ago

This looks like a straightforward question about cloud security solutions. I'll need to carefully read the options and think about which one best fits the description of a "software platform for public cloud security and compliance orchestration."

upvoted 0 times

...

Steffanie

8 months ago

Okay, I've got a strategy here. I'll focus on the core architectural benefits of keeping the transaction log in the database rather than a file system. Things like improved replication, performance, and consistency across data centers seem relevant.

upvoted 0 times

...

Leonor

1 year 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

Lorrine

11 months ago

User 4: Curly braces for the win!

upvoted 0 times

...

Elza

1 year ago

User 3: Definitely, option D is the best choice for the service path

upvoted 0 times

...

Izetta

1 year ago

User 2: I agree, curly braces make it clear that it's a variable

upvoted 0 times

...

Mila

1 year ago

User 1: I think the answer is D) /employee/{id}

upvoted 0 times

...

Kimberely

1 year ago

I'm going with option D. Curly braces are the industry-standard for representing dynamic parameters in REST APIs.

upvoted 0 times

Micaela

12 months 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

12 months 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

1 year ago

I agree, using curly braces for the ID parameter is the standard practice in RESTful services.

upvoted 0 times

...

Lashon

1 year ago

Option D is the correct choice. It's important to use curly braces for dynamic parameters in REST APIs.

upvoted 0 times

...

Matthew

1 year ago

I agree, using curly braces for the ID parameter is the standard practice in RESTful services.

upvoted 0 times

...

Laurene

1 year ago

Option D is the correct choice. It's important to use curly braces for dynamic parameters in REST APIs.

upvoted 0 times

...

Joaquin

1 year 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

1 year 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

1 year ago

I agree, using curly braces for dynamic parameters is a common practice in RESTful services.

upvoted 0 times

...

Gail

1 year 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

1 year 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

1 year 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

1 year 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

...