GitHub Professional Certificate GitHub Packages and Container Registry 2

Question 1

In a GitHub Actions workflow, which built-in secret should be used to authenticate with GitHub Packages?

Accepted Answer

secrets.GITHUB_TOKEN

Answer

secrets.GITHUB_PAT

Answer

secrets.PACKAGES_TOKEN

Answer

secrets.REGISTRY_PASSWORD

Question 2

What GitHub Actions step snippet correctly authenticates Docker with GHCR using the built-in token?

Accepted Answer

uses: docker/login-action@v3 with registry: ghcr.io, username: ${{ github.actor }}, password: ${{ secrets.GITHUB_TOKEN }}

Answer

run: docker login ghcr.io --username actions --password auto

Answer

uses: actions/setup-docker@v1 with token: ${{ secrets.GITHUB_TOKEN }}

Answer

run: gh auth configure-docker ghcr.io

Question 3

How can you link a container image published to GHCR to a specific GitHub repository?

Accepted Answer

By adding an org.opencontainers.image.source label in the Dockerfile pointing to the repository URL

Answer

By naming the image identically to the repository

Answer

By creating a package.json in the repository root

Answer

By enabling the 'Link Package' option in repository settings

Question 4

Which GitHub permission level is required for a user to delete a package version from GitHub Packages?

Accepted Answer

Admin access to the repository or organization

Answer

Read access to the repository

Answer

Write access to the repository

Answer

Any authenticated GitHub user

Question 5

What is the key difference between GitHub Packages (docker.pkg.github.com) and GitHub Container Registry (ghcr.io)?

Accepted Answer

GHCR is independent of repository permissions and supports granular access control; the older registry ties packages to repository access

Answer

GHCR supports only public images; GitHub Packages supports private images

Answer

GitHub Packages supports OCI artifacts; GHCR only supports Docker images

Answer

There is no functional difference; they use different domain names only

Question 6

How do you configure a Maven pom.xml to publish artifacts to GitHub Packages?

Accepted Answer

Add a block under with the GitHub Packages URL https://maven.pkg.github.com/OWNER/REPO

Answer

Set the MAVEN_REGISTRY environment variable to github.com

Answer

Add a <plugin> for github-packages-maven-plugin in the build section

Answer

Use mvn github:deploy instead of mvn deploy

Question 7

What happens to packages in GitHub Packages when a repository is deleted?

Accepted Answer

Packages are scheduled for deletion along with the repository

Answer

Packages are automatically transferred to the organization

Answer

Packages remain available at their original URLs indefinitely

Answer

Packages become public after 30 days