exam questions

Exam DP-600 All Questions

View all questions & answers for the DP-600 exam

Exam DP-600 topic 1 question 62 discussion

Actual exam question from Microsoft's DP-600
Question #: 62
Topic #: 1
[All DP-600 Questions]

Case study -

This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.

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 -
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.


Overview -

Litware, Inc. is a manufacturing company that has offices throughout North America. The analytics team at Litware contains data engineers, analytics engineers, data analysts, and data scientists.


Existing Environment -


Fabric Environment -

Litware has been using a Microsoft Power BI tenant for three years. Litware has NOT enabled any Fabric capacities and features.


Available Data -

Litware has data that must be analyzed as shown in the following table.



The Product data contains a single table and the following columns.



The customer satisfaction data contains the following tables:

• Survey
• Question
• Response

For each survey submitted, the following occurs:

• One row is added to the Survey table.
• One row is added to the Response table for each question in the survey.

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 -

The analytics team has large volumes of data, some of which is semi-structured. The team wants to use Fabric to create a new data store.

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 -


Planned Changes -

Litware plans to enable Fabric features in the existing tenant. The analytics team will create a new data store as a proof of concept (PoC). The remaining Liware users will only get access to the Fabric features once the PoC is complete. The PoC will be completed by using a Fabric trial capacity

The following three workspaces will be created:

• AnalyticsPOC: Will contain the data store, semantic models, reports pipelines, dataflow, and notebooks used to populate the data store
• DataEngPOC: Will contain all the pipelines, dataflows, and notebooks used to populate OneLake
• DataSciPOC: Will contain all the notebooks and reports created by the data scientists

The following will be created in the AnalyticsPOC workspace:

• A data store (type to be decided)
• A custom semantic model
• A default semantic model
• Interactive reports

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 -

The data store must support the following:

• Read access by using T-SQL or Python
• Semi-structured and unstructured data
• Row-level security (RLS) for users executing T-SQL queries

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-SOL. queries and in the default semantic model. The following logic must be used:

• List prices that are less than or equal to 50 are in the low pricing group.
• List prices that are greater than 50 and less than or equal to 1,000 are in the medium pricing group.
• List prices that are greater than 1,000 are in the high pricing group.


Security Requirements -

Only Fabric administrators and the analytics team must be able to see the Fabric items created as part of the PoC.

Litware identifies the following security requirements for the Fabric items in the AnalyticsPOC workspace:

• Fabric administrators will be the workspace administrators.
• The data engineers must be able to read from and write to the data store. No access must be granted to datasets or reports.
• The analytics engineers must be able to read from, write to, and create schemas in the data store. They also must be able to create and share semantic models with the data analysts and view and modify all reports in the workspace.
• The data scientists must be able to read from the data store, but not write to it. They will access the data by using a Spark notebook
• The data analysts must have read access to only the dimensional model objects in the data store. They also must have access to create Power BI reports by using the semantic models created by the analytics engineers.
• The date dimension must be available to all users of the data store.
• The principle of least privilege must be followed.

Both the default and custom semantic models must include only tables or views from the dimensional model in the data store. Litware already has the following Microsoft Entra security groups:

• FabricAdmins: Fabric administrators
• AnalyticsTeam: All the members of the analytics team
• DataAnalysts: The data analysts on the analytics team
• DataScientists: The data scientists on the analytics team
• DataEngineers: The data engineers on the analytics team
• AnalyticsEngineers: The analytics engineers on the analytics team


Report Requirements -

The data analysts must create a customer satisfaction report that meets the following requirements:

• Enables a user to select a product to filter customer survey responses to only those who have purchased that product.
• Displays the average overall satisfaction score of all the surveys submitted during the last 12 months up to a selected dat.
• Shows data as soon as the data is updated in the data store.
• Ensures that the report and the semantic model only contain data from the current and previous year.
• Ensures that the report respects any table-level security specified in the source data store.
• Minimizes the execution time of report queries.


You need to implement the date dimension in the data store. The solution must meet the technical requirements.

What are two ways to achieve the goal? Each correct answer presents a complete solution.

