問題文
The command line tool authenticates with a key and can be run inside a pipeline step. Why is it useful to have the same evaluation available as a command?
選択肢
- The command is the only supported way to create a policy, so the console pages for policies are read-only views of whatever was created there.
- The command bypasses the tenant entirely and evaluates against a local copy of the policy set, so it keeps working when the tenant is unreachable and is the recommended way to scan air-gapped repositories without any network access.
- A command can be placed at whatever point of a pipeline the team controls, so the check runs even where no native integration exists.
- The command requires an administrator role, so it can perform actions the console cannot, such as changing a policy while a build waits on it.