exam questions

Exam PL-300 All Questions

View all questions & answers for the PL-300 exam

Exam PL-300 topic 1 question 7 discussion

Actual exam question from Microsoft's PL-300
Question #: 7
Topic #: 1
[All PL-300 Questions]

You are building a Power BI report that uses data from an Azure SQL database named erp1.
You import the following tables.

You need to perform the following analyses:
✑ Orders sold over time that include a measure of the total order value
Orders by attributes of products sold

The solution must minimize update times when interacting with visuals in the report.
What should you do first?

  • A. From Power Query, merge the Order Line Items query and the Products query.
  • B. Create a calculated column that adds a list of product categories to the Orders table by using a DAX function.
  • C. Calculate the count of orders per product by using a DAX function.
  • D. From Power Query, merge the Orders query and the Order Line Items query.
Show Suggested Answer Hide Answer
Suggested Answer: D 🗳️

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
PinkZebra
Highly Voted 2 years, 5 months ago
Selected Answer: D
I'm very sure it's D. It's the Header/Detail Schema, and the most optimal way is to flatten the header into the detail table.
upvoted 96 times
tranquanghuy2111
1 year, 5 months ago
Totally agree, in Star Schema, we should only have one FACT table of ONE object (here is order). So, in this example, we should combine Order and Order Detail into one FACT table.
upvoted 12 times
...
NevilleV
2 years, 5 months ago
D. doesn't have a common field. The answer has to be A
upvoted 9 times
PinkZebra
2 years, 5 months ago
I agree that it's not clearly stated in the question that Order and Order Line tables have common field (for example: order ID) If there is no common fields, there is no way to implement the requirements (calculating order value from Order line).
upvoted 10 times
...
ApacheKafka
1 year, 7 months ago
There is no way D doesnt have a common field. There wouldn't be an order line if there was no Order ID in it. so just because it is not stated doesnt mean it dont exist.
upvoted 10 times
...
...
shako
1 year, 7 months ago
I was first going with A but from the explanations I got from his source and re-reading the question between the lines, it is obvious that the answer is D.
upvoted 3 times
...
Joaomagafer
1 year ago
My option here was A. Nothing in the question makes me think I need any High level Info on Orders (i.e. Orders table). In the 'Order Line Item' I have everything I need to calculate 'Total Order Value' (i.e. Quantity * Price) plus the Product ID, which I'd use to get the Product Attributes required. In my opinion and based on the requirements, I don't think we even need/should to load 'Orders' table, as this would not be a requirement for the task in hand, thus we would be loading extra info that in not needed.
upvoted 2 times
...
...
David_Zed
Highly Voted 2 years, 6 months ago
Selected Answer: A
Should be A, because we need to get " Orders sold over time that include a measure of the total order value Orders by attributes of products sold" Order line detail for quantities ordered, and product for product's attribute
upvoted 40 times
WZ17
2 years, 3 months ago
I think you're forgetting about the "over time" part of the objective. You cannot show a distribution of sales over time without having a date column which does not seem to be present in Products or Order Line Items.
upvoted 16 times
Legato
2 years, 3 months ago
Exactly
upvoted 4 times
...
Hoeishetmogelijk
1 year, 8 months ago
The date column is also not specified in the Orders, so this argument doesn't make sense.
upvoted 1 times
Maniula
1 year, 7 months ago
What do you mean? High-level info about orders includes date of the order.
upvoted 9 times
...
...
...
golden_retriever
2 years, 3 months ago
Price is also an attribute to the product, which is present in Order line detail. The key word here is a product sold. The sold items are present only in the Order line detail. So A is INCORRECT
upvoted 19 times
...
Shalaleh
1 year, 10 months ago
it is not good idea to merge dim table with fact table!
upvoted 6 times
Hoeishetmogelijk
1 year, 8 months ago
It is not a good idea, but in this case it is the only way to aggregate the order value per product attributes.
upvoted 1 times
...
...
...
binny89
Most Recent 5 days, 20 hours ago
Selected Answer: A
The order table's description says "contain high level information about order". Nothing else. And most importantly, the requirement is 1) order quantity, 2) order value and 3) order by product attributes - nothing else valuable can be acquired from the order table? Therefore if the requirement is to minimize update time of visual, don't bother connecting order and order line item table. Answer should be A
upvoted 1 times
...
MANANDAVEY
2 months ago
Selected Answer: D
Answer is D. Tried and Tested.
upvoted 2 times
...
Pey1nkh
2 months ago
Selected Answer: A
Why not D: Merging these two tables would help calculate the total order value but does not associate product attributes (e.g., categories) with orders. Without merging Order Line Items and Products, you cannot analyze orders by product attributes effectively.
upvoted 1 times
...
esrath
2 months, 1 week ago
Selected Answer: D
Note: We must suggest the action we should perform FIRST. Of course, we need the Products table for the product attributes but first, we need to merge the Orders and Order Line Items to get the time-based information from the Orders table. We need that for the "Orders sold over time". The Order Line Items table does not have time-based information(Date). As per the question, it only has those 3 columns. After using number D as the first step, we can merge the Product table, write DAX for total order value, etc...
upvoted 2 times
...
AlexBear
2 months, 3 weeks ago
Selected Answer: A
I choose A. The Products table contains product attributes (e.g., category, brand), but it cannot directly connect to the Orders table since there’s no shared key. The Order Line Items table acts as a bridge between the Products table (via Product ID) and the Orders table (via Order ID). By merging Products with Order Line Items, the resulting table includes both product attributes and order-level details, enabling comprehensive analysis. For analysis 1 (orders sold over time with total order value): Use the merged table to calculate total order value (Quantity × Price) for each order and aggregate by the order date from the Orders table. For analysis 2 (orders by product attributes): Filter and group the merged table by product attributes (e.g., category or brand) to analyse sales performance for specific product groups.
upvoted 1 times
...
Rahultakle
2 months, 3 weeks ago
Selected Answer: D
D is right, Merging the Orders query with the Order Line Items query in Power Query creates a more efficient data model. This reduces the number of relationships and joins that need to be processed during report interactions, leading to faster update times. With the merged data, calculations such as total order value and orders by product attributes become simpler and more efficient. This reduces the need for complex DAX calculations that can slow down report performance
upvoted 2 times
...
Madhu1551546
3 months ago
The Order Line Items table contains only the following columns: Product ID Quantity Price Details It does not include a date column or other high-level order information. The Orders table, on the other hand, likely contains essential information such as: Order Date (for time-based analysis) Order ID (to link with Order Line Items) Customer Details (if needed) so Answer is D
upvoted 1 times
...
DexTorao
3 months, 3 weeks ago
D - From Power Query, merge the Orders query and the Order Line Items query
upvoted 1 times
...
NLeeXTung
5 months, 1 week ago
Selected Answer: D
Hello everyone, to make it clear we must to know: --- PBI will do the best aggregation base on Star Schema model, we now have 1 Fact table (Order Line Items) and 2 Dim tables (Products, Orders). Orders has common field with Products (ProductID), and pretty sure time series field (OrderDate); Orders Line Items has Price and Quanity. --- We need summarize some values like "price" and "quantity" over-time by attributes product. But we only have common field in Dim table (Orders) so we need to merge Dim (Orders) and Fact (Order Line Items) to new single Fact table to design the right Star Schema model. => So that D is correct
upvoted 2 times
...
Ganga425
5 months, 3 weeks ago
Might be option A. How about the orders by attribute without accessing the Product datasource ?
upvoted 1 times
...
rcaliandro
7 months ago
Selected Answer: D
We need first, in such way to join orders and order line query. So the right answer is: D. From Power Query, merge the Orders query and the Order Line Items query.
upvoted 1 times
...
HenryBiz
9 months ago
Selected Answer: D
D. Since Order and Order Lines tables are parts of the fact table, so combine them first and make the combination the centre of the star schema, then join the DIM table Product.
upvoted 3 times
...
SureshReddyMoole
9 months, 3 weeks ago
D. From Power Query, merge the Orders query and the Order Line Items query. By merging these queries, you create a single table that contains all the necessary information about orders and their line items. This simplifies the data model and reduces the overhead of handling multiple tables and relationships, leading to more efficient interactions with visuals in your report.
upvoted 3 times
...
jsav1
10 months, 1 week ago
Selected Answer: D
D - Consolidate the order and order line items query first - you will need information from both tables
upvoted 2 times
...
tarekff
11 months, 2 weeks ago
The main advantage of D over A is that Merging Orders with Order Line Items creates a fact table in a star schema, instead of having two fact table.
upvoted 1 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