A company wants to track modifications to the code that is used to build new virtual servers. Which of the following will the company most likely deploy?

Question

Options

• AChange management ticketing system
• BBehavioral analyzer
• CCollaboration platform
• DVersion control tool

• B
  7% (1)
• C
  7% (1)
• D
  87% (13)

Explanation

Version control (D) is the right fit because it's purpose-built to track every change made to code or configuration files - who changed what, when, and why - which is exactly what's needed when managing infrastructure-as-code (e.g., scripts or templates used to provision virtual servers.

Why the distractors are wrong:

• A (Change management ticketing system) tracks requests and approvals for changes, not the code changes themselves - it's process-oriented, not code-oriented.
• B (Behavioral analyzer) monitors runtime activity or anomalies in systems/users, not source code history.
• C (Collaboration platform) (think Slack or Teams) facilitates communication but doesn't record or manage code revisions.

Memory tip: Think "version control = code history." Whenever a question mentions tracking modifications to code or scripts, version control (Git, SVN, etc.) is almost always the answer - it's the only tool in this list that creates a timestamped, auditable log of code changes.

No community discussion yet for this question.