Gids-gekoppelde quiz · Middelmatig Niveau
GitHub Acties voor ML-pijplijnenquiz
Bouw gefaseerde ML-automatisering met Actions-taken, traceerbaarheid van artefacten, beschermde releases en zorgvuldige omgang met runners en inloggegevens.
Vraag 1 van 8
Wat definieert een GitHub Actions-workflow?
Bekijk elke vraag8 vragen
Antwoorden en uitleg verschijnen terwijl je de quiz doet.
- Wat definieert een GitHub Actions-workflow?
- Triggers, jobs, runners and steps
- A container image manifest and layer list
- Branch protection rules for a repository
- The model dependency lockfile alone
- Waarom snelle pull-request-controles scheiden van volledige GPU-training?
- It guarantees model quality without evaluation
- It keeps feedback quick while reserving specialized compute for expensive work
- It removes all runner maintenance
- It makes GPU hardware available on every runner
- Wat moet een evaluatierapport verbinden met het later gepromote artefact?
- The author’s username alone
- The workflow display name only
- The artifact digest or another immutable identity
- A cache key that changes each run
- Waarom vermijden dat repositorygeheimen worden blootgesteld aan niet-vertrouwde pull-request-code?
- Actions cannot run without write tokens
- Secrets are required to run Python imports
- It makes all validation nondeterministic
- Workflow code could use them to access external systems
- Wat kan OIDC bieden als het is geconfigureerd met een cloudprovider?
- A permanent model accuracy certificate
- Short-lived credentials tied to workflow identity
- An artifact cache without access control
- A Python virtual environment
- How should a dependency cache be used in an Actions workflow?
- Keep a deployable model file between workflow runs as the official release record
- Reuse dependencies with a key that ignores dependency input changes
- Speed up repeated dependency setup with keys based on dependency inputs
- Use a mutable image tag as the only record of workflow output
- What does an environment protection rule add to a model release job?
- A lockfile for training data
- An automatic guarantee that metrics are unbiased
- A new GPU device
- A controlled approval or deployment condition
- What does GitHub Actions alone not guarantee?
- That training data, evaluation or release decisions are sound
- That defined workflow steps execute on a runner
- That jobs can depend on prior jobs
- That artifacts can be uploaded