CTO Technology Roadmap & Planning 5

Question 1

A CTO is using OKRs to anchor the technology roadmap. Which is the BEST example of a well-formed technology Key Result?

Accepted Answer

Reduce API response time from 800ms to 200ms by Q3, enabling the product team to launch real-time features

Answer

A strong Key Result is specific, measurable, time-bound, and directly tied to a business or product outcome.

Question 2

Which stakeholder group is MOST likely to require a roadmap view focused on system reliability, uptime SLAs, and disaster recovery timelines?

Accepted Answer

Enterprise customers and operations leadership

Answer

Operations leadership and enterprise customers care most about reliability commitments, SLAs, and business continuity planning.

Question 3

What is the MOST effective way for a CTO to manage stakeholder expectations when a major roadmap milestone is at risk of slipping?

Accepted Answer

Proactively communicate the risk early, provide root cause analysis, and present revised timeline options with trade-offs

Answer

Early, transparent communication about risks with options and trade-offs preserves trust and gives stakeholders time to adjust plans.

Question 4

A CTO wants to introduce a formal 'buy vs. build vs. partner' framework into roadmap planning. What is the PRIMARY benefit of this approach?

Accepted Answer

It creates a structured evaluation process that optimizes for cost, speed, and strategic differentiation

Answer

A buy/build/partner framework forces deliberate evaluation of how to source each capability based on strategic value and economics.

Question 5

When sequencing items on a technology roadmap, which dependency type MOST commonly causes cascading delays?

Accepted Answer

Resource dependencies where multiple initiatives share the same team or infrastructure

Answer

Resource contention creates hard blockers — if a shared team or platform is delayed, every downstream initiative waiting on it slips too.

(CTO) Certified Chief Technology Officer Practice Test