Cuestionario vinculado a una guía · Medio Nivel
Prueba de deuda técnica oculta en sistemas de aprendizaje automático
Identifique dependencias de datos, entrelazamientos y bucles de retroalimentación que crean costos de mantenimiento ocultos en los sistemas de aprendizaje automático implementados.
Pregunta 1 de 8
Which downstream dependency is an undeclared consumer?
Vista previa de cada pregunta8 preguntas
Las respuestas y explicaciones aparecen a medida que realiza el cuestionario.
- Which downstream dependency is an undeclared consumer?
- A downstream component that uses a feature or prediction without tracked ownership
- A model trained without labels
- A missing value in a tensor
- A GPU that lacks a driver
- How can a model create a feedback loop in ranking?
- Its loss function changes the programming language
- Its selections shape which future interactions become training data
- Its predictions remove all user behavior
- Its features become immutable
- What does entanglement describe in an ML system?
- Training data contain only one class
- All model parameters are independent
- Changes in one component can have nonlocal effects through dependencies
- The model is stored in a container
- Why can a feature schema change be risky when several models share a pipeline?
- It removes the need for integration tests
- It automatically improves every model
- Shared features cannot be versioned
- The change can alter behavior for multiple consumers
- What can schema contracts and ownership help expose?
- The model's exact future accuracy
- Changes in data meaning and responsibility across system boundaries
- A guaranteed causal relationship
- The optimal number of latent factors
- Why may model-only monitoring miss an upstream data issue?
- Monitoring disables prediction logs
- The model cannot receive data
- Input or pipeline failures can cause output changes before model code changes
- Upstream systems are always stable
- How can a team reduce risk when retiring an unused model?
- Remove its evaluation report first
- Delete the artifact without checking dependencies
- Keep every model forever
- Map consumers and use a staged retirement plan
- Which symptom can indicate accumulating technical debt?
- Changes become slower and rollback or regression analysis becomes difficult
- Every model has fewer parameters
- Training loss decreases
- The repository contains tests