Course custom drop-down field is not treated as mandatory during course creation when it has a default value configured and marked as mandatory under Custom field Feature
When creating an advanced course and setting up a custom field as a drop-down, administrators are able to save the course without selecting a value from the drop-down. This happens because the field has a default value pre-set, and the system automatically saves the first option from the drop-down, bypassing the mandatory selection requirement. If the field type is String or Date and no default value is set, it will be treated as mandatory, requiring users to make an explicit selection before saving the course. Questions this answers: Why can a mandatory drop-down custom field be saved without a choice?