Easy Business Analytics Interview Questions

Waterfall runs fixed phases one after another with requirements frozen early. Agile delivers in short sprints with continuous feedback, so requirements can change. In Agile, BAs maintain the backlog and user stories.

Excel suits small to medium data and quick ad-hoc work; SQL queries large databases directly and repeatably.

Low-fidelity layouts of screens that help stakeholders visualise and agree on requirements before development starts.

A BRD states what the business needs and why. An FRD details how the system should behave to meet those needs (functional specifications).

A column or set of columns that uniquely identifies each row in a table and cannot contain NULL.

Prepare clean data, build PivotTables and PivotCharts, add KPI cards and slicers, and arrange everything on one sheet with a clear layout.

Anyone affected by or influencing the project: sponsors, product owners, end users, developers, testers, operations and customers.

A chart shows one view of data; a dashboard combines several charts and KPIs on one page for monitoring.

A language for querying databases. BAs use it to pull data themselves, validate numbers, check reports and answer questions without waiting for engineers.

Agile delivers value in small increments with feedback. Scrum organises work in sprints with planning, daily stand-ups, review and retrospective, led by a Scrum Master and Product Owner.

Functional requirements describe what the system does (login, reports); non-functional ones describe how well it does it (speed, security, availability, usability).

VLOOKUP or XLOOKUP, INDEX-MATCH, SUMIFS, COUNTIFS, IF, text functions, PivotTables and charts.

A measurable value showing progress to a goal, such as conversion rate, average order value, cart abandonment rate and customer retention.

XLOOKUP can look left or right, uses exact match by default, returns a custom value if nothing is found and doesn't break when columns move. VLOOKUP only looks right and needs a column number.

Uncontrolled growth of requirements. Control it with a clear scope statement, change control process, impact analysis and sponsor approval for additions.

A BA bridges business and technology: gathers requirements, analyses data and processes, documents BRD/FRD and makes sure the final solution actually solves the business problem.

Every KPI is a metric, but a KPI is tied directly to a strategic goal (e.g. monthly churn). A metric can be any measurement (e.g. page views).

A UML diagram showing actors and the actions (use cases) they perform with the system, giving a quick view of scope.

As a customer, I want to reset my password by email so that I can get back into my account. Acceptance criteria: • Reset link expires in 15 minutes • Password rules are shown while typing • A success message appears after reset

INNER returns only matching rows; LEFT returns all rows from the left table and NULLs where there is no match.

Clarify the scope, break the problem into logical parts, state assumptions with round numbers, compute step by step and sanity-check the answer.

Compare the current state (as-is) with the desired state (to-be), list the gaps in process, people or technology, and plan actions to close them.

Strengths and Weaknesses are internal; Opportunities and Threats are external. Example: S = strong faculty, W = low brand awareness, O = AI upskilling demand, T = free online content.

Revenue is total money from sales; profit is what remains after subtracting all costs and expenses.

The smallest version of a product with enough features to deliver value and gather real user feedback before investing more.

Functions that summarise rows into a value, such as COUNT, SUM, AVG, MIN and MAX.

Power BI Desktop is the free Windows app where you connect to data, model it, write DAX and design reports. Power BI Service is the cloud portal where you publish reports, schedule refresh, build dashboards, set permissions and share with users. Power BI Mobile is the phone app for viewing reports on the go. A typical flow is build in Desktop, publish to a Service workspace, and consume on web or mobile.

A calculated column is computed row by row at refresh time and stored in the model, so it uses memory and can be used in slicers, rows and relationships. A measure is computed at query time based on the current filters, so it is not stored and responds to slicers. Use a column for attributes such as an age band, and a measure for aggregations such as Total Sales or Margin %.

Power Query is the data preparation engine inside Power BI and Excel. It connects to sources like Excel, CSV, SQL databases and web APIs, then lets you clean and shape data with recorded steps: remove columns, change types, split, merge, unpivot, append and group. Each step is written in the M language and replays on every refresh, so a monthly cleanup job becomes repeatable instead of manual.

Dimensions are qualitative fields such as Region, Category or Customer Name; placing them on a shelf creates headers and splits the view into groups. Measures are numeric fields such as Sales or Quantity that Tableau aggregates, usually with SUM or AVG. Tableau also marks fields as discrete (blue pills, headers) or continuous (green pills, axes). A date can act as either, which changes whether you get separate bars or a continuous trend line.

