It aligns with Microsoft’s convention for placeholders in Copilot-related tools (e.g., Copilot Studio uses [topic]).
It fits the promptbook workflow where users input values into defined fields, requiring a distinct, parseable format.
It’s consistent with KQL and Sentinel integration (Copilot uses the Sentinel plugin), where brackets denote parameters or fields.
Alternatives like < >, ## ##, or $ $ lack support in this context and Microsoft’s AI prompt patterns.
After reviewing the documentation, C. [IncidentID] remains the strongest choice:
It aligns with Microsoft’s convention for placeholders in Copilot-related tools (e.g., Copilot Studio uses [topic]).
It fits the promptbook workflow where users input values into defined fields, requiring a distinct, parseable format.
It’s consistent with KQL and Sentinel integration (Copilot uses the Sentinel plugin), where brackets denote parameters or fields.
Alternatives like < >, ## ##, or $ $ lack support in this context and Microsoft’s AI prompt patterns.
I do not think the formatting should be blank, according to gpt and copilot it's C. I am not sure about this one.
upvoted 1 times
...
This section is not available anymore. Please use the main Exam Page.SC-200 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Optimizor_IT
1Â month ago54c341a
2Â months agoSelimG
2Â months agoOptimizor_IT
1Â month agoSelimG
2Â months ago