TIBCO Data Virtualization 5 — Questions and Answers
Question 1: In a TDV high-availability cluster, what is the role of the 'worker node' versus the 'coordinator node'?
- Worker nodes store physical data; coordinator nodes process metadata only
- Worker nodes execute query fragments in parallel; the coordinator node orchestrates query decomposition (Correct answer)
- Worker nodes handle user authentication; the coordinator node handles data access
- Worker nodes cache results; the coordinator node writes to the audit log
Correct answer: Worker nodes execute query fragments in parallel; the coordinator node orchestrates query decomposition
In TDV clusters, the coordinator decomposes and plans queries while worker nodes execute assigned fragments in parallel for scalability.
Question 2: What is the impact of setting a TDV virtual view's cache mode to 'Refresh on Demand' versus 'Scheduled Refresh'?
- Refresh on Demand loads data at server startup; Scheduled Refresh loads data continuously
- Refresh on Demand updates the cache only when explicitly triggered via API or admin action; Scheduled Refresh runs automatically at set intervals (Correct answer)
- Refresh on Demand is faster because it uses incremental updates; Scheduled Refresh always does full reloads
- Refresh on Demand is only available for file-based sources; Scheduled Refresh works for all sources
Correct answer: Refresh on Demand updates the cache only when explicitly triggered via API or admin action; Scheduled Refresh runs automatically at set intervals
Refresh on Demand gives manual control over cache updates, while Scheduled Refresh automates updates at defined time intervals.
Question 3: When exposing TDV virtual data as a REST service, which HTTP method is most appropriate for retrieving data from a virtual view?
- POST
- GET (Correct answer)
- PUT
- DELETE
Correct answer: GET
GET is the standard HTTP method for read-only data retrieval, and TDV REST services use GET to return query results from virtual views.
Question 4: Which TDV concept describes the ability to query data from a MongoDB collection alongside an Oracle relational table in a single SQL statement?
- Homogeneous federation
- Heterogeneous data federation (Correct answer)
- Cross-schema replication
- Polyglot persistence migration
Correct answer: Heterogeneous data federation
Heterogeneous data federation in TDV enables combining data from structurally different sources (NoSQL, relational, file) in a single unified query.
Question 5: In TDV, what is a 'parameterized view' and how does it differ from a standard view?
- A parameterized view stores results as a named dataset; a standard view recomputes on every access
- A parameterized view accepts input parameters to filter or modify query behavior; a standard view always returns the same result set definition (Correct answer)
- A parameterized view requires manual cache refresh; a standard view auto-refreshes
- A parameterized view can only be published via SOAP; a standard view supports all protocols
Correct answer: A parameterized view accepts input parameters to filter or modify query behavior; a standard view always returns the same result set definition
Parameterized views accept caller-supplied values (e.g., a date range or customer ID) that are injected into the query at runtime, unlike standard views with fixed logic.
Question 6: What TDV auditing capability records which user executed a query, on which resource, and at what timestamp?
- Execution Plan Log
- Query Audit Log (Correct answer)
- Introspection History
- Cache Access Report
Correct answer: Query Audit Log
The Query Audit Log in TDV captures detailed records of query activity including user identity, resource accessed, and execution time for compliance purposes.
Question 7: Which TDV feature enables developers to define custom transformation logic in Java and invoke it within a TDV SQL query?
- External Stored Procedure
- Custom Java Function (User-Defined Function) (Correct answer)
- Adapter Extension API
- SOAP Transformation Filter
Correct answer: Custom Java Function (User-Defined Function)
TDV supports User-Defined Functions written in Java that can be registered and called within SQL queries to extend built-in transformation capabilities.
In a TDV high-availability cluster, what is the role of the 'worker node' versus the 'coordinator node'?