For a trend over time use a line chart. For part-to-whole use a stacked bar or a 100 percent bar; a pie or donut only works with two to four slices. For comparing categories use a sorted horizontal bar chart. For distribution use a histogram or box plot. For correlation between two measures use a scatter plot. Choosing by the question being answered, not by looks, keeps dashboards readable.

Promote the first row to headers and remove blank or total rows. Set correct data types for dates and amounts, and use locale settings for Indian date formats. Trim and clean text columns, replace errors and nulls, split combined fields like 'City-State', and unpivot month columns into rows. Remove duplicates on the order ID, then merge with the product master. Rename steps clearly so others can follow the logic.

Save the .pbix and click Publish, choosing the team workspace. In the Service, set data source credentials and, for on-premises data, configure the gateway. Schedule refresh. Then share by giving workspace access to editors, or package it as an app for viewers, and apply row-level security roles if needed. Finally, check it on web and mobile and send the link with a short note on what each page answers.

A relative reference like A1 shifts when the formula is copied. An absolute reference like $A$1 stays fixed, useful for a tax rate or target cell. A mixed reference fixes only the column ($A1) or only the row (A$1), which is handy in multiplication grids or when copying a formula across months and products. Press F4 to cycle through the four options while editing a formula.

An Excel Table turns a range into a named, structured object. It expands automatically when rows are added, so formulas, charts, PivotTables and Power Query sources pick up new data without range edits. It supports structured references like =SUM(Sales[Amount]), calculated columns that fill down automatically, built-in filters, banded formatting and a total row. Tables make reports far less error-prone than fixed ranges like A2:F5000.

Conditional formatting changes a cell's look based on rules or formulas. In reports you can highlight targets missed in red, use data bars for sales size, colour scales for a region heatmap, icon sets for trend direction, or a formula rule like =$E2<$F2 to colour an entire row. Use it sparingly and with a legend so the eye goes only to the exceptions that need action.

Usually the values only look the same. Common causes are trailing or leading spaces, numbers stored as text in one sheet and as numbers in the other, non-breaking spaces from web exports, or different spellings. Check with =LEN() and =ISNUMBER(), clean with TRIM, CLEAN or VALUE, and confirm the lookup range covers all rows and uses exact match. Wrap the final formula in IFNA to label true misses.

Both stack the results of two queries with the same number and type of columns. UNION removes duplicate rows, which needs a sort or hash step and is slower. UNION ALL keeps every row and is faster. Use UNION ALL when combining data such as online and store sales where duplicates are genuine or impossible, and UNION only when you specifically need a distinct list, such as unique customer IDs from two sources.

A foreign key is a column in one table that refers to the primary key of another, such as orders.customer_id pointing to customers.customer_id. Referential integrity means every foreign key value must exist in the parent table, so you cannot have an order for a customer who does not exist. The database enforces it on insert, update and delete, which keeps joins reliable for reporting.

An index is a sorted lookup structure on one or more columns that lets the database find rows without scanning the whole table, much like a book index. It speeds up WHERE filters, joins and ORDER BY on those columns. It hurts when there are too many indexes, because every insert and update must maintain them, and it may not help on low-selectivity columns or when functions are applied to the indexed column.

Gross margin is revenue minus cost of goods sold, divided by revenue, and shows how profitable the product itself is. Net margin is net profit after all expenses, including salaries, rent, marketing, interest and tax, divided by revenue. A company can have a healthy 60 percent gross margin but a negative net margin if it overspends on marketing or overheads, which tells you where to look for fixes.

Churn rate is the percentage of customers who leave in a period: customers lost divided by customers at the start. Retention rate is the percentage who stay, roughly 100 minus churn for the same cohort. If you start a month with 1,000 subscribers and 50 cancel, churn is 5 percent and retention 95 percent. Count new customers separately, otherwise growth hides churn. Revenue churn can differ from customer churn.

ARPU, Average Revenue Per User, is total revenue in a period divided by the average number of users in that period. If a telecom-style app earns 50 lakh in a month from 25,000 average users, ARPU is 200 rupees. It is tracked to see whether growth comes from more users or more value per user. ARPPU, revenue per paying user, is used when only some users pay.

