According to the Cisco Business Architecture methodology, to what do you map business capabilities?

Question

Options

• Asolutions maturity
• Btechnical solutions
• Cbusiness solutions
• Dfinancial outcomes

• A
  6% (2)
• B
  3% (1)
• C
  91% (32)

Explanation

In Cisco's Business Architecture methodology, business capabilities are mapped to business solutions because the framework works by aligning what a business needs to do (capabilities) with the solutions that fulfill those needs at the business level - before technical implementation is considered. This keeps the architecture conversation grounded in business value rather than technology.

Why the distractors are wrong:

• A (solutions maturity): Maturity models assess how well solutions are implemented, not what capabilities map to.
• B (technical solutions): Technical solutions come after business solutions are defined; jumping straight to technology skips the business-alignment layer the methodology is designed to enforce.
• D (financial outcomes): Financial outcomes are a result of good architecture decisions, not the mapping target for capabilities.

Memory tip: Think of the acronym CAP → BIZ: Capabilities map to Business solutions first. The word "business" appears in both "business capabilities" and "business solutions" - they belong together at the same layer of the architecture.

No community discussion yet for this question.