TCP-EMS8 TIBCO Enterprise Message Service 8 Certification Exam Questions and Answers

When messages are sent to a queue with a store that is Ssys.failsafe

When messages are sent to a topic with no durable subscriber

When messages are sent to a queue with a PERSISTENT delivery mode

When messages are sent to a topic with one subscriber with a fault tolerant EMS connection

Map incoming messages only through the_ns_filed in the message

Map incoming messages directly to an event in TIBCO Business Events

Map incoming messages only through the_nm_field in the message

Map incoming messages through two fields (_ns_, _nm_) in the message

If a client does not receive heartbeats from EMS server for a period exceeding 20 seconds, the client will close the connection.

If a client does not receive heartbeats from EMS server for a period exceeding 10 seconds, the client will close the connection.

If EMS server does not receive heartbeats from a client for a period exceeding 20 seconds, the EMS server will close the connection.

If EMS server does not receive heartbeats from a client for a period exceeding 10 seconds, the EMS server will close the connection.

EMS "administered" objects include users/groups.

The EMS server and third-party naming/directory services automatically synchronize administered objects,

EMS client can perform JNDI lookups of administrated objects stored in third-party naming/directory services.

Dynamic topics are automatically added to the third-party naming/directory service.

EMS client can only perform JNDI lookups on static queues or topics.

The location of log file is set in tibemsd.conf file via the log_trace parameter.

Message tracing applies only to headers.

Message tracing can be applied at destination and message levels.

Access control violations can be logged to console or log file.

Processing Unit name

EAR file location

Destination collection

CDD file location

Rule collection

They can be applied only on header of the message.

They can be applied on bridges and routes.

They can be applied on header, properties, and body of the message.

They can be applied only on header and properties of the message.

A CDD needs to be rebuilt when a new rule is added to the project.

Deployment requires both a CDD and the project.

Deployment requires both CDD and EAR files.

A project can have a one-to-many relationship with a CDD.

A CDD can be associated with only Object Management type at any given time.

return a SOAP fault

return a constructed reply message

loop and try again

update a database

A Processing Unit containing a Cache agent acts as a cache server.

Multiple Inference agents can be run in a single Processing Unit.

Inference agents and Cache agents can co-exits in a Processing Unit.

A rule in one Processing Unit cannot trigger a rule in a different Processing Unit.

from a service in one SCA composite to a reference of another SCA composite

from a reference in one SCA comopsite to a service of another SCA composite

from a component reference to a component service in the same SCA composite

from a component service to a component reference in the same SCA composite

The entire table represents a rule.

A rule function's arguments represent columns of a table.

Each row in the table represents a rule.

Each table can have one exception table.

reserve memory

max_msg_memory

reserve_msg_memory

max_memory

compliant_ack_check

non persistent

confirm ok

npsend_check_mode

Text Messages

Map Messages

XML Messages

Stream Messages

create a single node that spans multiple hosts to provide resiliency in the event of host failure

specify virtualization upon service deployment allowing Active matrix to transparently recover a failed service

deploy the service in the system node so the Active matrix infrastructure can manage availability

deploy the service across multiple nodes: TIBCO Enterprise Message Service delivers

Its settings define backing store database connection pools.

It contains the settings necessary to enable the JMX connector.

It is mandatory when running the be-engine.

It is used to select backing store database types.

It defines the classpath for Java libraries exiting outside of the project

Synchronous In-Out with SOAP/JMS

Synchronous Out-In with XML over JMS

Asynchronous In-Out with Soap/HTTP

Asynchronous Out-Only with XML over JMS

Header

Envelope

Body

Properties

Footer