Average Order Value is total revenue divided by number of orders. If an online store earns 9 lakh from 1,500 orders, AOV is 600 rupees. Businesses increase it with bundles, cross-sell and upsell recommendations, free delivery above a threshold, volume discounts and premium options. Watch margin and conversion while doing so, because a high free-delivery threshold can raise AOV but reduce the number of orders.

A vanity metric looks impressive but does not guide decisions, such as total app downloads, page views or social followers that only ever go up. An actionable metric links clearly to a decision and behaviour, such as Day-7 retention, conversion rate by channel or revenue per active user. A good test: if the number changes, do you know what to do differently? If not, it is probably vanity.

NPS asks customers how likely they are to recommend you on a 0 to 10 scale. Scores of 9 to 10 are promoters, 7 to 8 passives and 0 to 6 detractors. NPS equals percent promoters minus percent detractors, ranging from minus 100 to plus 100. Limitations: it is one question, sensitive to survey timing and sample bias, and does not explain why. Pair it with open-text reasons and behavioural metrics like retention.

Churn rate uses customers at the start: 400 divided by 8,000 gives 5 percent. Ending customers are 8,000 plus 1,200 minus 400, which is 8,800. Net growth is 800 divided by 8,000, or 10 percent. Do not divide churned customers by the ending count, since new joiners who have not had a chance to churn would understate the churn rate.

A power-interest grid maps stakeholders by how much influence they have over the project and how interested or affected they are. High power and high interest: manage closely with regular involvement. High power, low interest: keep satisfied with concise updates. Low power, high interest: keep informed, for example end users. Low power, low interest: monitor. It helps a BA decide who to consult, how often and in what format.

Executives want outcomes, impact, risk and decisions needed, in a one-page summary or a few slides with clear numbers. Technical teams need precise details: data fields, business rules, edge cases, acceptance criteria and dependencies. Operations users need process steps and what changes in their daily work. Same facts, different depth and vocabulary. Ask each group how they prefer to receive updates and adjust.

Data storytelling combines data, visuals and narrative so the audience understands what happened, why, and what to do. A good story has context, a clear insight, supporting evidence in one or two simple charts and a recommendation. Accurate numbers alone rarely change decisions; people act when they see the implication. Remove chart clutter, highlight the key point with colour and use titles that state the conclusion.

Skip the formulas and talk about what drives the forecast, such as seasonality, past trend and pipeline, in plain words. Show one chart of actuals versus forecast with a range rather than a single number, and explain that the range reflects uncertainty. Translate it into their terms: what it means for their targets and stock. Invite questions and share an example of where it would be wrong.

Use a short, fixed format. Start with an overall status of green, amber or red and one line explaining it. Then list what was completed this week, what is planned next week, key risks and issues with owners, and decisions needed from stakeholders with dates. Add a link to the detailed tracker. Keep it under one screen, and highlight anything that changed since last week.

Keep it to about 90 seconds in a present, past, future flow. For example: I am a commerce graduate working as an analyst intern, where I build Excel and Power BI reports and write SQL queries for the sales team. Earlier, my college project analysed customer churn for a local gym and recommended changes they adopted. I want to grow as a business analyst because I enjoy turning business problems into clear requirements and data-driven decisions.

Link your answer to real experience. For example: during my internship I noticed reports were rebuilt manually every week, so I mapped the process and automated it with Power Query, saving the team a day each week. I enjoyed understanding the problem, talking to users and seeing the result used. A BA role combines that problem solving, communication and data work, which is where my strengths are, and I want to build deeper domain knowledge.

Situation: in my final-year project, our client moved the presentation forward by a week. Task: finish the analysis and dashboard in four days instead of eleven. Action: I listed the must-have outputs, split work across the team, cut two nice-to-have charts and checked numbers every evening. Result: we presented on time, the client used our recommendations, and I learned to prioritise ruthlessly and confirm what is truly essential.

Situation: my manager said my first analysis deck was hard to follow. Task: improve it before it went to the client. Action: I asked for specific examples, learned that I had put twenty charts before any conclusion, and restructured it with the recommendation first, three supporting charts and an appendix. Result: the client meeting went well, and I now ask a colleague to review my storyline before every major presentation.

