ML Supply Chain Security and Model Signing Quiz

Answers and explanations appear as you take the quiz.

1. What does verifying a digital signature on an artifact establish most directly?
   • The bytes match a signature associated with a trusted signing identity
   • The model is accurate on every future dataset
   • The model is free of bias
   • The training data were collected ethically
2. Why is loading an untrusted Python pickle risky?
   • It always deletes the source file
   • Deserialization can execute arbitrary code
   • It cannot represent numeric tensors
   • It guarantees a model will be biased
3. What can build provenance add to a signed model artifact?
   • A model card describing intended use
   • A vulnerability report listing known component issues
   • Evidence about source, build steps and inputs
   • An evaluation report containing only validation metrics
4. Why must deployment enforce signature verification?
   • Only evaluation reports need verification
   • Signing automatically blocks every unsigned file
   • Verification changes model weights into a safe format
   • A signature provides no protection if deployment accepts artifacts without checking it
5. What does a valid signature fail to prove?
   • That the bytes match the signed digest
   • That the signed model is safe or accurate
   • That a trusted identity signed it under policy
   • That the artifact was not altered after signing
6. Why keep a dependency lockfile and source revision in release provenance?
   • They replace model evaluation
   • They guarantee every package has no vulnerabilities
   • They help trace which inputs produced the deployed artifact
   • They ensure the host driver is installed
7. How does an SBOM differ from a signature?
   • It describes the build workflow and source revision
   • It verifies artifact bytes against a signing identity
   • It reports model quality on an evaluation set
   • It inventories software components; it answers a different question from integrity verification
8. Which action protects signing credentials?
   • Limit key access and plan rotation or managed identity use
   • Commit private keys into the model repository
   • Share credentials across all build users
   • Disable verification after signing