Microsoft GitHub Advanced Security - GH-500무료 덤프문제 풀어보기
Which of the following is NOT an action a user can take when they receive an alert from GitHub Advanced Security (GHAS)?
정답: B
What do you need to do before you can define a custom pattern for a repository?
정답: C
설명: (Fast2test 회원만 볼 수 있음)
As a repository owner, you want to receive specific notifications, including security alerts, for an individual repository. Which repository notification setting should you use?
정답: C
설명: (Fast2test 회원만 볼 수 있음)
As a contributor, you discovered a vulnerability in a repository. Where should you look for the instructions on how to report the vulnerability?
정답: C
설명: (Fast2test 회원만 볼 수 있음)
A dependency has a known vulnerability. What does the warning message include?
정답: A
설명: (Fast2test 회원만 볼 수 있음)
What YAML syntax do you use to exclude certain files from secret scanning?
정답: D
설명: (Fast2test 회원만 볼 수 있음)
Hotspot Question
You have a GitHub Enterprise Server instance named Server1 that contains multiple organizations. Server1 uses GitHub Advanced Security and has GitHub Secret Protection enabled. Repository administrators can change the secret scanning settings of their respective repository.
You discover the following issues:
- The developers at your company bypass secret scanning push protection by asking the repository administrators to temporarily disable secret scanning.
- Some security-critical secret scanning alerts are dismissed by non-
security staff without review.
You need to configure enterprise governance to meet the following requirements:
- Ensure that the repository administrators can no longer manage or
modify secret scanning.
- Ensure that dismissing secret scanning alerts requires the approval
of designated users.
What should you do for each requirement? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
You have a GitHub Enterprise Server instance named Server1 that contains multiple organizations. Server1 uses GitHub Advanced Security and has GitHub Secret Protection enabled. Repository administrators can change the secret scanning settings of their respective repository.
You discover the following issues:
- The developers at your company bypass secret scanning push protection by asking the repository administrators to temporarily disable secret scanning.
- Some security-critical secret scanning alerts are dismissed by non-
security staff without review.
You need to configure enterprise governance to meet the following requirements:
- Ensure that the repository administrators can no longer manage or
modify secret scanning.
- Ensure that dismissing secret scanning alerts requires the approval
of designated users.
What should you do for each requirement? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
정답:
Explanation:
Box 1: Prevent the repository administrators from managing secret scanning To solve this problem, you should prevent the repository administrators from managing secret scanning.
Enforces Compliance: Preventing local administrators from disabling security features stops them from creating temporary, unsafe workarounds for developers.
Centralizes Control: GitHub Enterprise Server allows enterprise or organization owners to enforce policies globally.
Maintains Security Baseline: Locking the setting ensures that
Box 2: Enable delegated alert dismissal for secret scanning
To resolve this problem, you must configure Delegated Alert Dismissal for secret scanning. This feature forces non-security users to submit a dismissal request instead of bypassing or directly closing an alert, requiring a mandatory review by authorized stakeholders.
Note:
Create Organization-Level Security Configurations
Enforcing this behavior at the organization or enterprise level ensures repository administrators cannot change or weaken these safety settings locally.
1. Navigate to the Organization Settings.
2. In the left sidebar, click Code security and select Configurations.
3. Click New configuration (or edit an existing custom configuration).
-> 4. Under the Secret scanning section, locate the dropdown for Prevent direct alert dismissals and set it to Enabled.
5. Save the configuration and Apply it to all relevant repositories across the organization.
Reference:
https://github.blog/changelog/2024-03-11-secret-scanning-and-push-protection-are-enabled-by-default-on-new-public-repositories/
https://github.blog/changelog/2025-06-03-custom-roles-can-now-review-secret-scanning-alert-dismissal-requests/
In a private repository, what minimum requirements does GitHub need to generate a dependency graph? (Each answer presents part of the solution. Choose two.)
정답: B,C
설명: (Fast2test 회원만 볼 수 있음)
What is the purpose of push protection?
정답: C
설명: (Fast2test 회원만 볼 수 있음)
Which security feature shows a vulnerable dependency in a pull request?
정답: A