Free Microsoft GH-300 Actual Exam Questions - Question 14 Discussion
I think D and E make the most sense here. The "/fix" command in the inline chat is a direct way to ask Copilot to fix or refactor specific code snippets, so that’s definitely one. And option E sounds right because I’ve seen right-click context menus for refactoring in some editors using Copilot, so "Refactor using GitHub Copilot" fits that use case. A and B don’t feel like official features, and I’ve never heard of running a separate command line like in C for this.
Maybe A and D. Adding comments to your code is a well-known way to prompt Copilot for specific suggestions, including refactoring ideas. The "/fix" command in the inline chat (D) sounds like a direct way to request fixes or improvements, which fits with how Copilot integrates chat-like commands nowadays. The right-click options (B and E) don’t seem consistent across all environments, and I’m not sure if the gh copilot fix command (C) is an actual feature or just made up. So A and D feel like the most reliable picks here.
A, E. I agree that adding comments (A) is a good way to trigger Copilot suggestions since it guides what you want changed. For the second, E makes sense because refactoring usually comes from a right-click menu option in IDEs, and "Refactor using GitHub Copilot" sounds legit. B seems less likely since I haven’t seen that “Fix using GitHub Copilot” option pop up anywhere official. C and D don’t seem like real commands either. So yeah, A and E fit best with how Copilot works for inline refactoring suggestions.
B tbh feels like a stretch since I haven’t seen that right-click fix option widely mentioned. A and E seem much more straightforward and aligned with current Copilot features.
It’s definitely not C or D since those commands don’t exist in Copilot as far as I know. A makes sense because comments guide Copilot on what you want changed, and E fits with the usual refactoring actions available in the editor. B sounds like a close alternative, but I’ve never seen that exact menu option. So I’d go with A and E too—seems the most consistent with how Copilot interacts in the IDE.
It’s A and E for sure. Adding comments (A) helps Copilot understand what you want improved, and E matches the typical IDE context menu style for refactoring tasks. B sounds plausible but I’ve never seen a “Fix using GitHub Copilot” option in the right-click menu, so I’d rule that out. C and D don’t seem like actual commands or features in Copilot from what I know. So A and E feel like the most straightforward ways to get inline refactoring suggestions.
Maybe A and E here. Adding comments (A) is a known way to get Copilot to suggest code improvements, so that’s a solid bet. E sounds right because “Refactor using GitHub Copilot” fits with how IDE context menus usually work for code changes. I’m less sure about B since “Fix using GitHub Copilot” seems less common or maybe outdated. D and C don’t ring a bell at all, especially since I haven’t seen those commands officially documented or in the tools I use. So, A and E make the most sense given how Copilot works in practice.
I’m skeptical about C since I’ve never seen a gh copilot fix command in the CLI docs. A seems useful for prompting suggestions, and E fits as a direct refactor option—B might be less common. Thoughts on B’s availability across editors?
B imo, right-click options usually show up in context menus for quick fixes. D sounds made up since I haven’t seen any "/fix" commands officially in Copilot chat. E still looks solid for refactoring.
A imo, adding comments is the easiest way; E also seems legit for refactoring.
B/E? I’m ruling out C and D too since those commands don’t match what I’ve seen in GitHub Copilot’s official tools. A is good for getting suggestions, but B feels like a real thing too—highlight code and use a context menu to fix stuff. E is similar, just focused on refactoring. So I’d say B and E make sense as the two ways to get inline refactoring suggestions, especially if you want something quick without typing comments.
Adding comments is a classic way to get suggestions, so A sounds solid. E fits as a direct refactor option
B tbh, I’m ditching C and D right away since those commands don’t sound like official features from GitHub Copilot docs. A makes sense because comments can prompt Copilot’s suggestions, and E is the only other one that aligns with the idea of inline refactoring assistance through right-click menus. So yeah, A and E seem like the legit pair here.
Option A and E