問題文
Image pulls succeed for most instances but intermittently fail with authorization errors on newly created instances. The identity's role assignment was added minutes before the failures. What is the likely cause?
選択肢
- The role assignment had not yet propagated to all the components that evaluate it when those instances started, so their pulls were rejected
- The image's digest changed between pulls, so the instances that fetched the newer digest are not covered by the permission that was granted
- The registry is throttling the burst of pulls that the new instances issue, and the rejection is reported to the caller as an authorization failure
- The newly created instances resolved a different image reference because the revision was updated during the rollout, and that reference is in another registry