Cognizant Database Testing Interview Questions – Complete Guide with SQL, Scenarios & Real-Time Use Cases

1. What is Database Testing? 

Database testing validates backend data using SQL queries to ensure accuracy, consistency, integrity, and reliability. It verifies that data stored in database tables matches application behavior and business requirements. 

Database testing is essential for validating data created, modified, retrieved, and deleted by enterprise applications. 

Why Database Testing Is Important 

• Ensures data accuracy 

• Verifies backend processing 

• Prevents data corruption 

• Supports business-critical transactions 

• Maintains data consistency 

In Cognizant projects, database testing is widely used across banking, healthcare, insurance, retail, and telecom domains. 

2. Why is Database Testing Important in Cognizant Projects? 

Cognizant works on enterprise-scale applications where data accuracy directly impacts business decisions. 

Key Reasons 

• Financial transactions require precision. 

• Customer information must remain accurate. 

• Business reports depend on correct data. 

• Regulatory compliance must be maintained. 

• Large-scale systems process millions of records. 

Database testing helps ensure that applications remain reliable and trustworthy. 

3. What Skills Are Required for Database Testing? 

A database tester should possess both technical and business knowledge. 

SQL Knowledge 

• SELECT 

• INSERT 

• UPDATE 

• DELETE 

• JOINs 

• Subqueries 

Understanding of Database Concepts 

• Primary Keys 

• Foreign Keys 

• Constraints 

• Indexes 

• Transactions 

Business Logic Understanding 

• Workflow validation 

• Data processing rules 

• Business calculations 

• Domain-specific requirements 

Strong SQL and analytical skills are essential for database testing roles. 

4. What is CRUD? 

CRUD represents the four fundamental operations performed on database records. 

CRUD validation is one of the most common database testing activities. 

5. What is a Primary Key? 

A primary key is a column that uniquely identifies each record. 

Characteristics 

• Unique for every row 

• Cannot contain NULL values 

• Prevents duplicate records 

Example 

customer_id 

Each record must have a unique identifier. 

6. What is a Foreign Key? 

A foreign key is a column that establishes a relationship between two tables. 

Benefits 

• Maintains referential integrity 

• Supports parent-child relationships 

• Prevents invalid references 

Example 

An order table may reference a customer table using a customer_id field. 

7. What is Data Integrity? 

Data integrity means ensuring data accuracy and consistency across tables. 

Types of Integrity 

• Entity Integrity 

• Referential Integrity 

• Domain Integrity 

Data integrity validation is a key responsibility of database testers. 

8. What is Normalization? 

Normalization is the process of reducing data redundancy. 

Benefits 

• Eliminates duplicate data 

• Improves consistency 

• Simplifies maintenance 

• Optimizes storage 

Common Normal Forms 

• First Normal Form (1NF) 

• Second Normal Form (2NF) 

• Third Normal Form (3NF) 

9. What is Denormalization? 

Denormalization is the process of adding redundancy for performance. 

Benefits 

• Faster query execution 

• Reduced joins 

• Better reporting performance 

Drawbacks 

• Increased storage usage 

• Potential data duplication 

10. What is a Schema? 

A schema is a logical container for database objects. 

Database Objects 

• Tables 

• Views 

• Indexes 

• Stored Procedures 

• Functions 

• Triggers 

Schemas help organize and manage database resources. 

SQL Interview Questions for Testing (21–45) 

21. Fetch All Records from a Table 

SELECT * FROM users; 

Returns all rows and columns from the users table. 

22. Fetch Users with Age Greater Than 30 

SELECT * 
FROM users 
WHERE age > 30; 

Filters records based on the specified condition. 

23. Fetch Unique City Names 

SELECT DISTINCT city 
FROM customers; 

DISTINCT removes duplicate values and returns only unique city names. 

24. Sort Records by Creation Date 

SELECT * 
FROM orders 
ORDER BY created_date DESC; 

Returns records sorted by creation date in descending order. 

25. What is GROUP BY? 

GROUP BY groups rows with the same values. 

Example 

SELECT department, 
      COUNT(*) 
FROM employees 
GROUP BY department; 

Common Use Cases 

• Department-wise employee count 

• Product-wise sales count 

• Customer-wise order count 

26. What is HAVING? 

HAVING filters grouped data after aggregation. 

Example 

SELECT department, 
      COUNT(*) 
FROM employees 
GROUP BY department 
HAVING COUNT(*) > 5; 

Returns only departments containing more than five employees. 

27. Difference Between WHERE and HAVING 

JOIN-Based Database Testing Interview Questions (46–65) 

46. What is a JOIN? 

A JOIN is used to retrieve data from multiple tables. 

Benefits 

• Combines related data 

• Supports reporting 

• Validates relationships 

47. Types of JOINs 

INNER JOIN 

Returns matching records from both tables. 

LEFT JOIN 

Returns all records from the left table and matching records from the right table. 

RIGHT JOIN 

Returns all records from the right table and matching records from the left table. 

