A. Select the corresponding pull policy.

B. Enable the engagement engine.

C. Configure advanced routing.

D. Select the Chat check box that is associated with an agent's staff account.

E. Select the Pull Chat check box in the chat profile.

A. Advanced

B. Standard

C. Manual

D. Round Robin

E. Strict Priority

F. First Due

A. It is required to create an incident.

B. It is widely used in Business-to-Business scenarios.

C. It has a one-to-many relation with contacts.

D. It has a one-to-one relation with contacts.

E. It can be associated with incidents directly.

A. All the permissions from an imported report remain unchanged after an export.

B. Reports must be exported manually in all interfaces.

C. The owner of a report remains the same even if the report is imported by some other user.

D. Published reports can be modified.

E. Reports are not common across the interface.

F. Reports are shared between interfaces.

G. After a report is published, the report data remains unchanged even as the knowledge base is updated.

A. You need to use the export and import option.

B. You need to copy and paste the source code across the multiple interfaces.

C. The change is reflected across all interfaces by default.

D. You need to re-create the message template across the multiple interfaces.

A. round

B. bitand

C. rand

D. floor

E. truncate

F. lower

G. to_number

H. ceiling

I. length

J. power

A. Filtering on standard fields that are indexed

B. Configuring many-to-many joins

C. Filtering on expressions and not on simple columns

D. Using outer joins rather than inner joins when possible

E. Providing values for runtime filters

F. Using the complex expression operator instead of the like operator

G. Providing default values for runtime filters

H. Using fixed filters whenever possible

I. Using the like operator instead of the complex expression operator

J. Using index custom fields as filters

K. Filtering on simple columns and not on expressions

A. A catch-all escalation action has no impact on incident rules.

B. A catch-all incident rule should be typically at the bottom of the rules listed in the initial state.

C. A catch-all rule has no impact on incident rules.

D. Incident rules should have one rule state.

E. Queues, staff accounts, custom fields, and profiles must be functioning before rules can be built based on them.

F. All incident rules should have an action to transit from the initial state to another state.

G. Incident rules should have a minimum of two rule states.