Ikibazo gihuza ibibazo · Hagati Urwego
ML Gutanga Urunigi Umutekano hamwe nicyitegererezo cyo gusinya
Tandukanya ubunyangamugayo nubukorikori hamwe nubwiza bwikitegererezo, kandi umenye ingaruka ziterwa no gukurikiranwa kutizewe no kugenzura intege nke.
Ikibazo 1 Bya 8
Ni iki kugenzura umukono wa digitale ku gihangano gishyiraho cyane?
Reba buri kibazo8 ibibazo
Ibisubizo nibisobanuro bigaragara mugihe ufata ikibazo.
- Ni iki kugenzura umukono wa digitale ku gihangano gishyiraho cyane?
- 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
- Ni ukubera iki gupakira umutobe wa Python utizewe?
- It always deletes the source file
- Deserialization can execute arbitrary code
- It cannot represent numeric tensors
- It guarantees a model will be biased
- Niki gishobora kubaka gihamye cyongerwaho ibihangano byashyizweho umukono?
- 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
- Kuki kohereza bigomba kubahiriza umukono?
- 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
- Niki umukono wemewe unanirwa kwerekana?
- 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
- 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
- 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
- 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