Manage and Respond to Secret Protection Alerts GH-500 Practice Questions (Page 1)

Questions 1–5

1. 1foundation · easy

   What is the recommended way to handle a Secret Protection alert that is a false positive?

   • ADismiss the alert with the reason 'used in tests' or 'false positive'
   • BDelete the secret from the repository
   • CResolve the alert by revoking the secret
   • DIgnore the alert without any action
   Reveal Solution Discussion Select an answer first
2. 2expert · hard

   A Secret Protection alert flags a production database password in a private repository. The password is used by a legacy application that cannot be easily reconfigured. The team wants to minimize downtime while addressing the exposure. What is the best approach?

   • ADismiss the alert because the repository is private and the exposure is limited.
   • BRotate the password, update the legacy application configuration, and then resolve the alert.
   • CRemove the password from the repository and commit the change, then resolve the alert.
   • DChange the repository to public to alert more users about the exposure.
   Reveal Solution Discussion Select an answer first
4. 3application · medium

   A Secret Protection alert is dismissed as a false positive by a developer. Later, the security team discovers the secret was actually valid and had been exposed. What should the team do to address the alert?

   • AReopen the alert and proceed with remediation, such as rotating the secret.
   • BDelete the dismissed alert from the alert list.
   • CCreate a new alert manually to track the exposure.
   • DLeave the alert dismissed because the developer already made a decision.
   Reveal Solution Discussion Select an answer first
5. 4application · medium

   A Secret Protection alert is currently 'open'. The security team has verified the secret is valid and has rotated it in the credential store. What should be done to the alert to reflect the remediation?

   • AResolve the alert after confirming the exposed secret is no longer valid.
   • BLeave the alert open until the repository history is rewritten.
   • CDismiss the alert as a false positive because the secret was rotated.
   • DReopen the alert after rotation to track the new secret.
   Reveal Solution Discussion Select an answer first
6. 5application · medium

   A security analyst is triaging a Secret Protection alert for a GitHub personal access token. The token is listed as 'expired' in the token registry. What is the appropriate action?

   • ALeave the alert open until the token is removed from the repository.
   • BResolve the alert because the token is no longer valid.
   • CRevoke the token even though it is expired.
   • DDismiss the alert as a false positive because the token is expired.
   Reveal Solution Discussion Select an answer first