TIBCO Middleware Concepts 3 — Questions and Answers
Question 1: What is the difference between a JMS Queue and a JMS Topic in TIBCO EMS?
- Queues support multiple publishers; Topics support only one
- Queues use point-to-point delivery; Topics use publish-subscribe delivery (Correct answer)
- Queues persist messages forever; Topics delete them immediately
- Queues require SSL; Topics do not
Correct answer: Queues use point-to-point delivery; Topics use publish-subscribe delivery
A Queue delivers each message to exactly one consumer (P2P), while a Topic delivers each message to all active subscribers (pub/sub).
Question 2: In TIBCO ActiveMatrix BusinessWorks 6, what is the primary unit of deployment?
- An EAR file
- An OSGi bundle packaged as an Application Archive (.ear) (Correct answer)
- A WAR file deployed to Tomcat
- A JAR file with a Main-Class manifest
Correct answer: An OSGi bundle packaged as an Application Archive (.ear)
BW6 applications are packaged as OSGi-based Application Archives (.ear) deployed to the ActiveMatrix runtime.
Question 3: Which TIBCO component acts as a service registry and repository in a SOA environment?
- TIBCO EMS
- TIBCO ActiveMatrix Service Grid (Correct answer)
- TIBCO BusinessConnect
- TIBCO Administrator
Correct answer: TIBCO ActiveMatrix Service Grid
TIBCO ActiveMatrix Service Grid provides service governance including registry, policy enforcement, and lifecycle management.
Question 4: What does 'message acknowledgment mode AUTO_ACKNOWLEDGE' mean in JMS?
- The broker auto-encrypts messages before sending
- The session automatically acknowledges each message when the receive call returns (Correct answer)
- Messages are acknowledged only after manual commit
- The consumer acknowledges batches of 10 messages at a time
Correct answer: The session automatically acknowledges each message when the receive call returns
In AUTO_ACKNOWLEDGE mode, the JMS session automatically sends an acknowledgment to the broker immediately after a message is received.
Question 5: In TIBCO middleware, what is 'message fanout'?
- Splitting a large message into smaller chunks for delivery
- Delivering the same message to multiple consumers or destinations simultaneously (Correct answer)
- Routing messages to the least-loaded consumer
- Archiving messages to cold storage after delivery
Correct answer: Delivering the same message to multiple consumers or destinations simultaneously
Message fanout distributes a single published message to multiple subscribers or destination queues at the same time.
Question 6: What is the purpose of TIBCO Hawk in a TIBCO middleware environment?
- To provide API gateway functionality
- To monitor and manage distributed TIBCO processes and system resources (Correct answer)
- To synchronize database transactions across nodes
- To handle B2B EDI document transformation
Correct answer: To monitor and manage distributed TIBCO processes and system resources
TIBCO Hawk is an agent-based monitoring tool that watches TIBCO services and system metrics and can take automated corrective actions.
Question 7: In TIBCO EMS, what happens to non-persistent messages if the EMS server restarts?
- They are recovered from a transaction log
- They are lost because they are not written to disk (Correct answer)
- They are held in consumer memory and redelivered
- They are forwarded to a dead-letter queue automatically
Correct answer: They are lost because they are not written to disk
Non-persistent messages are stored only in memory and are discarded when the EMS server shuts down or crashes.
TIBCO Middleware Concepts 3
What is the difference between a JMS Queue and a JMS Topic in TIBCO EMS?