Which of the following are valid for Transient Business Component? [Choose three]
-
TBCs provide a way to create task-specific data that can be displayed and edited in the user interface
-
TBCs are used to house data to control the flow or logic and are cleared when a task is completed
-
TBC does not stored the data in the database
-
TBC is based on S_TBC table
Transient Business Components (TBCs) are task-specific, in-memory structures that display and edit data without database persistence. They're cleared when tasks complete and used to control workflow logic. TBCs are not based on S_TBC table - they exist only in memory.
Transient Business Components (TBCs) in Siebel are used to hold task-specific, in-memory data for the UI — for example wizard or applet-level state — and are cleared once the task/session ends, rather than persisting anything to the database. Correctly, TBCs: (1) let you create and display/edit task-specific data in the UI, (2) hold flow/logic-control data cleared after the task completes, and (3) do not store any data in the database at all. The false option claims TBCs are 'based on S_TBC table' — this is incorrect because, by definition, transient business components are not backed by any physical database table (that's the whole point of being 'transient'), so there's no S_TBC table involved.