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

（A）Repository administrators can view Dependabot alerts.

（B）GitHub performs a read-only analysis on the repository.

（C）Dependency review, secret scanning, and code scanning are enabled.

（D）Your team is subscribed to security alerts.

（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）Enable system for cross-domain identity management (SCIM) provisioning for the enterprise.

（B）Dismiss alerts that are older than 90 days.

（C）Configure a webhook to monitor for secret scanning alert events.

（D）Document alternatives to storing secrets in the source code.

（A）Ignore

（B）Participating and @mentions

（C）Custom

（D）All Activity

（A）Exploit Prediction Scoring System (EPSS)

（B）Common Weakness Enumeration (CWE)

（C）Vulnerability Exploitability exchange (VEX)

（D）Common Vulnerabilities and Exposures (CVE)

（A）When the pull request checks are successful

（B）When Dependabot creates a pull request to update dependencies

（C）When you dismiss the Dependabot alert

（D）When you merge a pull request that contains a security update

（A）It notifies the repository administrators about the new alert.

（B）It consults with a security service and conducts a thorough vulnerability review.

（C）It generates a Dependabot alert and displays it on the Security tab for the repository.

（D）It generates Dependabot alerts by default for all private repositories.

（A）It notifies the service provider who issued the secret.

（B）It scans the contents of the commits for additional secrets.

（C）It displays a public alert in the Security tab of the repository.

（D）It sends a notification to repository members.