You are developing a SQL Server Analysis Services (SSAS) cube. The cube consists of a single
measure group.
The measure group consists of one partition that uses MOLAP.
The proactive caching policy has the following requirements:
The cache must be updated when data is changed in the table named tblOrders.
Changes must be notified through the use of the XML for Analysis (XMLA) NotifyTableChange
command.

You need to configure the proactive caching policy to meet the requirements.
Which three actions should you perform in sequence? (To answer, move the appropriate actions
from the list of actions to the answer area and arrange them in the correct order.)
Select and Place:

Answer:

Explanation:
Box 1: On the Partitions tab, Click Storage Settings
We specify the Storage Settings for the correct partition.
Box 2: Enable proactive caching.
We enable proactive caching.
Box 3: Select the Client initiated notification type, and then select the tblOrders table.
On the Notifications tab, there are three options out of which, as shown below, you can select any
one at a time.
* SQL Server – With this option, SSAS uses SQL Server notification services/specialized trace
mechanism to identify data changes.
* Client initiated – With this option, client can specify the XMLA (XML for Analysis) command
(NotifyTableChange) to identify data changes.
* Scheduled polling – With this option, SSAS uses a series of queries to see (polling at defined
interval) if there is any data change at the underlying relational database.

Note:
You use the Storage Settings dialog box in BIDS (Business Intelligence Development Studio) to
set the proactive caching feature, storage location, and notification settings for a dimension, cube,
measure group, or measure group partition.

The Custom Setting allows you to explicitly enable proactive caching (if you don’t want to use
Standard Setting), set storage mode, and notification options. (Box 2)