Isku duubnida Wejiga Kediska

Jawaabaha iyo sharraxaadaha waxay soo baxayaan markaad qaadanayso kediska.

1. A model repository is hosted on Hugging Face. What does hosting establish?
   • That the repository is published there, not that every claim or file is independently verified
   • That its license fits every use
   • That its evaluation results are complete
   • That its code is safe to execute
2. Which details should a model card help a reviewer understand?
   • Only a benchmark name without evaluation conditions
   • Intended use, evaluation, limitations, training information, and licensing
   • Only the latest download count
   • The performance of every variant
3. A model requires repository-provided custom code to load. What additional concern arises?
   • Only the expected prediction accuracy
   • Only the general task description
   • Software trust, separate from statistical performance
   • Only the repository download count
4. A community account uploads a quantized model based on a known release. What should be checked?
   • The original model’s score alone
   • Only the base model’s reputation
   • Only the downloaded weight file’s size
   • The base model, conversion method, license, files, and evaluation of the converted artifact
5. Why pin an exact repository revision?
   • To guarantee a license
   • To make an evaluation reproducible and identify the files used
   • To avoid reading a model card
   • To receive future security fixes automatically
6. A license appears in repository metadata. What should a user do?
   • Use the artifact commercially by default
   • Assume the metadata label settles all terms
   • Review the actual license and provenance for the intended use
   • Ignore publisher identity
7. A platform hosts model files from multiple publishers. What should the reviewer identify?
   • The exact publisher and artifact revision
   • Only the hosting platform
   • Only the model family’s marketing name
   • The largest file in the repository
8. What is appropriate before production adoption?
   • Rely on a demo Space alone
   • Load moving main-branch files directly in production
   • Skip resource testing
   • Evaluate in a controlled environment, record dependencies, and test the intended task