Quiz — Chapter 39: The Mainframe Architect's Career Path
Question 1
What is the PRIMARY shift in responsibility when moving from senior developer to architect?
A) Learning new programming languages B) Managing a team of developers C) Deciding which problems to solve rather than solving assigned problems D) Writing more documentation
Answer: C
Explanation: The core transition described in Section 39.1 is from solving the problem in front of you (developer) to deciding which problems are worth solving and in what order (architect). This represents a shift from execution to strategic decision-making. While architects do write more documentation and may influence teams, the fundamental change is in the scope of decision-making authority and responsibility.
Question 2
Which of the following is NOT one of the four dimensions of architectural thinking described in this chapter?
A) Technical breadth over technical depth B) Extended time horizon C) Programming language fluency D) Tradeoff management
Answer: C
Explanation: The four dimensions are technical breadth, time horizon, stakeholder awareness, and tradeoff management (Section 39.1). Programming language fluency is a developer-level skill. While architects need to understand programming concepts, their thinking operates at a higher level of abstraction than any single programming language.
Question 3
At the Technical Lead career level, approximately what percentage of time is typically spent writing code?
A) 80–100% B) 40–60% C) 10–20% D) 0%
Answer: B
Explanation: Section 39.2 describes the Technical Lead as spending approximately 40–60% of their time writing code, with the remainder spent on code review, design decisions, cross-team coordination, and other leadership activities. This represents the bridge between individual contribution and full-time architecture work.
Question 4
What is an Architecture Decision Record (ADR)?
A) A log of all code changes made to a system B) A document recording a significant architectural decision, its context, options considered, and rationale C) A performance benchmark report for system architecture D) A compliance audit document required by regulatory agencies
Answer: B
Explanation: As described in Section 39.3, an ADR documents a significant architectural decision including the context, options considered, the decision made, and the rationale. ADRs are considered perhaps the most important artifact in an architect's portfolio because they demonstrate the thinking process, not just the outcome.
Question 5
According to the chapter, which portfolio deliverable do most architects neglect but that most distinguishes the great ones?
A) Architecture Decision Records B) Technology evaluations C) Post-implementation reviews D) System architecture documents
Answer: C
Explanation: Section 39.3 explicitly states that post-implementation reviews are "the deliverable that most architects neglect — and that most distinguishes the great ones." They require intellectual honesty about mistakes and demonstrate the ability to learn from experience, which is uncomfortable but enormously valuable.
Question 6
In the stakeholder mapping framework described in Section 39.4, a stakeholder with HIGH influence and LOW interest should be:
A) Managed closely with regular detailed updates B) Kept satisfied with periodic updates C) Kept informed with general communications D) Monitored with minimal communication
Answer: B
Explanation: The stakeholder mapping quadrant in Section 39.4 places high-influence, low-interest stakeholders in the "keep satisfied" category. These stakeholders (like a CFO for a technical initiative) have the power to block your project but are not actively engaged in it. They need enough information to remain supportive but do not need detailed technical updates.
Question 7
What is the key principle for resolving architectural conflicts according to the chapter?
A) The most senior person's preference should prevail B) Always choose the technically superior solution C) Separate positions from interests to find creative solutions D) Put all options to a team vote
Answer: C
Explanation: Section 39.4 describes separating positions from interests as the most useful framework for architectural conflict resolution. A position is what someone says they want; an interest is why they want it. When you focus on interests rather than positions, creative solutions become possible that address multiple parties' underlying needs.
Question 8
In IBM mainframe economics, what is the R4HA and why does it matter to architects?
A) A reliability metric that determines warranty coverage B) The rolling four-hour average of highest CPU utilization that determines monthly software licensing costs C) A hardware performance rating that determines processing capacity D) A risk assessment formula used in vendor negotiations
Answer: B
Explanation: Section 39.5 explains that MLC (Monthly License Charge) software pricing is based on the R4HA — the rolling four-hour average of the highest CPU utilization in a month. This matters because a single batch job that spikes CPU at an unusual time can increase the entire monthly software bill. Architects must design workloads with these pricing implications in mind.
Question 9
Why is zIIP eligibility architecturally significant from a cost perspective?
A) zIIP processors are free with every z/OS license B) Work on zIIPs does not count toward MLC pricing calculations C) zIIPs process COBOL programs 50% faster than general-purpose processors D) zIIPs eliminate the need for DB2 licensing
Answer: B
Explanation: Section 39.5 explains that work running on IBM Specialty Engines (zIIPs) does not count toward MLC pricing. This means architects who can shift workloads to zIIP-eligible processing (Java, XML parsing, DB2 stored procedures, encryption) can deliver dramatic cost savings without changing the actual processing being done.
Question 10
When communicating with executives, the chapter recommends framing all architectural recommendations in terms of which four concepts?
A) Speed, reliability, scalability, security B) Revenue, cost, risk, competitive advantage C) Innovation, compliance, efficiency, customer satisfaction D) Technology, process, people, governance
Answer: B
Explanation: Section 39.5 states that when communicating with executives, architects should translate everything into four concepts: revenue (does it enable growth?), cost (does it reduce expenses?), risk (does it reduce exposure?), and competitive advantage (does it improve market position?). Every architectural recommendation should connect to at least one of these.
Question 11
What is the chapter's honest assessment of the value of certifications for architects?
A) They are essential and should be the primary focus of career development B) They are worthless and not worth pursuing C) They are necessary but not sufficient — they check boxes but do not prove architectural capability D) They are only valuable at the senior developer level
Answer: C
Explanation: Section 39.6 offers a candid assessment: certifications are "necessary but not sufficient." They prove you can pass a test, not that you can architect a system. However, they serve legitimate purposes including structured learning, common vocabulary, HR screening requirements, and demonstrating commitment to professional development.
Question 12
Which of the following is described as "the most dangerous thing a mainframe architect can do"?
A) Recommending a platform migration B) Disagreeing with an executive's technical opinion C) Stop learning about non-mainframe technologies D) Writing code in production systems
Answer: C
Explanation: Section 39.6 explicitly states that "the most dangerous thing a mainframe architect can do is stop learning about non-mainframe technologies." Understanding Kubernetes, microservices, event-driven architecture, cloud-native patterns, and AI/ML is essential not to replace the mainframe but to integrate with it effectively. Architects who become insular lose their ability to design hybrid solutions.
Question 13
According to the chapter, what are the three components of the mainframe architect's unique value proposition?
A) COBOL expertise, JCL knowledge, DB2 administration B) Understanding systems that cannot fail, bridging two worlds, carrying institutional knowledge C) Cost reduction, risk management, vendor negotiation D) Technical depth, management skills, industry certifications
Answer: B
Explanation: Section 39.7 identifies three components of the mainframe architect's unique value: understanding systems where failure has immediate material consequences (systems that cannot fail), bridging traditional mainframe and modern cloud-native worlds, and carrying institutional knowledge that exists nowhere else and cannot be Googled.
Question 14
In Kwame's business case for the CNB payment modernization, why did he recommend the hybrid approach ($6.4M TCO) over the COBOL-only refactor ($4.2M TCO)?
A) The hybrid approach used newer technology that looked better in presentations B) The COBOL refactor would not accommodate real-time payment requirements coming in 2027, requiring an additional $3M initiative later C) IBM offered a discount on the hybrid approach D) The Java team threatened to resign if the COBOL refactor was chosen
Answer: B
Explanation: Section 39.5 explains that while the COBOL refactor appeared cheapest at $4.2M over five years, Kwame's analysis showed it would not accommodate the real-time payment requirements expected in 2027, necessitating an additional $3M initiative. The hybrid approach, though more expensive initially, had a lower long-term cost when future requirements were factored in. This exemplifies the architect's longer time horizon.
Question 15
What does the chapter identify as the transition moment that signals readiness for the Technical Lead level?
A) Receiving a formal promotion offer from management B) Completing an architecture certification C) The first time you delete your own code because someone on your team wrote a better solution — and it feels good rather than threatening D) Having ten or more years of development experience
Answer: C
Explanation: Section 39.2 identifies this specific transition moment: "The first time you delete your own code because someone on your team wrote a better solution. If that feels good rather than threatening, you are ready for this level." This captures the psychological shift from individual contribution to team enablement that defines the move into technical leadership.