HOTSPOT
You are designing a SQL Server Analysis Services (SSAS) cube that contains two measure
groups named Sales History and Current Sales.
The Sales History measure group has the following characteristics:
Data changes on a monthly basis.
The measure group contains a very high data volume.
Queries that use the measure group only reference aggregate data.
The measure group includes SUM, MIN, MAX, and COUNT aggregate functions.
The Current Sales measure group has the following characteristics:
Data changes frequently.
The measure group contains a low data volume.
Queries that use the measure group often reference non-aggregate data.
The measure group includes SUM, MIN, MAX, and COUNT aggregate functions.
You need to select a storage mode for each measure group. The solution must meet the
following requirements:
For the Sales History measure group, query performance must be optimized over data
latency.
For the Current Sales measure group, data latency must be optimized over query
performance.
What should you do? To answer, select the appropriate storage mode for each measure
group in the answer area.
Answer: 
Sales History : Low-latency Molap
Current Sales: Low-latency Molap
0
0
http://www.200-120exam.com/wp-content/uploads/2015/02/clip_image01510.jpg
0
0
http://www.200-120exam.com/wp-content/uploads/2015/02/clip_image0178.jpg
0
0
For Current Sales-RT Rolap or RT Holap (cause told that Queries that use the measure group often reference non-aggregate data).
0
0
Sales History : Low-latency Molap
Current Sales = Real-Time Holap
0
0
I agree
0
0
sales History – MOLAP
Current Sales – Low Latency Molap
Sales HIstory Data changes on a monthly basis – therefore can be scheduled therefore MOLAP, NOT low Latency molap.
Current Sales: Low Latency Molap because question does not mention real-time but mentions that latency must be optimised
https://msdn.microsoft.com/en-us/library/ms175646.aspx
0
0
History mola
Current holap (as rola has problems with min and max)
https://msdn.microsoft.com/pl-pl/library/ms174915(v=sql.110).aspx
0
0
https://msdn.microsoft.com/pl-pl/library/ms175646(v=sql.110).aspx
0
0
should be
scheduled molap(latency is 24 hour, but it is fast)
holap (no latency, could support min/max)
?
0
0
Sales History : Automatic MOLAP
This setting is typically used for a data source when query performance is of key importance. This setting automatically processes MOLAP objects whenever required after the latency interval. Queries do not return the most recent data while the new cache is being built and processed.
Current Sales = Real-Time Holap
0
0