GH-100 無料問題集「Microsoft GitHub Administration」

（A）Development environment secrets

（B）Organization secrets

（C）Environment secrets

（D）Repository secrets

（A）Delete the repository.

（B）Configure branch protection rules.

（C）Push code to non-protected branches.

（D）Manage repository settings, such as labels and GitHub Pages.

（A）outages on GitHub.com affecting core Git functionality

（B）business impact from security issues within your organization

（C）license renewal

（D）hardware setup issues or errors

（A）To define which open source packages are permitted for use as part of that repository.

（B）To provide information on an open source repository for open source collaborators and researchers that may need to report and disclose sensitive security findings to maintainers securely.

（C）To communicate corporate security and compliance policies for end users on a private repository.

（D）To prevent anyone from pushing to the repository without approval.

（A）Machine accounts are easier to audit than GitHub Apps.

（B）GitHub Apps provide a higher rate limit ceiling than using a personal access token on a machine account, when they use an install token and are owned by a GitHub Enterprise Cloud licensed enterprise.

（C）Machine accounts are required for webhook delivery.

（D）GitHub Apps are limited to a single repository.

（A）Define the secrets in the reusable workflow's repository and reference the secret using the 'secrets' context.

（B）Use environment variables to pass data directly to the reusable workflow.

（C）Define inputs in the reusable workflow and pass values from the calling workflow.

（D）Define the secrets in the caller repository and call the reusable workflow using the 'secrets' keyword.

（A）Billing is based on total users in the enterprise that are not dormant

（B）Billing is based on owners and members of GitHub organizations

（C）Billing is based on the number of users created in Azure AD

（D）Billing is based on number of total users in the enterprise