NOTE: Each correct selection is worth one point.

  • A. Populate the date dimension table by using a dataflow.
  • B. Populate the date dimension table by using a Copy activity in a pipeline.
  • C. Populate the date dimension view by using T-SQL.
  • D. Populate the date dimension table by using a Stored procedure activity in a pipeline.
Show Suggested Answer Hide Answer
Suggested Answer: AD 🗳️

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
neoverma
Highly Voted 1 year ago
Selected Answer: AD
as per the technical requirements - "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." No existing data source & The date dimension must always contain dates from 2010 through the end of the current year is the Key Point here using the elimination method View wont be appropriate and COPY activity cant be used since there is no data source for DATE table. so the answer is A and D
upvoted 33 times
...
DirectX
Highly Voted 11 months, 3 weeks ago
C,D. I always create dimDate using a views (T-Sql select statement with recursive CTE). A. is too complicated.
upvoted 9 times
testtaker45
3 months, 2 weeks ago
Thank you for your answer. I would say A, D. You would use T-SQL at the data frame layer in a Notebook, this wouldn't be at the Data Source Layer. That is the trick, to be affecting the Data Source.
upvoted 1 times
...
os_ca
11 months ago
I am not able to create a view with CTE. Could you let us know how?
upvoted 3 times
...
...
zxc01
Most Recent 5 days, 12 hours ago
Selected Answer: AB
A is normal method. C is based on view but we cannot build date table in Lakehouse with view because there are no source data. D is not correct because we cannot build s SP which can load data to lakehouse because SQL endpoint is read only. We cannot add DML, such as insert, delete or update in SP. B is complicated method, but it can be worked. We can build a SP in lakehouse to generate date dimension data and use copy activity to connect it with SQL endpoint(you cannot find lakehouse and need Azure Synapse Analyse as connection) as Source. And you can use Lakehouse as destination.
upvoted 1 times
...
bc5468521
4 months, 3 weeks ago
Selected Answer: CD
Traditional way to create date dimension
upvoted 1 times
...
c119533
7 months, 3 weeks ago
It is specified: "The data store must support the following: Semi-structured and unstructured data". So the data store is a lakehouse. Stored procedures don't exist in a lakehouse. I think A and C
upvoted 3 times
...
stv
9 months, 2 weeks ago
C, D it says POPULATE, not CREATE... you cannot create tables with SPs in a lakehouse, BUT you CAN populate already existing ones!
upvoted 1 times
...
b6daab0
10 months, 3 weeks ago
ChatGDP chose AB. It says "Copy activity in tools like Azure Data Factory (ADF) allows you to copy data from various sources to your data warehouse. For a date dimension, you can generate the required dates using a source query or script and use the Copy activity to load them into your dimension table." and "While using a stored procedure can also achieve this, it typically requires more complex management and might not be as straightforward or flexible as using dataflows or copy activities, which are specifically designed for ETL (Extract, Transform, Load) processes."
upvoted 1 times
...
b6daab0
10 months, 3 weeks ago
correction: ChatGDP says A and C
upvoted 1 times
...
b6daab0
10 months, 3 weeks ago
ChatGPT says the answer should be A and D :)
upvoted 1 times
...
DarioReymago
10 months, 3 weeks ago
Selected Answer: AC
I prefered A & C. B&D need more steps to be created
upvoted 2 times
6d1de25
9 months, 4 weeks ago
I agree
upvoted 1 times
...
...
dev2dev
10 months, 4 weeks ago
Selected Answer: CD
C & D looks correct. A will be completed. C would need a new object to be created, rather we can simply use a one time script.
upvoted 1 times
...
David_Webb
11 months, 1 week ago
Selected Answer: AD
A and D should be the right answer to go.
upvoted 1 times
...
stilferx
11 months, 4 weeks ago
Selected Answer: AD
IMHO, AD may be good Agree, B is not good, C is just a weird way. But possible. So, the question is kind of ambiguous, with no particular directions from the Microsoft site. Among ABD, I am choosing AD
upvoted 3 times
stilferx
11 months, 4 weeks ago
Sorry, among ACD, I am choosing AD. That's what I meant
upvoted 2 times
...
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago