Free Microsoft GH-100 Practice Exam with Questions & Answers

EMU accounts are provisioned and authenticated exclusively through your identity provider - users sign in via the IdP and cannot use or manage GitHub-native credentials.

By defining the API key as an organization secret, you centralize management and can grant access only to the subset of repositories you choose - eliminating per‑repo duplication while enforcing the desired scope.

Designing your integration to stay within GitHub’s documented rate limits—by batching requests, using conditional requests, handling 429 responses with back‑off, and monitoring the X‑RateLimit-* headers - ensures you won’t be temporarily throttled or cut off when you hit secondary limits.

GitHub Marketplace Apps come with built‑in integrations to external services - so you can plug in things like CI servers, code-quality scanners, or deployment tools without writing and maintaining custom connectors.

Before you enable team synchronization, you should clearly define how groups in your identity provider will map to GitHub teams and roles - ensuring that when the sync runs, users land in the correct teams with the right permissions.

GitHub App Installation Access Tokens are privileged to the exact permissions you grant the App - down to individual repositories - and rotate automatically, making them the recommended choice for CI/CD automation workflows that demand least‑privilege, fine‑grained access.

You can configure the enterprise policy to allow organization owners to administer the forking setting at the organization level, giving them control over how repos fork within their orgs.

You can choose to allow any user who already has access to a private or internal repo to fork it.

You can also set the policy to never allow forking of private or internal repositories across all organizations.

The GraphQL Audit Log API surfaces entries whenever repository or organization permissions are changed (“Changes permissions”).

It records when users are elevated to administrative roles (“Promotes users to admin”).

It logs alterations to a GitHub App’s granted permissions (“Changes permissions of a GitHub App”).

GitHub Actions workflows are defined and triggered within a single repository’s context, whereas GitHub Apps are installed at the organization or user level and can subscribe to events across multiple repositories.

You need a GitHub App. Marketplace integrations that listen for events like repository.created and send notifications are delivered as GitHub Apps, since they can subscribe to organization‑level webhooks without you writing custom code.