Which approach best identifies credentials or tokens that could appear in code or commit messages during a repository review, while avoiding runtime checks?
An interactive method that probes application responses using crafted inputs
A container-centric assessment that detects open ports in running services
A pattern-driven inspection that parses revision history for sensitive content
A wireless-based procedure that checks for leaked identifiers on local channels
A pattern-driven inspection targets repository history to look for credential strings, tokens, and other private information committed in code. This process helps reveal unsecured data at rest. The other methods focus on application interaction, container endpoints, or wireless assessments, and do not cover static code analysis for stored secrets.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is a pattern-driven inspection?
Open an interactive chat with Bash
Why is analyzing revision history important during a repository review?
Open an interactive chat with Bash
How does a pattern-driven inspection differ from a runtime check?