How should I practice Daily Successful Transactions Per Department?

Start by reading the full statement, solve the visible examples, then compare the pattern against related infosys onsite interview problems in FastPrep.

Is Daily Successful Transactions Per Department associated with infosys?

FastPrep tags this as a infosys onsite interview coding practice problem when the problem catalog has that company and stage context.

Problem · Database

Daily Successful Transactions Per Department

● Easy

infosysNEW GRADONSITE INTERVIEW

Problem statement

The table products stores one row per product, including that product's department. The table transactions stores one row per product sale attempt, including the transaction date, department, price, and status.

For every distinct transaction date and every department that appears in products, count the successful transactions. A transaction is successful when its status is exactly successful.

Return transaction_date, department_id, and successful_count. Include department-date pairs with zero successful transactions. Order rows by transaction_date ascending, then department_id ascending.

What the interview report shared

There is a products table with productId, deptId, and price, and a transaction table with productId, deptId, transactionDate, price, and status. Find, for every day, for each department, the count of successful transactions.

products
Column	Meaning
`product_id`	Unique product identifier
`dept_id`	Department identifier
`price`	Listed product price

transactions
Column	Meaning
`product_id`	Product sold or attempted
`dept_id`	Department of the transaction
`transaction_date`	Calendar date of the transaction
`price`	Transaction price
`status`	Transaction outcome text

Table schema

MySQLPostgreSQLPandas

Use the same input data with any supported language. Open the Schema tab in the editor to see the generated SQL setup or Pandas DataFrames.

products

One row per product.

Column	Type	Nullable	Description
product_idPK	Integer	No	—
dept_id	Integer	No	—
price	Integer	No	—

transactions

One row per transaction attempt.

Column	Type	Nullable	Description
product_id	Integer	No	—
dept_id	Integer	No	—
transaction_date	Date	No	—
price	Integer	No	—
status	Text	No	—

Expected result

Your query or function must return these columns.

Column	Type	Nullable	Description
transaction_date	Date	No	—
department_id	Integer	No	—
successful_count	Integer	No	—

Row order: must match exactly. Numeric tolerance: 0.

Constraints

Each table has between 1 and 10^5 rows.
product_id is unique and non-null in products.
dept_id, price, transaction_date, and status are non-null.
A transaction is successful only when status is exactly successful.