What is the primary purpose of Push Protection in GitHub Advanced Security?

To block secrets from being pushed to a repository at the source, before they are uploaded

To automatically rotate any secrets that are detected in a repository

To encrypt all secrets stored in a repository so they cannot be read by unauthorized users

To scan existing repository history and alert on secrets that were pushed in the past

A developer at your company attempts to push a commit that contains a valid AWS access key ID and secret access key. Push Protection is enabled for the repository. The push is blocked, and the developer sees a message with a URL to a remediation guide. The developer needs to proceed with the push because the secret is a test credential that is intentionally committed. What must the developer do to push the commit?

Use the 'Allow secret' option in the GitHub UI, then re-attempt the push.

Contact a repository admin to disable Push Protection permanently.

Remove the secret from the commit, push, then add it back in a later commit.

Force push with --force to override the protection.

Which of the following is an example of a secret type that Push Protection can detect and block?

A password that is stored in a plain text file

An API key that is encrypted with a strong algorithm

A random string of 20 characters that is not a known secret pattern

A personal access token for GitHub

Your organization uses GitHub secret scanning. You receive a large number of alerts daily. You want to ensure that your security team first addresses the most critical exposures. What feature should you rely on?

Prioritized alerting for high-confidence secrets

Secret scanning validity checks

Custom patterns for secret scanning

At which point in the development workflow does Push Protection act to prevent secret exposure?

During code review, when a pull request is opened

During the git push operation, before the commit is uploaded to the remote repository

During the initial commit creation, before the commit is saved locally

During the build process in a CI/CD pipeline

GitHubAdvanced Security (GH-500)

Domain 2Objective 2

Prevent Secret Exposure GH-500 Practice Questions (Page 4)

Part of the Configure and use Secret Protection (formerly secret scanning) domain, which accounts for 15-20% of the GH-500 exam.

25questions here

5free pages

7concepts

15-20%of the exam

Questions 16–20

16foundation · easy
What is the primary purpose of Push Protection in GitHub Advanced Security?
Select an answer first
17application · medium
A developer at your company attempts to push a commit that contains a valid AWS access key ID and secret access key. Push Protection is enabled for the repository. The push is blocked, and the developer sees a message with a URL to a remediation guide. The developer needs to proceed with the push because the secret is a test credential that is intentionally committed. What must the developer do to push the commit?
Select an answer first
18foundation · easy
Which of the following is an example of a secret type that Push Protection can detect and block?
Select an answer first
19application · medium
Your organization uses GitHub secret scanning. You receive a large number of alerts daily. You want to ensure that your security team first addresses the most critical exposures. What feature should you rely on?
Select an answer first
20foundation · easy
At which point in the development workflow does Push Protection act to prevent secret exposure?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to GH-500

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by GitHub. “GH-500” is a trademark of its owner, used for identification only.