Kvíz spojený s průvodcem · Střední úroveň
Prefekt a dagster pro ML Orchestration Quiz
Porovnejte toky Prefect a prostředky Dagster pro úlohy ML, včetně opakování, linií, plánování, nasazení a provozu.
Otázka 1 z 8
Jak prefekt běžně definuje tok?
Náhled každé otázky8 otázky
Odpovědi a vysvětlení se zobrazují, jak budete v kvízu.
- Jak prefekt běžně definuje tok?
- A Python function that cannot call another flow
- A model evaluation metric that schedules jobs
- A decorated Python function that composes workflow logic
- A graph of named data assets and their dependencies
- Jak Dagster představuje pracovní postup zaměřený na aktiva?
- An invocation record for a scheduled workflow
- Named data outputs and their production dependencies
- A task execution state with no output lineage
- A set of training hyperparameters
- Proč může být automatické opakování pro některé kroky pracovního postupu nebezpečné?
- Prefect automatically detects non-idempotent operations and suppresses duplicate writes
- A task retry never calls its Python function more than once
- Setting a retry count of one prevents the first attempt from running
- A retry can repeat an external side effect when the operation is not idempotent
- Co by se mělo zaznamenat, aby se podpořila linie artefaktů ML?
- Dataset identity, code revision, configuration, and artifact version
- Only the schedule and run name
- Only the UI layout used to launch jobs
- Pouze konečné skóre přesnosti
- What should teams compare in a representative orchestrator trial?
- Only whether each workflow step is decorated
- Only the preferred dashboard color scheme
- Debugging, deployment, lineage, backfills, and operating requirements
- Only validation accuracy for the trained model
- Kdy by mohl být Dagsterův model aktiv užitečný?
- When a task has no outputs to track
- When teams need to track produced data and model outputs with dependencies
- Only when serving models on phones
- When the workflow should have no state
- What should happen to a training job that needs specialized compute?
- The orchestrator should run all GPU training inside its own process
- The training job should be hidden inside a schedule definition
- The model data should be stored as a secret
- Submit the job to suitable compute and track its outputs
- Which statement about Prefect and Dagster is accurate?
- Choose based on workflow abstractions and team operating needs
- One always runs faster for every ML workflow
- Either tool guarantees model validity
- Both remove the need to track data versions