CERTIFIED-MACHINE-LEARNING-PROFESSIONAL Question #11: Real Exam Question with Answer & Explanation

Question

Which of the following is a benefit of logging a model signature with an MLflow model?

Options

• AThe model will have a unique identifier in the MLflow experiment
• BThe schema of input data can be validated when serving models
• CThe model can be deployed using real-time serving tools
• DThe model will be secured by the user that developed it
• EThe schema of input data will be converted to match the signature

Explanation

Logging a model signature in MLflow enables schema enforcement, which means MLflow will automatically attempt to coerce or convert input data types to match the expected signature before the model runs - for example, converting integers to floats if the signature requires floats. This goes beyond mere validation; MLflow actively transforms compatible types to fit the signature schema.

Why the distractors are wrong:

• A - Unique identifiers (run IDs) are assigned to every MLflow run regardless of whether a signature is logged.
• B - Validation does occur, but it's a consequence of schema enforcement, not its primary benefit; more importantly, MLflow also converts data, making E the more precise and complete answer.
• C - Real-time serving capability depends on the model flavor and deployment infrastructure, not on whether a signature was logged.
• D - MLflow has no built-in security mechanism tied to model signatures; access control is handled separately.

Memory tip: Think of a model signature like a power adapter - it doesn't just check if your plug fits, it actually converts the current to match what the device needs. "Signature → Schema conversion" is the key phrase to lock in.

No community discussion yet for this question.