Access Control Lists (ACLs) are used in database security to specify the access privileges granted to users or groups for specific database objects. An ACL consists of a list of permissions associated with a resource, indicating which users or system processes are granted access and what operations are allowed for those users or processes. By configuring ACLs, database administrators can control who can access and manipulate the data stored in the database, helping to enforce security policies and protect sensitive information.

Load testing assesses the system's performance under expected load levels, including the ability to handle an increasing number of transactions. It helps determine the system's response time and resource utilization under typical usage scenarios.

Large and complex databases introduce data integration challenges in database testing. Testing against such databases requires careful consideration of how different components interact and exchange data, as well as ensuring the accuracy and consistency of data across various systems. Managing these integration challenges is crucial for comprehensive testing and ensuring the reliability of the database system.

In this scenario, the immediate action should be to analyze system logs and performance metrics to identify the root cause of the crash. Restarting the system or ignoring the issue can mask underlying problems and lead to inaccurate test results. Reporting the issue to the development team is also necessary, but analyzing logs and metrics first helps provide them with detailed information to address the problem effectively.

The SQL GROUP BY clause is used to group rows that have the same values into summary rows, such as "find the number of customers in each city" or "calculate the total sales for each product category." It is typically used with aggregate functions (like COUNT, SUM, AVG, etc.) to perform calculations on each group of data. This clause helps in analyzing data by organizing it into manageable chunks based on specified criteria.

Referential integrity constraint ensures that a foreign key in one table references a primary key in another table. It maintains the consistency and integrity of the data by enforcing relationships between tables. This constraint prevents actions that would violate these relationships, such as deleting a record with a referenced foreign key.

A rollback plan is crucial in data migration testing as it ensures that in case of any failures or issues during migration, the system can be reverted back to its previous state, minimizing risks and ensuring data integrity.

ACID stands for Atomicity, Consistency, Isolation, and Durability, which are the four properties ensuring the reliability of transactions in a database system.

To prevent conflicts with existing schemas during CI/CD pipeline executions, it's essential to use a database migration tool that supports schema comparison, enabling the tool to identify and resolve any conflicts before applying migration scripts.

Referential integrity constraint ensures that values in one column (or a group of columns) in one table correspond to values in another table's column(s) with a primary key constraint.