# Why must background be set to false on a Kyverno policy whose rules use request.userInfo, such as the requesting user's name or roles?

Kyverno, Hard (Expert), Policies. https://k8wiz.com/uquiz/why-must-background-be-set-to-false-on-a-kyverno-policy-whose-rules-use-requestuserinfo-such-as-the-requesting-users-name-or-rol

- A. Background scans run without an admission request, so there's no user
- B. request.userInfo is only populated for mutate rules, not validate rules
- C. Background scans run as cluster-admin, so userInfo checks always pass
- D. request.userInfo was deprecated and only works with background off

**Answer:** Background scans run without an admission request, so there's no user

**Explanation:** Background scans check resources already stored in the cluster, outside any admission request, so there's no requesting user, group or role. Kyverno requires background: false for rules that use variables only an admission request provides, and those rules then run only at admission time.