A relation Student_Course(StudentID, CourseID, StudentName, CourseName) stores StudentName redundantly in every row for each course a given student takes. If a student's name changes, every single row containing that StudentID must be updated, or the data becomes inconsistent. What type of anomaly does this illustrate, and what normalization violation causes it?

The composite primary key of Student_Course is {StudentID, CourseID}. However, StudentName depends only on StudentID (a proper subset of the key), not on the full composite key — this is a classic partial dependency, which violates Second Normal Form (2NF). Because StudentName is redundantly stored in every row for that student, any change to it must be propagated to all matching rows, or different rows will show conflicting names for the same student — this inconsistency risk is precisely what is termed an update anomaly.