GH-100 · Question #25
You need to contact GitHub Premium Support. What are valid reasons for submitting a support ticket? (Each answer presents a complete solution. Choose two.)
The correct answer is C. business impact from security issues within your organization D. outages on GitHub.com affecting core Git functionality. GitHub Premium Support is designed for business-critical and security-impacting issues, which is why C and D are correct. A security issue causing business impact (C) represents exactly the kind of urgent, high-stakes problem Premium Support exists to address. Similarly…
Question
You need to contact GitHub Premium Support. What are valid reasons for submitting a support ticket? (Each answer presents a complete solution. Choose two.)
Options
- Alicense renewal
- Bhardware setup issues or errors
- Cbusiness impact from security issues within your organization
- Doutages on GitHub.com affecting core Git functionality
How the community answered
(32 responses)- A3% (1)
- B9% (3)
- C88% (28)
Explanation
GitHub Premium Support is designed for business-critical and security-impacting issues, which is why C and D are correct. A security issue causing business impact (C) represents exactly the kind of urgent, high-stakes problem Premium Support exists to address. Similarly, outages on GitHub.com affecting core Git functionality (D) are platform-level incidents that directly disrupt development workflows and warrant premium escalation.
Why the distractors are wrong:
- A (license renewal) is an administrative/billing task handled through account management or sales - not a technical support channel.
- B (hardware setup issues) falls outside GitHub's scope entirely; they support their platform, not your local infrastructure or hardware.
Memory tip: Think "Premium = Platform problems with business consequences." If the issue is on GitHub's side (outages) or security-impacting your org, it's Premium territory. If it's billing/admin or your own hardware, look elsewhere.
Topics
Community Discussion
No community discussion yet for this question.