AZ-400 Configure processes and communications Practice Question
Your team uses GitHub Discussions for Q&A. You notice that many questions go unanswered. Which two actions can improve response rates? (Choose two.)
⚠ Common exam trap
Many exam-takers confuse 'closing' or 'converting' discussions with 'managing' them, but the correct approach is to improve the quality of the initial post (via templates) and ensure active monitoring (via assigned maintainers), not to remove or repurpose unanswered content.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create a template for new discussions to guide users.
Option C is correct because creating a discussion template guides users to provide complete, structured information (such as version, environment, and steps to reproduce), which makes questions easier to understand and answer, thereby improving response rates. Option D is correct because assigning a team of maintainers to monitor unanswered discussions ensures there is clear ownership and accountability for responding, directly reducing the number of questions that go unanswered. Option A is not appropriate because limiting discussions to a single category reduces organization and makes it harder for the right experts to find relevant questions. Option B is not appropriate because auto-closing unanswered discussions after 7 days would suppress legitimate questions rather than encourage answers. Option E is not appropriate because converting unanswered discussions to issues does not by itself increase response rates and may simply move the problem elsewhere.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Limit the number of discussion categories to one.
Why it's wrong here
Collapsing all discussions into a single category strips away GitHub's native grouping mechanism, because each category maps to a distinct label, a separate filtered feed, and its own notification scope. Without Q&A, announcements, and troubleshooting separated, maintainers lose the ability to quickly triage by intent and instead scan an unstructured stream, hurting response time. It also decreases discoverability, since participants cannot filter by category or subscribe only to relevant topics; the result is a chaotic dumping ground that discourages participation.
- ✗
Automatically close discussions that are unanswered for 7 days.
Why it's wrong here
Auto-closing unanswered threads after 7 days ignores actual engagement and question viability; many valid questions remain answerable beyond a fixed timer, and premature closing discourages late but useful contributions, reducing community responsiveness and creating friction for users seeking help.
- ✓
Create a template for new discussions to guide users.
Why this is correct
GitHub Discussions supports issue forms-style templates that enforce structured problem statements—such as expected behavior, reproduction steps, and screenshots—which reduces vague posts, surfaces necessary context upfront, and lets maintainers answer more efficiently, directly improving Q&A quality.
- ✓
Assign a team of maintainers to monitor unanswered discussions.
Why this is correct
Assigning specific maintainers to monitor unanswered discussions establishes clear ownership and triage responsibilities, ensuring each thread is evaluated, answered, or routed (e.g., to documentation or issues) rather than being overlooked in high-traffic repositories, thereby increasing response reliability.
- ✗
Convert unanswered discussions to issues.
Why it's wrong here
Converting discussions to issues fragments the conversation into a bug/task tracker that does not fit open-ended help threads, loses the collaborative Q&A context, and creates duplicate tracking—without addressing the root cause of unanswered posts or improving response times.
Go deeper
Related to this question
Key term
GitHub
GitHub is a cloud-based platform for storing, tracking, and collaborating on code using Git version control.
Key term
find
The find command in Unix/Linux is a powerful utility for searching files and directories based on a wide range of criteria such as name, size, type, permissions, and modification time.
About these practice questions
One of 696 original AZ-400 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-400 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-400 exam.