An organization wants to ensure that only the 'Security Team' receives notifications for Secret Protection alerts. Where should this be configured?

In the repository's 'Webhooks' settings, add a webhook that sends alerts to the Security Team's email.

In the repository's 'Collaborators' settings, add the Security Team as a collaborator.

In the organization's 'Security' settings, under 'Secret Protection', specify the Security Team as the alert recipients.

In the 'Notifications' settings of each individual user, enable Secret Protection alerts.

What is the primary purpose of a role-based bypass policy in Secret Protection?

To grant bypass permissions to all users who hold a specific role in the organization.

To automatically resolve alerts for secrets that are determined to be false positives.

To allow specific users or teams to bypass alerts based on their membership.

To exclude certain file paths from secret scanning to reduce noise.

An organization uses a proprietary API key format that is not covered by GitHub's default patterns. How can they detect these keys in their repositories?

Use a third-party scanning tool to detect the proprietary keys.

Create a custom secret pattern that matches the proprietary API key format.

Configure an alert exclusion for the proprietary API key format.

Enable the 'detect proprietary secrets' option in the repository settings.

What actions can be performed on a custom secret pattern in Secret Protection?

Create, edit, enable, disable, and delete.

Create, enable, and disable only.

What is the key difference between a role-based bypass policy and a delegated bypass policy in Secret Protection?

Role-based policies require approval for each bypass, while delegated policies do not.

Role-based policies are configured at the organization level, while delegated policies are configured at the repository level.

Role-based policies grant bypass to entire roles, while delegated policies grant bypass to specific users or teams.

Role-based policies apply to all repositories, while delegated policies apply only to specific repositories.

GitHubAdvanced Security (GH-500)

Domain 2Objective 4

Control Access, Policies, and Customization GH-500 Practice Questions (Page 1)

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

12questions here

3free pages

6concepts

15-20%of the exam

Questions 1–5

1foundation · easy
An organization wants to ensure that only the 'Security Team' receives notifications for Secret Protection alerts. Where should this be configured?
Select an answer first
2foundation · easy
What is the primary purpose of a role-based bypass policy in Secret Protection?
Select an answer first
3foundation · easy
An organization uses a proprietary API key format that is not covered by GitHub's default patterns. How can they detect these keys in their repositories?
Select an answer first
4foundation · easy
What actions can be performed on a custom secret pattern in Secret Protection?
Select an answer first
5foundation · easy
What is the key difference between a role-based bypass policy and a delegated bypass policy in Secret Protection?
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.