Skip to content

GH-100 · Domain 2: Administer GitHub Enterprise environment · 14% of the exam

Task 2.3: Manage deployment and licensing

Choosing between GitHub Enterprise Cloud with managed users or personal accounts, with data residency, and GitHub Enterprise Server, how licences and billing work, and who consumes a seat.

Study it

  • GitHub Enterprise Cloud with managed users, data residency or personal accounts, and GitHub Enterprise Server

    Lesson coming

  • Licences, billing and who consumes a seat

    Lesson coming

Sample questions

Try each one before opening the answer. Every option is explained, with the GitHub documentation page that proves it.

Question 1 · choose 1

A company runs GitHub Enterprise Server 3.22 in production and keeps a staging instance that mirrors it. The administrators want to try the next feature release before it is generally available, and then move production to it. Which plan follows GitHub's guidance?

  1. AUpgrade staging to the release candidate, then upgrade staging and production to the generally available release
  2. BTurn on automatic updates so that production installs the feature release when it ships
  3. CWait for GitHub to upgrade production in a maintenance window after the release ships
  4. DInstall the release candidate in a new test environment, destroy it after testing, then upgrade production to the release
Show the answer and why
  • AUpgrade staging to the release candidate, then upgrade staging and production to the generally available release

    Incorrect

    Don't upgrade a supported version to a release candidate, or a release candidate to later versions.

  • BTurn on automatic updates so that production installs the feature release when it ships

    Incorrect

    Automatic updates apply eligible hotpatches; they don't replace planned full upgrades.

  • CWait for GitHub to upgrade production in a maintenance window after the release ships

    Incorrect

    Administrators are responsible for keeping their own instance up to date.

  • DInstall the release candidate in a new test environment, destroy it after testing, then upgrade production to the release

    Correct

    Release candidates belong only in test environments, which are destroyed rather than upgraded.

GitHub Enterprise Server is self-hosted, and its administrators keep it up to date. Feature releases start with release candidates, which must not be installed in production, upgraded to from a supported version, or upgraded from to later versions; install a candidate in a new test environment and destroy it afterwards. Automatic updates can apply eligible hotpatches but don't replace planned full upgrades.

Question 2 · choose 1

A company's 800 developers each have an account on GitHub Enterprise Cloud and on its GitHub Enterprise Server 3.22 instance, and each should consume a single license. License usage has never been synced between the two. On Enterprise Server, 650 developers have a primary email that is a verified email of their Enterprise Cloud account; the other 150 use an old domain on Enterprise Server that isn't on their Enterprise Cloud accounts. The company uses no SAML or SCIM. What makes all 800 consume one license each?

  1. ASync license usage from Enterprise Server to Enterprise Cloud; all 800 are then counted once
  2. BHave the 150 add their old-domain address as a verified email on Enterprise Cloud, with no license sync needed for them
  3. CSync license usage, and have the 150 add their Enterprise Server email as a verified email on Enterprise Cloud
  4. DSync license usage, and give the 150 the same username on both deployments
Show the answer and why
  • ASync license usage from Enterprise Server to Enterprise Cloud; all 800 are then counted once

    Incorrect

    After a sync, accounts are matched by email, so the 150 with unmatched addresses still consume two licenses.

  • BHave the 150 add their old-domain address as a verified email on Enterprise Cloud, with no license sync needed for them

    Incorrect

    Without a license sync, users of both deployments aren't matched at all.

  • CSync license usage, and have the 150 add their Enterprise Server email as a verified email on Enterprise Cloud

    Correct

    The sync matches each Enterprise Server primary email with a verified email on Enterprise Cloud, which then holds for all 800.

  • DSync license usage, and give the 150 the same username on both deployments

    Incorrect

    Matching after a sync uses email addresses, not usernames.

For each user to consume a single license across deployments, license usage must be synced from GitHub Enterprise Server to GitHub Enterprise Cloud. After the sync, GitHub matches accounts by email: without SAML or SCIM identities, it compares the primary email address of each Enterprise Server user with the verified email addresses of Enterprise Cloud accounts. Users whose addresses don't match keep consuming a license in each deployment, so the troubleshooting fix is to make the same email address appear on both accounts and run the sync again.

Question 3 · choose 2

A company pays for GitHub Enterprise by invoice under a volume agreement that includes Visual Studio subscriptions with GitHub Enterprise, and it also runs a GitHub Enterprise Server instance. It is considering usage-based billing for licenses. Which two statements are true? (Choose TWO.)

  1. AIt moves to usage-based billing by itself at the start of its next billing cycle
  2. BIts volume agreement keeps billing until it expires, with the option to switch at renewal
  3. CAfter the switch, users who exist only on Enterprise Server consume no license at all
  4. DWith usage-based billing, users should be added to Enterprise Server before Enterprise Cloud
  5. EBundled Visual Studio licenses stay on a volume agreement
