PL-300 Question #5: Real Exam Question with Answer & Explanation

Question

Case Study 1 - Litware, Inc. Overview Litware, Inc. is an online retailer that uses Microsoft Power Bl dashboards and reports. The company plans to leverage data from Microsoft SQL Server databases, Microsoft Excel files, text files, and several other data sources. Litware uses Azure Active Directory (Azure AD) to authenticate users. Existing Environment Sales Data Litware has online sales data that has the SQL schema shown in the following table. In the Date table, the dateid column has a format of yyyymmdd and the month column has a format of yyyymm. The week column in the Date table and the weekid column in the Weekly_Returns table have a format of yyyyww. The regionid column can be managed by only one sales manager. Data Concerns You are concerned with the quality and completeness of the sales data. You plan to verify the sales data for negative sales amounts. Reporting Requirements Litware identifies the following technical requirements: - Executives require a visual that shows sales by region. - Regional managers require a visual to analyze weekly sales and returns. - Sales managers must be able to see the sales data of their respective region only. - The sales managers require a visual to analyze sales performance versus sales targets. - The sale department requires reports that contain the number of sales transactions. - Users must be able to see the month in reports as shown in the following example: Feb 2020. - The customer service department requires a visual that can be filtered by both sales month and ship month independently. - The maximum allowed latency to include transactions in reports is five minutes. You need to create a relationship between the Weekly_Returns table and the Date table to meet the reporting requirements of the regional managers. What should you do?

Options

• AIn the Weekly_Returns table, create a new calculated column named date-id in a format of
• BAdd the Weekly_Returns data to the Sales table by using related DAX functions.
• CCreate a new table based on the Date table where date-id is unique, and then create a many-to-

Explanation

The Date table uses 'dateid' in yyyymmdd format as its primary key. The Weekly_Returns table uses a 'weekid' column in yyyyww format, which cannot directly join to the Date table's dateid. To create a valid relationship, you need to create a calculated column in Weekly_Returns that converts the week value into a yyyymmdd date format (e.g., the first day of that week), enabling a proper many-to-one join to the Date table. Options B and C are either semantically incorrect (adding weekly data to a Sales table via DAX doesn't resolve the schema mismatch) or overly complex compared to a simple calculated column.

No community discussion yet for this question.