When comparing fine-grained Personal Access Tokens (PATs) with classic PATs, which of the following statements is accurate?

Question

Options

• AFine-grained PATs automatically renew while classic PATs require manual renewal.
• BFine-grained PATs permissions can be scoped to specific repositories.
• CClassic PATs offer more permission controls than fine-grained PATs.
• DClassic PATs can be restricted to specific organizations, but fine-grained PATs cannot.

• B
  91% (20)
• C
  5% (1)
• D
  5% (1)

Explanation

Fine-grained PATs were specifically designed to allow repository-level scoping, meaning you can limit a token's access to one or more specific repositories rather than all repositories the account can access - this is a core design advantage over classic PATs, making B correct.

Why the distractors are wrong:

• A is false: neither PAT type auto-renews. Fine-grained PATs can have expiration dates (and GitHub encourages setting them), but renewal is always manual for both.
• C is the opposite of reality. Fine-grained PATs offer more granular permissions (read vs. write per resource type like issues, pull requests, actions, etc.), while classic PATs use broad scopes like repo or admin:org.
• D reverses the truth. Fine-grained PATs require selecting a specific owner (a user or organization), and organizations can enforce approval policies. Classic PATs have no built-in org-restriction mechanism.

Memory tip: Think of "fine-grained" like a fine-tipped tool - it gives you more precision and control, not less. If you remember that fine-grained = more targeted/scoped, you can eliminate C and D immediately, and since expiration ≠ auto-renewal, A falls away too.

No community discussion yet for this question.