Show ambition that fits the role. For example: in five years I see myself as a senior business analyst who owns a business domain, such as payments or supply chain, leads requirement and analytics work for major initiatives and mentors juniors. To get there I am building strong SQL and Power BI skills, learning the domain deeply and taking on more stakeholder-facing work. I would like to grow that path within this organisation.

An epic is a large body of work that delivers a major business goal and spans several sprints, such as 'Online loan application'. It is broken into features or capabilities, such as 'Document upload'. Each feature is split into user stories small enough to finish in one sprint, such as 'As an applicant, I want to upload my PAN card photo so that I do not need to visit a branch'.

Backlog refinement, also called grooming, is a regular session where the team reviews upcoming backlog items to clarify, split, estimate and order them, so the next sprints have ready work. The BA prepares the stories in advance with business context, acceptance criteria, rules and examples, answers questions from developers and testers, and captures follow-ups. It is usually a short weekly session, not a sprint ceremony.

A sprint review is held at the end of the sprint with stakeholders to demonstrate completed work, gather feedback and adjust the backlog; it is about the product. A sprint retrospective is an internal team meeting afterwards to discuss what went well, what did not and what to improve in the way of working; it is about the process. The BA often helps demo stories in the review.

Scrum works in fixed sprints with defined roles such as product owner and scrum master, planned sprint goals and ceremonies like planning, review and retrospective. Kanban has no sprints: work flows continuously across a board, and work-in-progress limits on each column prevent overload. Kanban measures cycle time and throughput. Scrum suits product development with planned increments; Kanban suits support, operations and reporting requests that arrive unpredictably.

Product analytics studies how users behave inside a digital product, using event data such as sign-ups, clicks, feature use and purchases, to improve activation, engagement and retention. Business reporting usually summarises outcomes like revenue, cost and orders by period. Product analytics answers questions like where users drop off, which features retained users adopt, and whether a change worked, often through funnels, cohorts and experiments.

DAU, WAU and MAU count unique users active in a day, week and month, where 'active' must be clearly defined, such as completing a core action. The stickiness ratio is DAU divided by MAU and shows how often monthly users return. A ratio of 0.5 means the average monthly user is active about 15 days a month. Daily-use products like messaging aim high, while a travel app naturally has low stickiness.

Cohort analysis groups users by a shared starting point, usually their sign-up or first purchase month, and tracks their behaviour over time, such as the percentage still active in month 1, 2 and 3. It separates the effect of growth from the effect of retention, so you can see whether newer cohorts retain better after a product change. It is typically shown as a triangle table or retention curves.

Funnel analysis measures how many users move through a sequence of steps towards a goal, such as visit, product view, add to cart, checkout and payment, and the conversion and drop-off at each step. It shows where the biggest leak is so the team can focus fixes there. Break funnels down by device, channel and new versus returning users, and define a time window for completing the steps.

A/B testing is a controlled experiment where users are randomly split into a control group that sees the current version and a treatment group that sees a change, such as a new checkout button. You compare a pre-decided primary metric, like conversion rate, between groups. Because assignment is random, a significant difference can be attributed to the change rather than to seasonality, marketing or user mix.

Feature adoption rate is the share of eligible active users who used a feature in a period. For example, if 4,000 of 20,000 monthly active users used saved searches, adoption is 20 percent. Measure it against eligible users only, track first use and repeat use separately, and compare retention of adopters versus non-adopters. High first use with low repeat use often means the feature is discoverable but not valuable.

Control conversion is 400 divided by 10,000, which is 4.0 percent. Variant conversion is 460 divided by 10,000, which is 4.6 percent. The absolute lift is 0.6 percentage points and the relative lift is 0.6 divided by 4.0, which is 15 percent. Before calling it a win, run a two-proportion significance test and check the confidence interval and guardrail metrics.

MECE means Mutually Exclusive and Collectively Exhaustive. When you break a problem into parts, the parts should not overlap and together should cover every possibility. For example, profit splits into revenue and cost, and revenue into price times volume. A breakdown of customers into 'young' and 'students' is not MECE because they overlap. MECE structures prevent double counting and missed causes, which is what interviewers check.