FULL JOIN 

Returns all records from both tables. 

48. INNER JOIN Example 

SELECT o.order_id, 
      c.name 
FROM orders o 
INNER JOIN customers c 
ON o.customer_id = c.id; 

Returns customers who have placed orders. 

49. LEFT JOIN Use Case 

Find records without matching data. 

SELECT c.name, 
      o.order_id 
FROM customers c 
LEFT JOIN orders o 
ON c.id = o.customer_id; 

Useful for identifying missing relationships. 

50. Scenario: Customers With No Orders 

SELECT c.id 
FROM customers c 
LEFT JOIN orders o 
ON c.id = o.customer_id 
WHERE o.id IS NULL; 

Returns customers who have never placed an order. 

Indexes, Stored Procedures & Triggers (66–85) 

66. What is an Index? 

An index improves query performance by reducing table scans. 

Benefits 

• Faster searches 

• Improved query execution 

• Better application performance 

67. Types of Indexes 

Clustered Index 

Defines physical storage order. 

Non-Clustered Index 

Maintains a separate search structure. 

Composite Index 

Created using multiple columns. 

68. How Do Testers Validate Index Usage? 

By checking execution plans using EXPLAIN. 

Example 

EXPLAIN 
SELECT * 
FROM users 
WHERE email=’test@gmail.com‘; 

This helps identify whether indexes are being used effectively. 

69. What is a Stored Procedure? 

A stored procedure is pre-compiled SQL code stored in the database. 

Benefits 

• Reusability 

• Better performance 

• Centralized business logic 

70. Stored Procedure Example 

CREATE PROCEDURE getUser(IN uid INT) 
BEGIN 
  SELECT * 
  FROM users 
  WHERE id = uid; 
END; 

71. How Do Testers Test Stored Procedures? 

Input Validation 

Verify parameter handling. 

Output Verification 

Validate returned results. 

Error Handling 

Check behavior for invalid inputs. 

72. What is a Trigger? 

A trigger automatically executes SQL on INSERT, UPDATE, or DELETE operations. 

Common Uses 

• Audit logging 

• History tracking 

• Compliance monitoring 

73. Trigger Example 

CREATE TRIGGER audit_update 
AFTER UPDATE ON orders 
FOR EACH ROW 
INSERT INTO audit_log 
VALUES (NEW.id, NOW()); 

Creates an audit record whenever an order is updated. 

Scenario-Based Database Testing Interview Questions (86–110) 

86. Scenario: Validate User Registration 

Validation Points 

• Record inserted 

• Default values assigned 

• User information stored correctly 

SQL Query 

SELECT * 
FROM users 
WHERE email=’test@gmail.com‘; 

87. Scenario: Validate Update Operation 

Verify modified user information. 

SQL Query 

SELECT address 
FROM users 
WHERE id = 101; 

88. Scenario: Validate Soft Delete 

Verify inactive records. 

SQL Query 

SELECT * 
FROM users 
WHERE is_active=’N’; 

89. Scenario: Detect Duplicate Records 

SELECT email, 
      COUNT(*) 
FROM users 
GROUP BY email 
HAVING COUNT(*) > 1; 

Identifies duplicate user records. 

90. Scenario: Validate Banking Transaction 

Validation Points 

• Debit entry created 

• Credit entry created 

• Balance updated correctly 

• Transaction history recorded 

SQL Query 

SELECT balance 
FROM accounts 
WHERE acc_id = 101; 

91. Scenario: Validate Rollback 

Steps 

• Force transaction failure. 

• Verify rollback execution. 

• Ensure no partial data is saved. 

Expected Result 

Database remains consistent after failure. 

Advanced Database Testing Interview Questions (111–130) 

111. What is a Transaction? 

A transaction is a group of SQL statements executed as a single unit. 

Characteristics 

• All operations succeed together. 

• All operations fail together. 

112. What Are ACID Properties? 

ACID properties ensure reliable database transactions. 

Atomicity 

All or nothing execution. 

Consistency 

Database remains valid. 

Isolation 

Transactions do not interfere. 

Durability 

Committed changes remain permanent. 

113. What is a Deadlock? 

A deadlock occurs when two transactions wait indefinitely for each other. 

Example 

• Transaction A locks Resource X. 

• Transaction B locks Resource Y. 

• Both wait for each other. 

Neither transaction can proceed. 

114. What is Isolation Level? 

Isolation level controls visibility of uncommitted data during transactions. 

Common Levels 

• Read Uncommitted 

• Read Committed 

• Repeatable Read 

• Serializable 

Higher isolation levels improve consistency but may reduce performance. 

115. What is Data Migration Testing? 

Data migration testing validates data accuracy after migration from one system to another. 

Validation Areas 

• Record counts 

• Data accuracy 

• Data transformation rules 

• Referential integrity 

• Missing records 

Example 

Verify that all customer records and transaction data are migrated successfully without data loss or corruption. 

Real-Time Use Cases in Cognizant Projects