This is a dedicated watch page for a single video.
The downstream consumers of a Delta Lake table have been complaining about data quality issues impacting performance in their applications. Specifically, they have complained that invalid latitude and longitude values in the activity_details table have been breaking their ability to use other geolocation processes. A junior engineer has written the following code to add CHECK constraints to the Delta Lake table: ALTER TABLE activity_details ADD CONSTRAINT valid_coordinates CHECK ( latitude >= - 90 AND latitude = - 180 AND longitude <= 180 ); A senior engineer has confirmed the above logic is correct and the valid ranges for latitude and longitude are provided, but the code fails when executed. Which statement explains the cause of this failure?