CTO Digital Product Development 5 — Questions and Answers
Question 1: A CTO is evaluating whether to implement a 'strangler fig' pattern. In what scenario is this pattern most applicable?
- Launching a greenfield product with no legacy constraints
- Incrementally replacing a legacy monolith by routing traffic to new services as they are built (Correct answer)
- Rapidly scaling a stateless microservice under high load
- Implementing end-to-end encryption across a distributed system
Correct answer: Incrementally replacing a legacy monolith by routing traffic to new services as they are built
The strangler fig pattern allows teams to gradually migrate a legacy system by building new functionality alongside it and incrementally redirecting traffic, avoiding a risky big-bang rewrite.
Question 2: What does 'shift-left testing' mean in a digital product development context?
- Moving QA engineers to a different office location
- Introducing testing activities earlier in the development lifecycle, closer to coding (Correct answer)
- Reducing the number of test cases to accelerate delivery
- Outsourcing testing to a third-party vendor
Correct answer: Introducing testing activities earlier in the development lifecycle, closer to coding
Shift-left testing moves quality activities earlier in the SDLC—into design and development phases—so defects are caught when they are cheapest to fix.
Question 3: A product manager proposes an OKR where the Key Result is 'launch the mobile app by Q3.' Why is this a poorly formed Key Result?
- It is too ambitious for one quarter
- It measures an output (activity) rather than an outcome (measurable impact) (Correct answer)
- It lacks a specific technology stack
- It doesn't mention the responsible team
Correct answer: It measures an output (activity) rather than an outcome (measurable impact)
Good Key Results measure outcomes and impact (e.g., 'achieve 10,000 MAU on mobile by Q3'), not activities or deliverables, which are better tracked in project plans.
Question 4: In the context of digital product security, what is 'threat modeling'?
- Hiring ethical hackers to perform penetration testing post-launch
- A proactive process of identifying, enumerating, and mitigating potential security threats during design (Correct answer)
- Monitoring production systems for anomalous behavior
- Classifying data by sensitivity level in a data catalog
Correct answer: A proactive process of identifying, enumerating, and mitigating potential security threats during design
Threat modeling (e.g., STRIDE) is performed during design to systematically identify attack surfaces and mitigations before code is written, reducing cost of remediation.
Question 5: A SaaS product reaches product-market fit when which condition is met?
- The product has been featured in major tech press
- A sufficiently large segment of users would be 'very disappointed' if the product disappeared, typically 40%+ (Correct answer)
- Revenue exceeds operational costs for the first time
- The product has more features than its top competitor
Correct answer: A sufficiently large segment of users would be 'very disappointed' if the product disappeared, typically 40%+
Sean Ellis's benchmark for PMF is that at least 40% of surveyed users say they would be 'very disappointed' if they could no longer use the product.
Question 6: Which governance artifact helps a CTO ensure that all digital product teams are aligned on what to build next by making tradeoffs visible to stakeholders?
- Sprint burndown chart
- Prioritized product roadmap with explicit tradeoffs and strategic rationale (Correct answer)
- Daily standup notes
- Incident postmortem report
Correct answer: Prioritized product roadmap with explicit tradeoffs and strategic rationale
A well-structured product roadmap communicates prioritization decisions, their rationale, and what is explicitly NOT being done, enabling stakeholder alignment and managing expectations.
Question 7: A CTO wants to implement a 'dual-track agile' process. What characterizes this approach?
- Running two separate engineering teams on the same codebase
- Running discovery (validating what to build) in parallel with delivery (building validated ideas) (Correct answer)
- Maintaining two separate product roadmaps for enterprise and consumer segments
- Alternating between Scrum and Kanban every other sprint
Correct answer: Running discovery (validating what to build) in parallel with delivery (building validated ideas)
Dual-track agile keeps a discovery track (research, prototyping, validation) running continuously alongside the delivery track, ensuring engineers always build validated opportunities.
A CTO is evaluating whether to implement a 'strangler fig' pattern.
In what scenario is this pattern most applicable?