quiz bu lëkkale ak tegtal · Diggante Niveau

Defar ab quiz buy jàng masin

Yamale kodu ML, royuwaayi done, kaaye, test, tabb ak mbiri art ci wër liggéeyu ekip buñ mëna defaraat. ngir ñiy liggéeyandoo.

Yooni njiit yu jëm ciDefar ab projet buy jàng masin
Laaj 1 de 8

What should a project README help a new contributor understand?

Xoolaatal laaj bu nekk8 laaj

Sooy def quiz bi, tontu yi ak leeral yi dañuy feeñ.

  1. What should a project README help a new contributor understand?
    • Production credentials for every collaborator
    • Every hyperparameter before defining a task
    • Data access, workflow commands, prerequisites and limitations
    • A guarantee that evaluation results will be accurate
  2. Why separate reusable code from exploratory notebooks?
    • It prevents tests from importing shared transformations
    • It lets scripts, tests and notebooks share one implementation
    • It requires separate code copies for each notebook
    • It forces notebooks to execute cells in order
  3. How should sensitive or bulky datasets usually be handled?
    • Commit every copy to the repository
    • Store access tokens beside the raw data
    • Replace data governance with folder names
    • Use controlled storage and versioned references rather than blindly committing them to Git
  4. Where should parameters that vary across runs be stored?
    • Parameters that vary between runs without editing core logic
    • Source constants manually rewritten for every run
    • Notebook output text from a previous experiment
    • Serialized predictions from the last model
  5. What does a distinction between raw and processed data support?
    • Guaranteeing the model is unbiased
    • Eliminating data versioning
    • Tracing transformations and rerunning preprocessing
    • Storing only final predictions
  6. Why should generated artifacts have a clear storage policy?
    • They are always safe to commit
    • They can be large, sensitive or needed to reproduce results
    • They replace source code
    • They automatically contain the project license
  7. How should a team treat a project template such as Cookiecutter Data Science?
    • Copy every folder even when unused
    • Treat its layout as a legal requirement
    • Use it instead of tests
    • Use it as a starting convention and adapt it to the workflow
  8. Which automated check would catch a feature transform changing its expected columns or missing-value behavior?
    • A test for expected columns and missing-value cases
    • A linter checking code style
    • A type annotation on the function signature
    • A README description of the transform