Microsoft GH-500 Dumps Questions Answers

When a person's access to a private repository is removed, GitHub deletes that person's private forks belonging to the repository's network. This prevents the GitHub-hosted fork from remaining available after the user loses authorization to the upstream private repository. GitHub cannot, however, automatically erase local clones that the person previously downloaded to their own computers; the documentation explicitly states that local clones are retained. Removing one individual's access also does not necessarily revoke an entire team's access, because team permissions are managed separately. Nor does GitHub automatically delete confidential information that may have been copied outside the repository. GitHub therefore advises organizations to ensure that former collaborators appropriately dispose of confidential or proprietary information. The direct platform behavior described in the question is deletion of the user's private forks.

Secret scanning for a private repository is enabled through the repository's security configuration/settings, currently located under Settings → Security and quality → Advanced Security. In current GitHub terminology, enabling Secret Protection enables secret scanning alerts for an eligible private or internal repository. Repository rulesets control policies such as branch protection, required checks, and merge conditions; they are not the primary mechanism for enabling secret scanning. GitHub also does not use a secret.yml file to activate the feature. Code scanning default setup configures CodeQL analysis and is separate from secret detection. Organization owners can additionally enable Secret Protection and secret-scanning capabilities at scale by applying security configurations to repositories. Consequently, the code security or Advanced Security settings area is the correct location, making A the correct answer.

Code scanning is a static analysis feature that examines your source code to identify security vulnerabilities and coding errors . It runs either on every push, pull request, or a scheduled time depending on the workflow configuration.

It does not automatically contact maintainers, scan full Git history, or block pushes unless explicitly configured to do so.