Identify the category from behaviour, not the product name

short · 35 min · Objective 5.5

Task

The exam is vendor-neutral, so the skill is recognising what job a described tool is doing. Build the mapping yourself from descriptions rather than from product names.

Steps

  1. Write ten tool DESCRIPTIONS into lab/tools/descriptions.md, with no product names -- for example 'connects over SSH with no agent installed and enforces package versions from a YAML file'.
  2. Include at least one description each for: container orchestration, configuration management, CI/CD, infrastructure as code, source control, artefact registry, observability and secrets management.
  3. In lab/tools/mapping.csv, record description_number,category,distinguishing_property,example_product.
  4. For the configuration-management entries, state whether the description is agentless and push-based or agent-based and pull-based, and name a product matching each.
  5. Add a final row for a tool you have never used, described only by behaviour, and answer it from the category alone.

Verify

awk -F, 'NR>1 && NF>=4 {n++} END {print n" description(s) classified"}' lab/tools/mapping.csv
awk -F, 'NR>1 {print tolower($2)}' lab/tools/mapping.csv | sort -u | wc -l
grep -Eci 'agentless' lab/tools/mapping.csv
grep -Eci 'pull' lab/tools/mapping.csv

Ten classified and at least eight distinct categories. The agentless/pull distinction must appear -- it is the property that separates the named configuration-management tools from each other.

This is an independent study companion for CompTIA Cloud+ CV0-004 and is not produced by or endorsed by CompTIA.