CAP CAP Model Deployment & Lifecycle Management

Question 1

Which deployment pattern runs the new model alongside the old model and gradually shifts traffic to the new one?

Accepted Answer

Canary / gradual rollout

Answer

Big-bang deployment

Answer

Rollback deployment

Answer

Blue-green deployment

Question 2

Model monitoring in production should track which of the following to detect data drift?

Accepted Answer

Distribution of input features over time

Answer

Server CPU usage only

Answer

Number of database tables

Answer

Color scheme of dashboards

Question 3

What does 'model staleness' mean in the CAP lifecycle management context?

Accepted Answer

Model performance has degraded because the real-world environment has changed

Answer

The model has too many parameters

Answer

The model was never deployed

Answer

The model uses outdated visualization libraries

Question 4

Which artifact MUST be version-controlled alongside model code to ensure reproducibility?

Accepted Answer

Training data schema and model hyperparameters

Answer

Dashboard color themes

Answer

Email correspondence

Answer

Project management ticket IDs

Question 5

A/B testing in model deployment is used to:

Accepted Answer

Compare two model versions using live traffic and business metrics

Answer

Train two models on the same data simultaneously

Answer

Replace unit testing

Answer

Avoid data collection

Question 6

Which document formally describes a model's intended use, limitations, and performance across subgroups?

Accepted Answer

Model card

Answer

Data dictionary

Answer

Entity-relationship diagram

Answer

Sprint retrospective