WIPRO Data Analyst Interview Scenario Based
Power BI & SQL Q&A (2025 Edition)
1 Scenario
What they asked me:
“Suppose you have a Power BI dataset with 10 million rows of sales data that refreshes daily
from SQL Server. The refresh is taking hours. How will you optimize it without reducing
data size?”
What I said:
I would enable Incremental Refresh in Power BI. It allows refreshing only new or modified
data rather than the entire dataset.
Steps:
Create RangeStart and RangeEnd parameters in Power Query.
Filter the table using these parameters.
Configure incremental refresh in Power BI Service (e.g., store 5 years of data, refresh
last 7 days).
Publish and schedule refresh.
Tips:
Use Incremental Refresh for any table with historical data that doesn’t change. It drastically
reduces refresh time and load.
2️ Scenario:
What they asked me:
“Your Power BI dashboard is loading very slowly after adding more visuals. How will you
troubleshoot and optimize it?”
What I said:
I used the Performance Analyzer in Power BI Desktop to identify which visuals or DAX
queries were slow.
Then optimized by:
Removing unused columns and tables (simplify model).
Converting calculated columns to measures.
Using star schema instead of snowflake.
Reducing visuals per page.
Applying Aggregations for pre-calculated data.
Tips:
Always start with the Performance Analyzer → DAX Optimization → Model Design →
Visual Cleanup.
3️ Scenario:
What they asked me:
“You have a Sales table where each manager should see only their region’s data. How would
you implement this in Power BI?”
What I said:
I’d create Dynamic Row-Level Security (RLS).
Steps:
In Power BI Desktop → Manage Roles → Create Role.
DAX filter:
[ManagerEmail] = USERPRINCIPALNAME()
Test using View as Role.
Publish → In Power BI Service → Assign users/groups to roles.
Tips:
Dynamic RLS is better than static — use USERNAME() or USERPRINCIPALNAME() for
flexibility.
4️ Scenario:
What they asked me:
“You have 100 Excel/CSV files in a folder (monthly customer feedback reports). How would
you combine them into one Power BI dataset?”
What I said:
I’d use the Folder Connector in Power Query:
1. Go to Get Data → Folder.
2. Select folder path → Combine & Transform.
3. Power BI uses one sample file to define schema.
4. Clean data (remove extra rows, rename columns).
5. Load combined data into Power BI.
Tips:
Ensure all files have the same structure. Add a “File Name” column to track region or month
easily.
5️ Scenario:
What they asked me:
“If you have to calculate Profit = Sales – Cost, would you use a calculated column or a
measure? Why?”
What I said:
I’d use a Measure because it’s computed on the fly and doesn’t consume memory.
Example:
Profit = SUM(Sales[Amount]) - SUM(Sales[Cost])
If the result was needed per row (like a category flag), then I’d use a calculated column.
Tips:
Use Measures for aggregations → better performance.
Use Columns only when you need row-wise logic or filtering.
6️ Scenario:
What they asked me:
“Your model has duplicate Customer IDs in both ‘Sales’ and ‘Feedback’ tables. How do you
handle it?”
What I said:
I’d create a Bridge Table containing unique CustomerID values and link both tables to it (1-
to-many on each side).
This removes ambiguity and allows proper filtering across both tables.
Tips:
Avoid direct many-to-many relationships — use bridge tables or DAX TREATAS() when
necessary.
7️ Scenario:
What they asked me:
“Your Power BI report needs to reflect the latest Excel data stored on OneDrive
automatically. How would you set it up?”
What I said:
Upload Excel to OneDrive for Business.
In Power BI Service → Get Data → OneDrive – Business.
Choose “Import” or “Connect” (live connection).
Power BI auto-syncs changes every hour.
Tips:
This is perfect for shared Excel reports. No need to manually refresh — changes flow
automatically.
8️ SQL Scenario:
What they asked me:
“Write a SQL query to calculate cumulative salary per department for employees who joined
in the last 30 days.”
What I said:
SELECT department, emp_name, joining_date, salary,
SUM(salary) OVER (PARTITION BY department ORDER BY joining_date) AS
cumulative_salary
FROM employees
WHERE joining_date >= CURRENT_DATE - INTERVAL 30 DAY
ORDER BY department, joining_date;
It uses window functions to calculate running totals per department.
Tips:
Always use OVER (PARTITION BY … ORDER BY …) for cumulative or ranking calculations.
9️ Scenario:
What they asked me:
“How do you find the second most recent order date in SQL?”
What I said:
SELECT MAX(orderdate) AS second_most_recent
FROM Orders
WHERE orderdate < (SELECT MAX(orderdate) FROM Orders);
This gets the maximum date that’s less than the latest order date.
Tips:
This approach works in SQL Server, Oracle, PostgreSQL — no need for window functions.
10 Bonus Scenario:
What they asked me:
“Your report uses on-premises SQL data, but users access it from Power BI Service. How
will you connect it securely?”
What I said:
Install and configure Power BI Gateway (Standard Mode).
Register it using my Power BI account.
Add data sources (server, DB, credentials).
Map the dataset to the gateway in Power BI Service.
Schedule refresh.
Tips:
Use Standard Mode for enterprise — allows multiple datasets, refresh schedules, and shared
connections.