Capgemini Interview Questions for Database Testing – 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, and integrity. It verifies that data stored in database tables matches business requirements and application behavior. 

Why Database Testing Is Important 

• Ensures data accuracy 

• Verifies backend processing 

• Prevents data corruption 

• Detects duplicate or missing records 

• Supports business-critical operations 

In Capgemini projects, database testing is widely used in banking, healthcare, insurance, and e-commerce applications where data reliability is essential. 

2. Why is Database Testing Important in Capgemini Projects? 

Capgemini works on enterprise-scale systems where even small data errors can cause major business impact. 

Reasons 

• Financial transactions must be accurate. 

• Customer information must remain consistent. 

• Healthcare records require high integrity. 

• Compliance regulations must be followed. 

• Large volumes of data need validation. 

Database testing helps ensure that applications function correctly and business operations are not affected by data-related issues. 

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 critical for database testing roles. 

4. What is CRUD? 

CRUD represents the four basic 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 in a table. 

Characteristics 

• Unique for every row 

• Cannot contain NULL values 

• Prevents duplicate records 

• Maintains entity integrity 

Example 

customer_id 

Every customer must have a unique customer ID. 

6. What is a Foreign Key? 

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

Benefits 

• Maintains referential integrity 

• Prevents invalid references 

• Supports table relationships 

Example 

An order table may contain a customer_id that references the customer table. 

7. What is Data Integrity? 

Data integrity means ensuring data is accurate and consistent across tables throughout its lifecycle. 

Types of Integrity 

• Entity Integrity 

• Referential Integrity 

• Domain Integrity 

Data integrity testing is a key responsibility of database testers. 

8. What is Normalization? 

Normalization is the process of reducing data redundancy and improving database organization. 

Benefits 

• Eliminates duplicate data 

• Improves consistency 

• Simplifies maintenance 

• Optimizes storage 

Common Forms 

• 1NF 

• 2NF 

• 3NF 

9. What is Denormalization? 

Denormalization is the process of adding redundancy to improve database performance. 

Benefits 

• Faster queries 

• Reduced joins 

• Better reporting performance 

Drawbacks 

• Increased storage 

• Potential 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 Older Than 30 

SELECT * FROM users 
WHERE age > 30; 

Filters records based on the specified condition. 

23. Fetch Unique Cities 

SELECT DISTINCT city 
FROM customers; 

DISTINCT removes duplicate values and returns only unique cities. 

24. Sort Records by 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 

• City-wise customer 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 with more than five employees. 

27. Difference Between WHERE and HAVING 

Example 

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

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

46. What is a JOIN? 

A JOIN is used to combine data from multiple tables based on related columns. 

Benefits 

• Retrieves related data 

• Reduces redundancy 

• Supports reporting and analytics 

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 

• Better query execution 

• Improved application performance 

67. Types of Indexes 

Clustered Index 

Determines physical storage order. 

Non-Clustered Index 

Maintains a separate structure for searching. 

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 utilized efficiently. 

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 

• Enhanced security 

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? 

Validate Inputs 

Verify correct parameter handling. 

Verify Outputs 

Ensure expected results are returned. 

Check Error Handling 

Validate behavior for invalid inputs. 

72. What is a Trigger? 

A trigger automatically executes SQL when specific database events occur. 

Events 

• INSERT 

• UPDATE 

• DELETE 

Triggers are commonly used for logging and auditing. 

73. Trigger Example 

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

This trigger creates an audit entry 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 that modified data is correctly stored. 

SQL Query 

SELECT address 
FROM users 
WHERE id = 101; 

88. Scenario: Validate Soft Delete 

Soft delete marks records inactive instead of removing them. 

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 email addresses. 

90. Scenario: Validate Bank Fund Transfer 

Validation Points 

• Debit from sender account 

• Credit to receiver account 

• Balance updated correctly 

• Transaction recorded 

SQL Query 

SELECT balance 
FROM accounts 
WHERE acc_id=101; 

91. Scenario: Validate Rollback 

Steps 

• Force a 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 set of SQL statements executed as a single unit. 

Characteristics 

• All operations succeed together. 

• All operations fail together. 

Example 

Bank transfer transactions. 

112. What Are ACID Properties? 

ACID properties ensure reliable transaction processing. 

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 for each other indefinitely. 

Example 

• Transaction A holds Resource X. 

• Transaction B holds Resource Y. 

• Both wait for each other. 

Neither transaction can proceed. 

114. What is Isolation Level? 

Isolation level controls visibility of uncommitted data during concurrent transactions. 

Common Levels 

• Read Uncommitted 

• Read Committed 

• Repeatable Read 

• Serializable 

Higher isolation levels provide better consistency but may impact 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 from the legacy database are successfully migrated to the new system without data loss. 

Real-Time Use Cases in Capgemini Projects