GH-500 Exam Dumps : GitHub Advanced Security Exam

Validity checks — where GitHub verifies if a secret is still active — are available for partner patterns only. These are secrets issued by GitHub's trusted partners (like AWS, Slack, etc.) and have APIs for GitHub to validate token activity status.

Custom patterns and high entropy patterns do not support automated validity checks.

GitHub Actions supports path filters for events such as push and pull_request. The paths: key allows a workflow to run only when changed files match one or more specified path patterns. For example, a workflow could use paths: - 'src/**' so that a code scanning job runs when files under the src directory are changed. The related paths-ignore: key performs the opposite function by excluding matching paths. Characters such as ** are glob-pattern components placed beneath paths:; they are not replacements for the paths keyword itself. Therefore, because the workflow must conditionally run when files in a particular directory change, line 3 should contain paths: followed by the applicable directory pattern.

Dependency review and secret scanning are capabilities associated with GitHub Advanced Security. In GitHub's current product structure, dependency review is included with GitHub Code Security, while secret scanning is a central capability of GitHub Secret Protection. Both products are components of the broader GitHub Advanced Security offering, and legacy GHAS licenses can include the combined capabilities. The dependency graph is an important supply-chain feature and provides the underlying dependency inventory, but it is broadly available beyond the licensed GHAS feature set and is enabled by default for public repositories. A repository security policy, normally provided through SECURITY.md, is also a general repository capability rather than one of the licensed Advanced Security features being tested. Therefore, dependency review and secret scanning are the correct selections.