Question

As an enterprise security administrator, you create a security configuration in an organization that enables Code Security and Secret Protection, and you set the configuration's policy to 'Enforce'. A repository administrator later tries to individually disable secret scanning on a repository the configuration is applied to. What is the outcome, and why?

Accepted Answer

The repository administrator cannot change the settings the configuration manages, because 'Enforce' locks those feature settings so they cannot be modified at the repository level.

Answer

The repository administrator can disable secret scanning, because security configurations only set initial defaults and never restrict repo-level changes.

Answer

The repository administrator can disable secret scanning only after requesting a bypass approval from the security manager.

Answer

The repository administrator cannot change any repository setting at all, because 'Enforce' places the entire repository in read-only mode.