TAM, Total Addressable Market, is total demand for the product if every possible customer bought it. SAM, Serviceable Available Market, is the part you can reach with your model, geography and channels. SOM, Serviceable Obtainable Market, is the share you can realistically capture in the next few years given competition. For an online tutoring startup in India, TAM is all school students, SAM those online in target cities, SOM a small share of that.

The BCG matrix classifies business units or products by market growth rate and relative market share. Stars have high share in high-growth markets and need investment. Cash cows have high share in slow markets and fund the rest. Question marks have low share in fast markets and need a decision to invest or exit. Dogs have low share in slow markets and are candidates to divest. It guides portfolio resource allocation.

They assess how you think, not just the final answer. Key areas are clarifying the problem before solving, building a clear and MECE structure, handling numbers accurately with sanity checks, using business sense to prioritise, adapting to new information, and ending with a crisp recommendation with risks and next steps. Thinking aloud and communicating clearly matter as much as getting the right number.

PESTEL scans the external environment across Political, Economic, Social, Technological, Environmental and Legal factors. For an electric vehicle maker in India it would cover subsidies and policy, fuel prices and interest rates, consumer attitudes, battery technology, emission targets and safety regulations. It is useful in market entry and strategy cases to spot opportunities and risks beyond the company's control, and pairs well with SWOT.

BPMN (Business Process Model and Notation) is a standard graphical notation, maintained by the OMG, for drawing business processes. Business analysts use it because business users, developers and process owners can all read the same diagram. It shows who does what, in which order, with which decisions and messages. A BPMN 2.0 model can also be executed by workflow engines, so the same diagram can move from analysis to automation with less rework.

BPMN groups its shapes into four categories. Flow objects are events (circles), activities (rounded rectangles) and gateways (diamonds). Connecting objects are sequence flows, message flows and associations. Swimlanes are pools and lanes that show participants and roles. Artifacts are data objects, groups and text annotations that add context without changing the flow. Knowing these four groups lets you read almost any BPMN diagram quickly.

A pool represents a separate participant in a process, such as the customer, your company or an external bank. A lane is a subdivision inside a pool, usually a department, role or system, such as Sales, Finance and Warehouse within your company. Sequence flows can cross lanes within one pool, but communication between two pools must be shown with message flows, because separate participants do not share one controlled flow.

Events are circles that show something happening. A start event (thin border) triggers the process, such as a form submitted or a timer firing on the first of the month. An intermediate event (double border) happens during the process, such as waiting for a payment message or a 48-hour timer. An end event (thick border) marks where a path finishes and can carry a result such as a message, an error or termination of all paths.

A task is an atomic unit of work that you do not break down further in the diagram, such as Verify PAN details. A sub-process is a compound activity that contains its own flow of tasks, events and gateways, shown with a small plus sign when collapsed. Sub-processes keep high-level diagrams readable: the main map shows Credit Check as one box, and a separate detailed view explains its internal steps.

A simple flowchart shows the sequence of steps and decisions but not who performs them. A swimlane diagram divides the chart into horizontal or vertical lanes, one per role, team or system, and places each step in the lane of its owner. This makes handoffs visible, because every arrow crossing a lane boundary is a handoff where delays, errors and unclear ownership often occur. BPMN lanes are a standardised form of swimlanes.

A process describes what happens end to end to achieve an outcome, across roles, such as customer onboarding. A procedure describes how one part of that process is carried out and who is responsible, such as the KYC verification procedure. A work instruction is the most detailed, step-by-step guide for a single task, often with screenshots, such as how to upload a document in the CRM. BAs usually model processes and reference the other two.

DELETE removes selected rows using a WHERE clause, logs each row and can usually be rolled back inside a transaction. TRUNCATE removes all rows quickly by deallocating data pages, keeps the table structure and normally resets identity counters; rollback behaviour depends on the database. DROP removes the whole table, including its structure, indexes and permissions. Analysts mostly use DELETE carefully on staging tables and should rarely need TRUNCATE or DROP on production data.

Use Data Validation with a List rule. Keep the allowed regions in a separate sheet as an Excel Table, name it, and set the validation source to that range so the dropdown grows when you add a region. Turn on an error alert so free text is rejected. Then clean existing entries once with Find and Replace or a mapping lookup. For stronger control, protect the sheet and unlock only the input cells, so the list cannot be edited by mistake.

