Free Microsoft GH-900 Actual Exam Questions - Question 3 Discussion

Question No. 3
An employee needs to find all issues within organization “Avocado" containing text "404 error" and a
"guacamole" label. Which of the following steps would be best to search for these results?
Select one option, then reveal solution.
US
SB
Shoaib B.
2026-02-19

C imo. It covers the entire org with org:Avocado, filters by label:guacamole, and searches for "404 error" in the text. Then selecting "Issues" ensures you only see issue results. A has is:issue which might be redundant if you filter by issues afterward, and B only looks at one repo’s issues, not the whole org. D is about settings, not searching. So C feels like a cleaner way to combine all criteria across the org.

0
SB
Shoaib B.
2026-02-17

Maybe C works best because it specifically includes the label and text in the query and then filters to issues, which should cover all repos in the Avocado org. A includes “is:issue” but I’m not totally sure if that’s needed or if it might narrow things unnecessarily. B looks too limited since it only checks one repo, and D is about settings, not searching. So C seems like the most straightforward way to get all issues with that label and text across the whole organization.

0
LT
Luke T.
2026-01-30

B tbh. Filtering issues by label directly in the org’s repo view feels more straightforward and less reliant on tricky search syntax that might not work across all repos. You get a clear list of relevant issues without guessing if the search query covers everything. Plus, it’s easier to confirm you’re in the right place when you can visually see the filter applied. The search bar queries can be hit or miss depending on how the platform handles org-wide searches, so this method is a safer bet overall.

0
LT
Luke T.
2026-01-25

C imo. It’s similar to A but without is:issue, which might not work org-wide. Plus, C explicitly says to filter by Issues after searching, so you’re sure you’re looking at the right results. That should find all issues across the org with the label and text without relying on if is:issue works at the org level. D and B seem off since D is about settings, not searching, and B limits you to one repo's issues, not all org repos.

0
RL
Ryan L.
2026-01-12

A looks best since it includes org, issue, label, and text search all in one query. B and D seem too manual or unrelated. C misses is:issue so might not filter properly. I’d go with A.

0