GH-500 無料問題集「Microsoft GitHub Advanced Security」

（A）Secret validation

（B）Non-provider patterns

（C）Push protection

（D）Custom pattern dry runs

（A）As soon as a pull request is opened by a contributor

（B）When a pull request adding a vulnerable dependency is opened

（C）When Dependabot opens a pull request to update a vulnerable dependency

（D）As soon as a vulnerable dependency is detected

（A）A list of repositories to scan

（B）Additional match requirements for the secret format

（C）The secret format

（D）The name of the pattern

（A）The security impact of these changes

（B）How many projects use these components

（C）A brief description of the vulnerability

（D）An easily understandable visualization of dependency change

（A）3

（B）1

（C）4

（D）2

（A）Change the repository visibility to Internal

（B）Specify additional match criteria

（C）Enable secret scanning

（D）Close other secret scanning alerts

（A）Process alerts

（B）Upload scan results

（C）Analyze code

（D）Write queries

（E）Install the CLI

（A）Dependencies parsed from a repository's manifest and lock files.

（B）A summary of the dependencies used in your organization's repositories.

（C）Dependencies from all your repositories.

（D）Annotated code scanning alerts from your repository's dependencies.