Question bank
Pick an answer to see if you're right — with an explanation.
All topicsPythonSQL / MySQLData ScienceNumPyPandasMatplotlibMachine LearningDeep LearningArtificial IntelligenceLarge Language ModelsDjangoAPIsGit & GitHubPower BIExcelStatistics
Power BIEasy
A depot file has one column per month (Apr, May, Jun...). Which Power Query transform turns them into `Month` and `Sales` columns?
aPivot Columns
bUnpivot Other Columns
cMerge Queries
dTranspose
Explanation: Unpivot collapses many value columns into an attribute/value pair; Unpivot Other Columns keeps working when a new month arrives.
Power BIEasy
You have three depot files with identical columns and want a single table containing all their rows. Which operation do you use?
aMerge Queries
bGroup By
cAppend Queries
dUnpivot Columns
Explanation: Append is the UNION ALL of Power Query — it stacks rows; Merge adds columns via a join.
Power BIEasy
In a star schema, `Product` (one side) is related to `Sales` (many side) with Single cross-filter direction. Which way do filters flow?
aFrom Product to Sales
bFrom Sales to Product
cIn both directions
dFilters do not propagate across relationships
Explanation: With single direction, the one side filters the many side; selecting a brand filters sales, but not the reverse.
Power BIEasy
Which object is computed row by row and physically stored in the model at refresh time?
aA measure
bA slicer
cA report-level filter
dA calculated column
Explanation: Calculated columns are materialised into the table at refresh; measures are evaluated per visual cell at query time.
Power BIMedium
What does this measure return in a matrix sliced by `Product[Brand]` and `Store[Region]`?
Brand Share % =
DIVIDE (
[Total Sales],
CALCULATE ( [Total Sales], REMOVEFILTERS ( Product[Brand] ) )
)
aThe brand's share of all sales ever recorded, ignoring region
bAlways 100% because numerator and denominator match
cThe brand's share of sales within the current region and other filters
dAn error, because REMOVEFILTERS cannot be used inside DIVIDE
Explanation: REMOVEFILTERS clears only the Brand filter; the region and any other filters still apply to both numerator and denominator.
Power BIMedium
What is the purpose of the `"31/3"` argument here?
Sales FYTD =
CALCULATE ( [Total Sales], DATESYTD ( 'Date'[Date], "31/3" ) )
aIt filters the result to 31 March only
bIt sets the fiscal year end to 31 March so the running total restarts on 1 April
cIt formats the output as a date
dIt limits the calculation to the year 2031
Explanation: DATESYTD takes an optional year-end date; "31/3" gives the Indian April-March fiscal year.
Power BIMedium
A scheduled refresh of an Import model sourced from an on-premises SQL Server fails with a gateway error. What fixes it?
aInstall and configure the on-premises data gateway in standard mode and bind the data source to the model
bRepublish the .pbix from Desktop
cSwitch the workspace licence from Pro to Premium
dGive report users Build permission on the semantic model
Explanation: Cloud-to-on-premises refresh requires a gateway; republishing or changing licences does not create that connection.
Power BIMedium
Why does `RELATED` work in this calculated column on the `Sales` table?
Line MRP Value = Sales[Qty] * RELATED ( Product[MRP] )
aBecause RELATED works in any direction across any relationship
bBecause calculated columns always ignore relationships
cBecause Sales is the one side of the relationship
dBecause Sales is the many side, so each row has exactly one matching Product row
Explanation: RELATED goes from the many side to the one side; from the one side you would need RELATEDTABLE with an aggregator.
Power BIHard
An RLS role filters `Store[Region] = "Vidarbha"`, and a user assigned to that role is also a Member of the workspace. What do they see?
aOnly Vidarbha rows, because RLS always wins
bNo data at all, because the two permissions conflict
cAll rows — RLS is not applied to workspace Admins, Members or Contributors
dOnly Vidarbha rows in reports but all rows in the model
Explanation: RLS applies to Viewers and app consumers; users with edit rights on the workspace bypass it, so restricted users must be Viewers.
Power BIHard
On 12 September, `Total Sales` covers 12 days but `SAMEPERIODLASTYEAR` returns all 30 days of last September, making YoY look awful. What is the correct fix?
aRestrict the prior-year measure to the same number of elapsed days, e.g. by adding a filter up to EDATE(MAX(Sales[InvoiceDate]), -12)
bReplace SAMEPERIODLASTYEAR with PREVIOUSYEAR
cSet the date table's end date to today so future days disappear
dChange the relationship to bi-directional so filters flow back to the date table
Explanation: Like-for-like comparison means truncating last year's window to the same elapsed period; the other options do not align the two periods.