Practice Repository Management Questions Now

Start a timed practice session focusing on Repository Administration topics from the GH-ADMIN question bank.

GH-ADMIN Repository Management Question Bank (7 Questions)

Browse all 7 practice questions covering Repository Administration for the GH-ADMIN certification exam. Each question includes the full answer and a detailed explanation to help you understand the concepts.

Question 1Enable Secure Development and Compliance
What happens when a GitHub repository is archived?
AThe repository is permanently deleted after 30 days
BThe repository becomes read-only; issues, PRs, and pushes are disabled✓
CThe repository is moved to GitHub's long-term cold storage
DThe repository is hidden from search but still writable by collaborators
Show Answer & Explanation
Correct Answer: B
Explanation:
Archiving a repository makes it read-only. The code, issues, and PRs are preserved but no new changes can be made.
Question 2Manage GitHub at Scale
What is the purpose of repository templates in GitHub?
ACode formatting
BCreate new repositories with pre-configured files, directory structure, and settings as a starting point✓
CWorkflow templates
DIssue templates only
Show Answer & Explanation
Correct Answer: B
Explanation:
Repository templates allow creating new repositories pre-populated with files, directories, and configurations, ensuring consistent project setup across an organization.
Question 3Manage GitHub at Scale
What are repository rulesets?
AOld branch protections
BFlexible, layered rule enforcement for branches and tags across repositories or organization-wide, with bypass permissions and status check requirements✓
CRepository settings
DAction restrictions only
Show Answer & Explanation
Correct Answer: B
Explanation:
Rulesets: successor to branch protection rules. Support: organization-wide application, multiple rulesets per branch, bypass actors, creation/update/deletion restrictions, status checks, commit signing, and merge requirements. More flexible and scalable.
Question 4Manage GitHub at Scale
How do you implement a repository template strategy?
AOne template for all
BCreate template repositories for different project types (API, frontend, library), including CI/CD workflows, linting configs, README templates, and security policies✓
CNo templates needed
DUse forks instead
Show Answer & Explanation
Correct Answer: B
Explanation:
Template strategy: create per-type templates (Node API, React app, Python package) with: .github/workflows, linting config, README template, CODEOWNERS, security policy, .gitignore, and devcontainer.json — standardizing project creation.
Question 5Manage GitHub at Scale
What are repository templates and their governance benefits?
ANo governance benefit
BStandardized starting points that ensure all new repositories include required files (LICENSE, SECURITY.md, CODEOWNERS, CI workflows) and configurations for organizational compliance✓
CPersonal preference only
DOnly for documentation
Show Answer & Explanation
Correct Answer: B
Explanation:
Template governance: include required files (README template, LICENSE, CONTRIBUTING.md, SECURITY.md, CODEOWNERS, .github/workflows/ci.yml, .gitignore). Benefits: consistent standards, security-by-default (CI/CD, code scanning), compliance (license, security policy), and reduced onboarding time. Org policy: recommend or require template use for new repos. Automation: probot or GitHub App to check new repos against standards.
Question 6Manage Repository Security
What are repository rulesets at the org level?
AOnly repo-level
BOrganization-wide rulesets that apply branch/tag protection rules across multiple repositories simultaneously, with bypass permissions and enforcement status for consistent governance✓
CCannot apply at org level
DOnly for branches
Show Answer & Explanation
Correct Answer: B
Explanation:
Org rulesets: org Settings > Rulesets. Target: repos by name pattern (include/exclude), branches, and tags. Rules: require PR, require reviews, require status checks, block force push, require signatures, restrict creation/deletion. Bypass: teams, roles, or GitHub Apps. Enforcement: Active (enforce), Evaluate (audit mode — see what would be enforced), Disabled. Benefits: centralized governance without configuring each repo individually.
Question 7Manage GitHub at Scale
What are repository templates?
AJust forks
BRepositories marked as templates that allow creating new repos with the same directory structure, files, and branches — useful for standardized project scaffolding with CI/CD, configs, and documentation✓
CSame as cloning
DOnly for GitHub Pages
Show Answer & Explanation
Correct Answer: B
Explanation:
Templates: Settings > Template repository checkbox. Create from: 'Use this template' button → new repo with same files (not same git history). Include: all branches (optional), directory structure, workflow files, configuration, and documentation. Use for: organization standards (CI/CD template, security config, CODEOWNERS, issue templates), microservice starter, and consistent project structure. Not included: git history, contributors, stars, and watchers. Alternative: GitHub CLI 'gh repo create --template'.

Key Repository Management Concepts for GH-ADMIN

repositorybranch protectionrulesetswebhookstemplatearchive

GH-ADMIN Repository Management Exam Tips

Repository Administration questions in GH-ADMIN are typically scenario-based. Focus on service-level decision making aligned to official exam objectives. Priority concepts: repository, branch protection, rulesets, webhooks, template, archive.

What GH-ADMIN Expects

Anchor your answer in select the most practical, secure, and scalable answer for the stated scenario.
Repository Management scenarios for GH-ADMIN are frequently mapped to Domain 2 (20%), so read the objective carefully before picking controls or architecture.
Expect multi-service scenarios where Repository Management interacts with IAM, networking, storage, or observability patterns rather than appearing as an isolated service question.
When two options are both technically valid, prefer the choice that best aligns with the exam's operational scope (Intermediate) and managed-service best practices.

High-Value Repository Management Concepts

Know the core Repository Management building blocks cold: repository, branch protection, rulesets, webhooks.
Review the edge-case features and limits for template, archive; these details are commonly used to differentiate answer choices.
Practice service-integration reasoning: how Repository Management pairs with Organization Management, Security in real deployment patterns.
For GH-ADMIN, explain why the chosen Repository Management design meets reliability, security, and cost expectations better than the alternatives.

Common GH-ADMIN Traps

Watch for answers that partially solve the requirement but miss operational constraints.
Questions in Manage User Identities and Access often include distractors that look correct for Repository Management but violate least-privilege, durability, or availability requirements.
Avoid picking options purely by feature name; validate data path, failure handling, and governance impact before answering.
If the prompt hints at automation or repeatability, eliminate manual-only operational answers first.

Fast Review Checklist

Can you compare at least two Repository Management implementation paths and justify which one best fits the scenario?
Can you map the chosen answer back to Manage User Identities and Access (20%) outcomes for GH-ADMIN?
Can you explain security and access boundaries for Repository Management without relying on default-open assumptions?
Can you describe how Repository Management integrates with Organization Management and Security during failure, scaling, and monitoring events?

Exam Domains Covering Repository Management

Domain 2Manage User Identities and Access20%

Related Resources

🎯 Free GH-ADMIN Mock Exam 📝 Organization Management Questions 📝 Security Questions

More GH-ADMIN Study Resources

← GH-ADMIN Study Hub 30-Day Study Plan Full Practice Exam

📦 Repository Administration - GH-ADMIN Practice Questions