A security manager has just authored a new custom secret scanning pattern at the organisation level and wants to understand the impact before any developer sees an alert. They run the pattern as a dry run across the selected repositories. What does the dry run produce, and what state is the pattern in afterwards?
- AIt scans the default branch only and immediately opens alerts there, while leaving non-default branches untouched until the pattern is formally published.
- BIt returns a sample of matches for the author to review without creating alerts, and the pattern remains unpublished until the author explicitly publishes it. Correct
- CIt publishes the pattern in a monitor-only mode that records matches silently for thirty days before alerts and push protection switch on automatically.
- DIt creates alerts but marks every one as resolved as a false positive, so the author can reopen the genuine matches and discard the noise.
Why A is wrong: A dry run deliberately creates no alerts at all, so describing it as opening alerts on the default branch contradicts its purpose. The default-versus-other-branch detail is a plausible distraction but the premise that alerts appear is wrong.
Why B is correct: A dry run evaluates the pattern against repository contents and shows the author a set of results so they can judge precision, but it raises no alerts and notifies no one. The pattern stays in a draft, unpublished state, letting the author refine the expression before publishing creates real alerts.
Why C is wrong: There is no timed monitor-only mode that auto-promotes a custom pattern after a fixed window. This invents a lifecycle that does not exist; publishing and any push protection are explicit author decisions, not scheduled transitions.
Why D is wrong: A dry run does not create alerts in any state, resolved or otherwise, so there is nothing to reopen. The idea of pre-resolved alerts sounds like a tidy review workflow but misrepresents what a dry run does.