Which action hides an old model from default lists, without deleting it?
Why A is the answer
Archiving it
Archiving hides a model from default list queries. It is not deleted, and it can still be referenced and used.
In detail
- Archiving hides the model from default list queries, and it can still be referenced and used.
- Archive rather than delete in regulated settings.
Use case
An illustrative scenario, not a real incident.
An old model should drop out of daily lists but stay available for audit. Archiving hides it from default list queries, and workflows can still reference it.
See it in different ways
stateDiagram-v2 [*] --> Trained Trained --> Registered: version and lineage Registered --> Deployed Deployed --> Monitored Monitored --> Retrained: drift alert Retrained --> Registered Deployed --> Archived: replaced
flowchart TD
Q{"Does audit need it?"}
Q -->|"Yes"| A0["Archive"]
Q -->|"No, and policy allows"| A1["Delete"]Key point: Archive to hide a model without deleting it.
Why the other options are wrong
- B. Renaming its experiment
- A rename changes nothing about use.
- C. Deleting its training data
- Deleting data harms the audit trail.
- D. Moving it to a notebook
- A notebook is not a model store.