11.  Maintain a data analytics solution 
Testlet 2 
Case study
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study. 
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section. 
To start the case study
Overview
Existing Environment
Available Data
The Product data contains a single table and the following columns. 
The customer satisfaction data contains the following tables:
For each survey submitted, the following occurs:
The Question table contains the text of each survey question. The third question in each survey response is an overall satisfaction score. Customers can submit a survey after each purchase. 
User Problems
Product data is often classified into three pricing groups: high, medium, and low. This logic is implemented in several databases and semantic models, but the logic does NOT always match across implementations. 
Requirements
The following three workspaces will be created:
The following will be created in the AnalyticsPOC workspace:
The data engineers will create data pipelines to load data to OneLake either hourly or daily depending on the data source. The analytics engineers will create processes to ingest, transform, and load the data to the data store in the AnalyticsPOC workspace daily. Whenever possible, the data engineers will use low-code tools for data ingestion. The choice of which data cleansing and transformation tools to use will be at the data engineers’ discretion. 
All the semantic models and reports in the Analytics POC workspace will use the data store as the sole data source. 
Technical Requirements
Files loaded by the data engineers to OneLake will be stored in the Parquet format and will meet Delta Lake specifications. 
Data will be loaded without transformation in one area of the AnalyticsPOC data store. The data will then be cleansed, merged, and transformed into a dimensional model. 
The data load process must ensure that the raw and cleansed data is updated completely before populating the dimensional model. 
The dimensional model must contain a date dimension. There is no existing data source for the date dimension. The Litware fiscal year matches the calendar year. The date dimension must always contain dates from 2010 through the end of the current year. 
The product pricing group logic must be maintained by the analytics engineers in a single location. The pricing group data must be made available in the data store for T-SQL queries and in the default semantic model.
Security Requirements
Litware identifies the following security requirements for the Fabric items in the AnalyticsPOC workspace:
Both the default and custom semantic models must include only tables or views from the dimensional model in the data store.
Report Requirements
HOTSPOT