The PivotTable source is probably a fixed range such as A1:F500, so rows added below 500 are outside it. The fix is to convert the data to an Excel Table with Ctrl+T and change the pivot's data source to the table name, so it expands automatically. Also check for blank header cells, filters on the pivot hiding new items, and whether the new rows are actually text values in a numeric column, which can change grouping.

Correlation means two metrics move together; causation means one actually changes the other. Users who use the wishlist feature may retain better, but they may simply be more engaged users already. Acting on correlation alone can waste effort, such as forcing everyone into the wishlist. To establish causation, run an A/B test, or use quasi-experimental methods such as difference-in-differences when a test is not possible, and always check for confounders like user tenure or acquisition channel.

The income statement shows revenue, expenses and profit over a period. The balance sheet shows assets, liabilities and equity at a point in time. The cash flow statement shows cash from operating, investing and financing activities. They link together: net profit flows into retained earnings on the balance sheet and is the starting point of operating cash flow, and the closing cash balance from the cash flow statement equals cash on the balance sheet.

EBITDA is earnings before interest, taxes, depreciation and amortisation. It approximates operating profit generated by the core business before financing choices, tax rules and non-cash accounting charges. It is useful for comparing companies with different debt levels or asset ages and is used in valuation multiples such as EV/EBITDA. Its weakness is that it ignores capital expenditure and working capital needs, so a company can show strong EBITDA and still burn cash.

Working capital is current assets minus current liabilities, mainly receivables plus inventory minus payables. It is the money tied up in running daily operations. Too little means the company may struggle to pay suppliers and salaries; too much means cash is locked in slow inventory or unpaid customer invoices. Analysts track it because a growing business often needs more working capital, so fast growth can create cash shortages even when the business is profitable.

Both measure short-term liquidity. The current ratio is current assets divided by current liabilities; around 1.5 to 2 is often comfortable, though it varies by industry. The quick ratio excludes inventory and prepaid items: (cash plus marketable securities plus receivables) divided by current liabilities. It is stricter because inventory may not sell quickly. A retailer with a current ratio of 1.8 but a quick ratio of 0.4 depends heavily on selling its stock to pay bills.

Capex (capital expenditure) is spending on long-term assets that benefit several years, such as machinery, buildings or capitalised software development. It goes on the balance sheet and is expensed gradually through depreciation or amortisation. Opex (operating expenditure) covers day-to-day running costs such as salaries, rent and cloud subscriptions, and is expensed in the period it occurs. Moving from owned servers to cloud services shifts IT spending from capex to opex, which changes how budgets and business cases look.

The time value of money means a rupee today is worth more than a rupee in the future, because today's rupee can be invested to earn a return and future money carries inflation and risk. Future cash is converted to present value using PV = FV / (1 + r)^n. At a 10 percent discount rate, 1,10,000 rupees received after one year is worth 1,00,000 rupees today. It is the basis of NPV, IRR, loan EMIs and valuation.

Debt-to-equity equals total borrowings divided by shareholders' equity. It shows how much the company relies on borrowed money versus owners' funds. A ratio of 0.5 means 50 paise of debt for every rupee of equity. Higher leverage can boost returns but raises interest burden and risk in downturns. Acceptable levels depend on the industry: utilities and infrastructure carry more debt than software firms. Always read it with interest coverage, which is EBIT divided by interest expense.

Operating expenses here exclude depreciation. Gross profit is 50 - 30 = 20 crore. EBITDA is gross profit minus operating expenses: 20 - 12 = 8 crore. EBITDA margin is 8 / 50 = 16 percent. EBIT is EBITDA minus depreciation, 8 - 2 = 6 crore, which is a 12 percent operating margin. In an interview, state your assumption about whether operating expenses include depreciation, because that changes the answer.

An impact-effort matrix is a 2x2 grid that plots options by expected business impact against effort, cost or time. High impact and low effort are quick wins to do first; high impact and high effort are major projects to plan; low impact and low effort are fill-ins; low impact and high effort should be dropped. In a case interview, it helps you end with a clear, prioritised recommendation rather than a long list of ideas.

