The tables above show information on a school database. The questions below will test your understanding of the violations of constraints. Check all the constraints that the operations below violate. Flag question: Question 6Question 6Tips2 ptsUPDATE Enrollments SET StudentID = 10, CourseID = 999 WHERE EnrollmentID = 1;Group of answer choicesKey constraintEntity integrity constraintReferential integrity constraintNo Violation

Without the actual tables, it's hard to determine the exact constraints that are violated. However, based on the query, here are the possible violations:

1. Key Constraint: If the EnrollmentID = 1 already exists in the table, then changing the StudentID and CourseID might violate the key constraint if a record with StudentID = 10 and CourseID = 999 already exists.

2. Entity Integrity Constraint: This constraint states that no attribute (column) of a primary key (unique identifier for records in a table) can contain a null value. If either StudentID = 10 or CourseID = 999 does not exist, then this constraint is violated.

3. Referential Integrity Constraint: This constraint is about maintaining consistency in a database. It ensures that the relationship between tables remains consistent. More specifically, it ensures that the foreign key values in the Enrollments table match the primary key values in the related table. If either StudentID = 10 or CourseID = 999 does not exist in their respective tables, then this constraint is violated.

Again, without the actual tables, it's hard to determine the exact constraints that are violated.