CAPM Practice: Demonstrate an understanding of product roadmaps

The features/capabilities distinction enables appropriate communication depth. Customer-facing roadmaps may show 'Mobile ordering capability' (broad), while internal planning details the specific features (redesigned cart, saved addresses, Apple Pay) that comprise that capability — matching communication depth to audience needs.

**Why not B:** Denying the distinction between features and capabilities ignores a well-established product management practice. Features are specific, implementable functions (e.g., "export to PDF"), while capabilities represent broader business outcomes enabled by groups of features (e.g., "reporting and analytics"). This distinction is critical for tailoring communication to different audiences.

**Why not C:** Capabilities and features are not exclusive to specific roadmap types. Both concepts appear in product roadmaps and technology roadmaps alike. The distinction is about granularity and audience, not about which type of roadmap they belong to.

**Why not D:** While the definitions of features and capabilities in this choice are partially accurate, the claim that both appear identically on all roadmaps is incorrect. A key strategic practice is showing capabilities externally (to customers and partners) for simplicity and competitive protection, while showing detailed features internally (to development and product teams) for execution planning.