System testing is done by the QA team to verify that one system works against its functional and non-functional specifications. SIT (system integration testing) checks that connected systems exchange data correctly, such as CRM to billing to payment gateway. UAT (user acceptance testing) is done by business users to confirm the solution supports real business processes and is ready for go-live. UAT asks whether this is fit for our business, not just whether it matches the specification.

A test scenario is a high-level statement of what to test, usually derived from a business process or user story, such as Customer applies a discount coupon at checkout. A test case is a detailed, executable set of steps with preconditions, test data, expected result and actual result, such as applying an expired coupon to a 1,000 rupee cart shows an expiry message. One scenario usually produces several test cases covering positive, negative and edge conditions.

UAT sign-off is the formal acceptance by the business that the solution meets agreed requirements and is fit to go live, often with a list of known open defects and agreed workarounds. It should be given by the accountable business owner or product owner, not by the IT team or the BA. The BA prepares the evidence: test execution summary, defect status and traceability to requirements. Sign-off is recorded in writing, usually by email or in the test management tool.

Severity describes the impact of a defect on the system or business, such as critical when payments fail or low for a spelling mistake. Priority describes how urgently it must be fixed, which is a business decision. They can differ: a wrong company logo on the login page is low severity but high priority before a launch, while a crash in a rarely used year-end report may be high severity but lower priority if the report is months away.

Alpha testing is done internally, by employees or a selected group, in a controlled environment before the product is released to outsiders, and aims to catch major issues early. Beta testing releases the product to a limited group of real external users in real conditions to gather feedback on usability, performance and missing features before general release. For a mobile app, beta often uses store testing tracks, and feedback is fed into the final release backlog.

Release notes describe what changed in a specific release: new features, enhancements, fixed defects, known issues and any actions users must take. They are short and version-specific. A user manual or user guide explains how to use the whole system to complete tasks, with step-by-step instructions and screenshots, and is updated as the product evolves. BAs often review both, because users rely on them in the first weeks after go-live.

Test case ID: UAT-LOGIN-03. Precondition: registered customer with a verified mobile number. Steps: 1. Open the app and enter the registered mobile number. 2. Tap Send OTP. 3. Enter the 6-digit OTP received by SMS within 3 minutes. 4. Tap Verify. Expected result: the customer lands on the account dashboard, and the login is recorded in the activity log. Related negative cases: wrong OTP shows an error, and three wrong attempts lock login for 30 minutes.

Situation: during interviews for a new order system, a warehouse supervisor kept mentioning that Friday evenings were chaotic. Task: understand whether this mattered for the requirements. Action: instead of moving on, I asked what happened on Fridays and learned that bulk orders were split manually because of truck capacity limits. Result: we added an automatic order-splitting rule that nobody had listed, which saved the team about four hours a week and avoided a likely UAT failure.

Heatmaps aggregate where users click, move and scroll on a page, while session recordings replay individual user sessions. Funnel analysis tells you where users drop off, for example 40 percent leave on the address page; heatmaps and recordings help explain why, such as a hidden Continue button or a confusing pin code field. They are qualitative, so use them to form hypotheses and then validate fixes with an A/B test. Personal data must be masked in recordings.

A report is a multi-page, interactive view built in Power BI Desktop from one semantic model, with slicers, drill-through and cross-filtering. A dashboard is a single-page canvas in the Service made of tiles pinned from one or more reports, and is meant for monitoring key numbers at a glance. Dashboards support data alerts on card and KPI tiles, but have limited interactivity; clicking a tile opens the underlying report for detailed exploration.

COALESCE returns the first non-NULL value from a list of expressions, for example COALESCE(mobile, landline, 'Not available'). It is ANSI standard and works in all major databases. ISNULL (SQL Server) and IFNULL (MySQL) accept only two arguments and are vendor-specific. Analysts commonly use COALESCE to show zero instead of NULL after a LEFT JOIN, such as COALESCE(SUM(o.amount), 0), so that customers without orders appear with zero revenue.

Situation: my team moved reporting from Excel to Power BI, and I had two weeks to rebuild the weekly sales report. Task: deliver it on time without errors. Action: I took a short online course, practised data modelling on a copy of our data, and asked a colleague to review my DAX measures. I reconciled every number with the old Excel report before launch. Result: the report went live on schedule, and refresh time dropped from half a day to minutes.