TIBCO Messaging 5 — Questions and Answers
Question 1: What does TIBCO EMS 'connection factory' configuration allow administrators to define?
- The list of allowed topics and queues
- Pre-configured connection settings (server URL, SSL, reconnect) that clients look up by name (Correct answer)
- The maximum number of messages per second per producer
- The encryption key used for message payloads
Correct answer: Pre-configured connection settings (server URL, SSL, reconnect) that clients look up by name
Connection factories are JNDI-accessible objects that encapsulate server URL, reconnection behavior, and SSL settings, simplifying client configuration.
Question 2: In TIBCO Rendezvous, what is a 'subject name' and what wildcard character represents a single element?
- A topic path where '*' matches a single element (Correct answer)
- A routing key where '%' matches a single element
- A subscription filter where '_' matches any single character
- A message header where '#' matches a single element
Correct answer: A topic path where '*' matches a single element
RV subject names use dot-separated hierarchical elements; '*' matches exactly one element and '>' matches one or more trailing elements.
Question 3: Which TIBCO EMS feature prevents a producer from overwhelming a slow consumer by pausing message production?
- Message prioritization
- Flow control (Correct answer)
- Consumer throttling
- Message batching
Correct answer: Flow control
EMS flow control signals producers to slow down or pause when destinations approach capacity limits, preventing memory exhaustion.
Question 4: What is the difference between a TIBCO EMS 'static' route and a 'dynamic' route?
- Static routes use SSL; dynamic routes do not
- Static routes are configured in tibemsd.conf at startup; dynamic routes are created at runtime via the API (Correct answer)
- Static routes only handle queues; dynamic routes handle topics
- Static routes replicate all messages; dynamic routes replicate only persistent messages
Correct answer: Static routes are configured in tibemsd.conf at startup; dynamic routes are created at runtime via the API
Static routes are defined in configuration files and loaded at server startup, while dynamic routes are created programmatically at runtime.
Question 5: In TIBCO EMS, what is the purpose of setting a 'redelivery delay' on a queue?
- It delays the first delivery of new messages to reduce burst load
- It introduces a wait period before a negatively-acknowledged message is redelivered (Correct answer)
- It schedules message delivery at a future time regardless of consumer state
- It batches multiple redeliveries into a single transfer
Correct answer: It introduces a wait period before a negatively-acknowledged message is redelivered
Redelivery delay adds a configurable pause between failed delivery attempts, preventing rapid retry storms that could overload consumers.
Question 6: Which TIBCO EMS administrative command-line tool is used to manage topics, queues, and connections on a running server?
- tibemsadmin (Correct answer)
- tibrvlisten
- tibemsctl
- rvd
Correct answer: tibemsadmin
tibemsadmin is the interactive command-line administrative client for TIBCO EMS, allowing real-time management of destinations, connections, and server properties.
Question 7: What happens in TIBCO EMS when a message's redelivery count exceeds the queue's configured 'redelivery.limit'?
- The message is permanently deleted without trace
- The message is moved to the Dead Message Queue (DMQ) (Correct answer)
- The message is returned to the original producer
- The message is converted to a non-persistent message and requeued
Correct answer: The message is moved to the Dead Message Queue (DMQ)
When redelivery attempts exceed the configured limit, EMS moves the undeliverable message to the DMQ for inspection and potential manual reprocessing.
TIBCO Messaging 5
What does TIBCO EMS 'connection factory' configuration allow administrators to define?