Show the answer and why
  • AIt moves to usage-based billing by itself at the start of its next billing cycle

    Incorrect

    Volume agreements continue until they expire, and a Visual Studio bundle switches through the account manager or Sales.

  • BIts volume agreement keeps billing until it expires, with the option to switch at renewal

    Correct

    Invoiced volume, subscription or prepaid agreements keep that billing until they expire.

  • CAfter the switch, users who exist only on Enterprise Server consume no license at all

    Incorrect

    Users who are only on GitHub Enterprise Server consume a GitHub Enterprise license once you switch.

  • DWith usage-based billing, users should be added to Enterprise Server before Enterprise Cloud

    Incorrect

    Usage-based licensing is cloud-first: users must first be added to an organization on GitHub Enterprise Cloud.

  • EBundled Visual Studio licenses stay on a volume agreement

    Correct

    Bundled licenses remain on a volume agreement; usage-based billing applies to the non-bundled licenses.

Usage-based billing charges each month for the licenses actually consumed. Customers who pay by invoice under a volume, subscription or prepaid agreement keep that billing until the agreement expires and can switch at renewal. With a Visual Studio bundle, only non-bundled licenses move to usage-based billing. The model is cloud-first, so users should be on GitHub Enterprise Cloud before they are added to GitHub Enterprise Server.

Question 4 · choose 1

A company runs GitHub Enterprise Server 3.22. Its administrators want scheduled backups configured from the Management Console, without running backup software on a separate host. What should they use?

  1. AA high availability replica, which serves as the backup
  2. BThe GitHub Enterprise Server Backup Utilities on a dedicated host
  3. CBackups that GitHub takes of the instance automatically
  4. DThe built-in GitHub Enterprise Server Backup Service
Show the answer and why
  • AA high availability replica, which serves as the backup

    Incorrect

    A replica isn't a replacement for backups, because corruption on the primary is replicated.

  • BThe GitHub Enterprise Server Backup Utilities on a dedicated host

    Incorrect

    The legacy backup utilities need a separate host, which the team wants to avoid.

  • CBackups that GitHub takes of the instance automatically

    Incorrect

    The instance is self-hosted, and its administrators configure its backups.

  • DThe built-in GitHub Enterprise Server Backup Service

    Correct

    The Backup Service is built in, configured in the Management Console, and needs no separate host.

The GitHub Enterprise Server Backup Service is a managed backup solution built into the instance. It is configured from the Management Console, doesn't require a separate host for backup software, and stores backups on a dedicated storage volume. A high availability replica complements backups but doesn't replace them.

Question 5 · choose 1

An enterprise with usage-based billing for GitHub Enterprise licenses downloads a new license file for its GitHub Enterprise Server instance. How is the seat count in that license file set?

  1. AIt is the number of licenses in the original volume purchase
  2. BIt is the number of consumed Cloud licenses when the file was generated
  3. CIt is unlimited, because usage-based billing removes the seat count
  4. DIt is the number of users who signed in to the instance during the last 30 days
Show the answer and why
  • AIt is the number of licenses in the original volume purchase

    Incorrect

    With metered billing the count comes from consumed licenses, not a purchase.

  • BIt is the number of consumed Cloud licenses when the file was generated

    Correct

    With usage-based billing, the seat count reflects consumed Cloud licenses at generation.

  • CIt is unlimited, because usage-based billing removes the seat count

    Incorrect

    A license file still controls how many people can use the instance.

  • DIt is the number of users who signed in to the instance during the last 30 days

    Incorrect

    The count is based on Cloud consumption at generation time.

A GitHub Enterprise Server license file has an expiration date and controls the number of people who can use the instance. If the enterprise uses metered, usage-based billing, the seat count in the file is the number of consumed Cloud licenses at the time the license was generated.

Question 6 · choose 1

In an enterprise with managed users, a developer has a Visual Studio subscription with GitHub Enterprise, but her account still consumes a regular GitHub Enterprise license instead of the bundled one. What should the administrator check?

  1. AThat her Visual Studio UPN matches her SCIM userName or her linked identity's email
  2. BThat she has verified a personal email address on GitHub
  3. CThat she has signed in to GitHub Enterprise Server at least once
  4. DThat an owner has added a support entitlement to her account
Show the answer and why
  • AThat her Visual Studio UPN matches her SCIM userName or her linked identity's email

    Correct

    With managed users, the Visual Studio UPN must match the SCIM userName or linked identity email.

  • BThat she has verified a personal email address on GitHub

    Incorrect

    Managed user accounts are matched through SCIM or the linked identity, not a personal email.

  • CThat she has signed in to GitHub Enterprise Server at least once

    Incorrect

    Server sign-ins don't decide whether a Cloud account matches a subscription.

  • DThat an owner has added a support entitlement to her account

    Incorrect

    Support entitlements don't affect license matching.

A Visual Studio subscriber consumes a bundled license when the subscriber's User Principal Name (UPN) matches the account. For personal accounts the match is a verified email address; with Enterprise Managed Users the UPN must match the SCIM userName attribute or the email address from the linked identity.

Practice domain 2 →Practice all domains →