Advanced
Enterprise Architecture
#capability
#heat-map
#gap-analysis
Capability Modeling Vocabulary
5 exercises — practice the language for business capability maps, heat maps, gap analysis, and capability maturity assessments.
0 / 45 completed
1 / 45
An enterprise architect presents a capability map to the board.
What does a business capability map show?
What does a business capability map show?
A business capability map answers "what can we do?" — not "how do we do it?" or "who does it?" Capabilities are defined at the business level (e.g., "Customer Onboarding," "Risk Assessment," "Claims Processing") independently of the current operating model. This makes the map durable through organisational change and technology evolution. It is the foundation for investment prioritisation, heat mapping, and gap analysis.
2 / 45
During a capability assessment, a team uses a heat map overlay on the capability model.
What does this communicate?
What does this communicate?
A capability heat map applies a colour coding (typically red/amber/green or a similar scale) to a capability map to communicate a specific dimension — common examples: performance gaps (red = underperforming), investment levels (high/medium/low), strategic priority (core/differentiating/commodity). Heat maps make complex assessments immediately visual for executive stakeholders, enabling fast decisions about where to invest, improve, or divest.
3 / 45
Complete the gap analysis statement from a capability review:
"Our current capability for real-time fraud detection is at Level 2 (Managed). The target state is Level 4 (Optimised). We need to close this _____ gap by investing in ML-based scoring and automated case management."
"Our current capability for real-time fraud detection is at Level 2 (Managed). The target state is Level 4 (Optimised). We need to close this _____ gap by investing in ML-based scoring and automated case management."
Capability gap is the standard term for the distance between the current capability maturity and the target level. Gap analysis is a core output of capability modelling: it identifies where investment is needed to reach the target state. The language "current capability... target state... close this gap" is the standard narrative structure for presenting capability investment cases to leadership.
4 / 45
A capability maturity assessment rates the "Order Management" capability as Level 1 — Initial.
What does this mean?
What does this mean?
In capability maturity models (derived from CMMI and similar frameworks), Level 1 — Initial describes processes that are chaotic, ad hoc, and undocumented. Success depends on heroic individual effort rather than repeatable process. The typical maturity scale is: 1 (Initial) → 2 (Managed) → 3 (Defined) → 4 (Quantitatively Managed) → 5 (Optimising). Capability maturity ratings help organisations prioritise where process and technology investment will have the most impact.
5 / 45
Which sentence correctly uses capability modelling vocabulary in an executive briefing?
Option B correctly combines capability modelling concepts: heat map (visual assessment tool), strategic differentiator (a capability that provides competitive advantage), Level 2 maturity (specific rating), and capability gap (the investment case). This is the language of an architecture briefing to a board or executive committee. Option A describes a technical inventory (microservices ≠ capabilities). Option C describes process modelling (BPMN), not capability modelling.
6 / 45
Senior Dev: "I'm seeing a lot of inconsistencies in how we handle user authentication across the different microservices. The API response from AuthService is returning a JWT, but PaymentService isn't validating it properly – it's just trusting the header. This could lead to serious security vulnerabilities if an attacker can spoof the JWT. What should I add to my PR description to clearly communicate this issue and request changes?", The correct answer highlights the need for robust JWT validation. Simply stating an inconsistency isn't enough; developers need precise instructions on how to fix the vulnerability. A detailed schema definition and stricter validation (signature verification and expiration checks) are crucial steps to mitigate security risks—the other options either downplay the severity or offer insufficient guidance. This aligns with best practices for secure API design and proactive code reviews.
7 / 45
Sarah: "Hey team, I'm reviewing this PR for the 'Product Catalog' capability. The description mentions 'data governance,' but I'm not entirely clear on what that means in the context of our architecture. Specifically, it doesn't specify *which* data elements are governed or *how*. Should I push for more detail about the scope of data governance within this PR?
Mark: "Just add a note saying we're focusing on ensuring data quality and compliance with GDPR requirements."This scenario highlights the importance of precise language when discussing capability modeling. 'Data governance,' while related to compliance (as Mark suggests), is a broader concept that needs specific definition within the context of the 'Product Catalog' capability. Sarah's question correctly identifies that the PR description lacks detail about *which* data elements are governed and *how*, which is crucial for understanding the scope and impact as defined in the enterprise architecture. A robust explanation requires clarifying the boundaries of governance, not just stating a general compliance objective.
8 / 45
Alex: "I've been reviewing the proposed capability model for 'Customer Onboarding'. The description states we have a 'Service Level Agreement' (SLA) for processing new customer accounts. However, I'm not sure what that actually *means* in terms of measurable performance – what metrics would we track to demonstrate successful onboarding?"This question tests understanding of how SLAs are practically applied within capability modeling. An SLA in this context isn't just a statement; it needs to be translated into measurable KPIs – quantifiable metrics that demonstrate performance. Options A and B correctly highlight the need for defining specific targets and associated KPIs, while options C and D misinterpret the purpose of an SLA as purely descriptive or security-focused respectively.
Alex is asking for a concrete definition, not a vague promise.9 / 45
Liam (Senior Architect) sends this Slack message during a code review:
'Okay team, I've noticed the 'Inventory Management' capability consistently returns slightly delayed data. The API calls are fine from the front-end, but the backend processing seems to be bottlenecking. We need to understand *why* it's lagging and whether we can proactively mitigate this without fundamentally changing how we handle inventory updates. Any ideas?'
Which of the following responses best addresses Liam's concern and aligns with capability modeling principles?The correct answer (option 1) demonstrates an understanding of capability modeling by focusing on *root cause analysis* within the defined 'Inventory Management' capability. It acknowledges the performance issue while staying aligned with the existing architecture and process – a key principle in capability modeling. Options A and B propose simplistic solutions without considering the broader capability context, and option C is too vague to guide an investigation. It's crucial to identify the *why* behind a problem within a capability before attempting a fix.
10 / 45
Liam's Slack message highlights a performance issue within the 'Inventory Management' capability. Which of the following responses best addresses this concern and aligns with capability modeling principles?
Consider Liam's focus on understanding *why* the data is delayed without fundamentally changing the process. The goal isn't just to fix the immediate problem, but to understand the root cause within the context of the capability's defined requirements.
Option 2 is correct because it directly addresses Liam's concern by proposing a systematic investigation – monitoring API response times. This aligns with capability modeling by focusing on measuring performance against defined requirements (the SLA) and using data to understand the root cause of the delay within the 'Inventory Management' capability. Options A and B represent reactive, potentially inefficient solutions; option C is appropriate but doesn't specifically connect to the core principles of capability analysis, while option D shifts blame without diagnosing the underlying problem.
11 / 45
Senior Dev: "I'm seeing a lot of inconsistencies in how we handle user authentication across the different microservices. The API response from AuthService is returning a JWT, but PaymentService isn't validating it properly – it's just trusting the header. This could lead to serious security vulnerabilities if an attacker can spoof the JWT. What should I add to my PR description to clearly communicate this issue and request changes?", The correct answer highlights the need for robust JWT validation. Simply stating an inconsistency isn't enough; developers need precise instructions on how to fix the vulnerability. A detailed schema definition and stricter validation (signature verification and expiration checks) are crucial steps to mitigate security risks—the other options either downplay the severity or offer insufficient guidance. This aligns with best practices for secure API design and proactive code reviews.
12 / 45
Sarah: "Hey team, I'm reviewing this PR for the 'Product Catalog' capability. The description mentions 'data governance,' but I'm not entirely clear on what that means in the context of our architecture. Specifically, it doesn't specify *which* data elements are governed or *how*. Should I push for more detail about the scope of data governance within this PR?
Mark: "Just add a note saying we're focusing on ensuring data quality and compliance with GDPR requirements."This scenario highlights the importance of precise language when discussing capability modeling. 'Data governance,' while related to compliance (as Mark suggests), is a broader concept that needs specific definition within the context of the 'Product Catalog' capability. Sarah's question correctly identifies that the PR description lacks detail about *which* data elements are governed and *how*, which is crucial for understanding the scope and impact as defined in the enterprise architecture. A robust explanation requires clarifying the boundaries of governance, not just stating a general compliance objective.
13 / 45
Alex: "I've been reviewing the proposed capability model for 'Customer Onboarding'. The description states we have a 'Service Level Agreement' (SLA) for processing new customer accounts. However, I'm not sure what that actually *means* in terms of measurable performance – what metrics would we track to demonstrate successful onboarding?"This question tests understanding of how SLAs are practically applied within capability modeling. An SLA in this context isn't just a statement; it needs to be translated into measurable KPIs – quantifiable metrics that demonstrate performance. Options A and B correctly highlight the need for defining specific targets and associated KPIs, while options C and D misinterpret the purpose of an SLA as purely descriptive or security-focused respectively.
Alex is asking for a concrete definition, not a vague promise.14 / 45
Liam (Senior Architect) sends this Slack message during a code review:
'Okay team, I've noticed the 'Inventory Management' capability consistently returns slightly delayed data. The API calls are fine from the front-end, but the backend processing seems to be bottlenecking. We need to understand *why* it's lagging and whether we can proactively mitigate this without fundamentally changing how we handle inventory updates. Any ideas?'
Which of the following responses best addresses Liam's concern and aligns with capability modeling principles?The correct answer (option 1) demonstrates an understanding of capability modeling by focusing on *root cause analysis* within the defined 'Inventory Management' capability. It acknowledges the performance issue while staying aligned with the existing architecture and process – a key principle in capability modeling. Options A and B propose simplistic solutions without considering the broader capability context, and option C is too vague to guide an investigation. It's crucial to identify the *why* behind a problem within a capability before attempting a fix.
15 / 45
Liam's Slack message highlights a performance issue within the 'Inventory Management' capability. Which of the following responses best addresses this concern and aligns with capability modeling principles?
Consider Liam's focus on understanding *why* the data is delayed without fundamentally changing the process. The goal isn't just to fix the immediate problem, but to understand the root cause within the context of the capability's defined requirements.
Option 2 is correct because it directly addresses Liam's concern by proposing a systematic investigation – monitoring API response times. This aligns with capability modeling by focusing on measuring performance against defined requirements (the SLA) and using data to understand the root cause of the delay within the 'Inventory Management' capability. Options A and B represent reactive, potentially inefficient solutions; option C is appropriate but doesn't specifically connect to the core principles of capability analysis, while option D shifts blame without diagnosing the underlying problem.
16 / 45
Senior Dev: "I'm seeing a lot of inconsistencies in how we handle user authentication across the different microservices. The API response from AuthService is returning a JWT, but PaymentService isn't validating it properly – it's just trusting the header. This could lead to serious security vulnerabilities if an attacker can spoof the JWT. What should I add to my PR description to clearly communicate this issue and request changes?", The correct answer highlights the need for robust JWT validation. Simply stating an inconsistency isn't enough; developers need precise instructions on how to fix the vulnerability. A detailed schema definition and stricter validation (signature verification and expiration checks) are crucial steps to mitigate security risks—the other options either downplay the severity or offer insufficient guidance. This aligns with best practices for secure API design and proactive code reviews.
17 / 45
Sarah: "Hey team, I'm reviewing this PR for the 'Product Catalog' capability. The description mentions 'data governance,' but I'm not entirely clear on what that means in the context of our architecture. Specifically, it doesn't specify *which* data elements are governed or *how*. Should I push for more detail about the scope of data governance within this PR?
Mark: "Just add a note saying we're focusing on ensuring data quality and compliance with GDPR requirements."This scenario highlights the importance of precise language when discussing capability modeling. 'Data governance,' while related to compliance (as Mark suggests), is a broader concept that needs specific definition within the context of the 'Product Catalog' capability. Sarah's question correctly identifies that the PR description lacks detail about *which* data elements are governed and *how*, which is crucial for understanding the scope and impact as defined in the enterprise architecture. A robust explanation requires clarifying the boundaries of governance, not just stating a general compliance objective.
18 / 45
Alex: "I've been reviewing the proposed capability model for 'Customer Onboarding'. The description states we have a 'Service Level Agreement' (SLA) for processing new customer accounts. However, I'm not sure what that actually *means* in terms of measurable performance – what metrics would we track to demonstrate successful onboarding?"This question tests understanding of how SLAs are practically applied within capability modeling. An SLA in this context isn't just a statement; it needs to be translated into measurable KPIs – quantifiable metrics that demonstrate performance. Options A and B correctly highlight the need for defining specific targets and associated KPIs, while options C and D misinterpret the purpose of an SLA as purely descriptive or security-focused respectively.
Alex is asking for a concrete definition, not a vague promise.19 / 45
Liam (Senior Architect) sends this Slack message during a code review:
'Okay team, I've noticed the 'Inventory Management' capability consistently returns slightly delayed data. The API calls are fine from the front-end, but the backend processing seems to be bottlenecking. We need to understand *why* it's lagging and whether we can proactively mitigate this without fundamentally changing how we handle inventory updates. Any ideas?'
Which of the following responses best addresses Liam's concern and aligns with capability modeling principles?The correct answer (option 1) demonstrates an understanding of capability modeling by focusing on *root cause analysis* within the defined 'Inventory Management' capability. It acknowledges the performance issue while staying aligned with the existing architecture and process – a key principle in capability modeling. Options A and B propose simplistic solutions without considering the broader capability context, and option C is too vague to guide an investigation. It's crucial to identify the *why* behind a problem within a capability before attempting a fix.
20 / 45
Liam's Slack message highlights a performance issue within the 'Inventory Management' capability. Which of the following responses best addresses this concern and aligns with capability modeling principles?
Consider Liam's focus on understanding *why* the data is delayed without fundamentally changing the process. The goal isn't just to fix the immediate problem, but to understand the root cause within the context of the capability's defined requirements.
Option 2 is correct because it directly addresses Liam's concern by proposing a systematic investigation – monitoring API response times. This aligns with capability modeling by focusing on measuring performance against defined requirements (the SLA) and using data to understand the root cause of the delay within the 'Inventory Management' capability. Options A and B represent reactive, potentially inefficient solutions; option C is appropriate but doesn't specifically connect to the core principles of capability analysis, while option D shifts blame without diagnosing the underlying problem.
21 / 45
Senior Dev: "I'm seeing a lot of inconsistencies in how we handle user authentication across the different microservices. The API response from AuthService is returning a JWT, but PaymentService isn't validating it properly – it's just trusting the header. This could lead to serious security vulnerabilities if an attacker can spoof the JWT. What should I add to my PR description to clearly communicate this issue and request changes?", The correct answer highlights the need for robust JWT validation. Simply stating an inconsistency isn't enough; developers need precise instructions on how to fix the vulnerability. A detailed schema definition and stricter validation (signature verification and expiration checks) are crucial steps to mitigate security risks—the other options either downplay the severity or offer insufficient guidance. This aligns with best practices for secure API design and proactive code reviews.
22 / 45
Sarah: "Hey team, I'm reviewing this PR for the 'Product Catalog' capability. The description mentions 'data governance,' but I'm not entirely clear on what that means in the context of our architecture. Specifically, it doesn't specify *which* data elements are governed or *how*. Should I push for more detail about the scope of data governance within this PR?
Mark: "Just add a note saying we're focusing on ensuring data quality and compliance with GDPR requirements."This scenario highlights the importance of precise language when discussing capability modeling. 'Data governance,' while related to compliance (as Mark suggests), is a broader concept that needs specific definition within the context of the 'Product Catalog' capability. Sarah's question correctly identifies that the PR description lacks detail about *which* data elements are governed and *how*, which is crucial for understanding the scope and impact as defined in the enterprise architecture. A robust explanation requires clarifying the boundaries of governance, not just stating a general compliance objective.
23 / 45
Alex: "I've been reviewing the proposed capability model for 'Customer Onboarding'. The description states we have a 'Service Level Agreement' (SLA) for processing new customer accounts. However, I'm not sure what that actually *means* in terms of measurable performance – what metrics would we track to demonstrate successful onboarding?"This question tests understanding of how SLAs are practically applied within capability modeling. An SLA in this context isn't just a statement; it needs to be translated into measurable KPIs – quantifiable metrics that demonstrate performance. Options A and B correctly highlight the need for defining specific targets and associated KPIs, while options C and D misinterpret the purpose of an SLA as purely descriptive or security-focused respectively.
Alex is asking for a concrete definition, not a vague promise.24 / 45
Liam (Senior Architect) sends this Slack message during a code review:
'Okay team, I've noticed the 'Inventory Management' capability consistently returns slightly delayed data. The API calls are fine from the front-end, but the backend processing seems to be bottlenecking. We need to understand *why* it's lagging and whether we can proactively mitigate this without fundamentally changing how we handle inventory updates. Any ideas?'
Which of the following responses best addresses Liam's concern and aligns with capability modeling principles?The correct answer (option 1) demonstrates an understanding of capability modeling by focusing on *root cause analysis* within the defined 'Inventory Management' capability. It acknowledges the performance issue while staying aligned with the existing architecture and process – a key principle in capability modeling. Options A and B propose simplistic solutions without considering the broader capability context, and option C is too vague to guide an investigation. It's crucial to identify the *why* behind a problem within a capability before attempting a fix.
25 / 45
Liam's Slack message highlights a performance issue within the 'Inventory Management' capability. Which of the following responses best addresses this concern and aligns with capability modeling principles?
Consider Liam's focus on understanding *why* the data is delayed without fundamentally changing the process. The goal isn't just to fix the immediate problem, but to understand the root cause within the context of the capability's defined requirements.
Option 2 is correct because it directly addresses Liam's concern by proposing a systematic investigation – monitoring API response times. This aligns with capability modeling by focusing on measuring performance against defined requirements (the SLA) and using data to understand the root cause of the delay within the 'Inventory Management' capability. Options A and B represent reactive, potentially inefficient solutions; option C is appropriate but doesn't specifically connect to the core principles of capability analysis, while option D shifts blame without diagnosing the underlying problem.
26 / 45
Senior Dev: "I'm seeing a lot of inconsistencies in how we handle user authentication across the different microservices. The API response from AuthService is returning a JWT, but PaymentService isn't validating it properly – it's just trusting the header. This could lead to serious security vulnerabilities if an attacker can spoof the JWT. What should I add to my PR description to clearly communicate this issue and request changes?", The correct answer highlights the need for robust JWT validation. Simply stating an inconsistency isn't enough; developers need precise instructions on how to fix the vulnerability. A detailed schema definition and stricter validation (signature verification and expiration checks) are crucial steps to mitigate security risks—the other options either downplay the severity or offer insufficient guidance. This aligns with best practices for secure API design and proactive code reviews.
27 / 45
Sarah: "Hey team, I'm reviewing this PR for the 'Product Catalog' capability. The description mentions 'data governance,' but I'm not entirely clear on what that means in the context of our architecture. Specifically, it doesn't specify *which* data elements are governed or *how*. Should I push for more detail about the scope of data governance within this PR?
Mark: "Just add a note saying we're focusing on ensuring data quality and compliance with GDPR requirements."This scenario highlights the importance of precise language when discussing capability modeling. 'Data governance,' while related to compliance (as Mark suggests), is a broader concept that needs specific definition within the context of the 'Product Catalog' capability. Sarah's question correctly identifies that the PR description lacks detail about *which* data elements are governed and *how*, which is crucial for understanding the scope and impact as defined in the enterprise architecture. A robust explanation requires clarifying the boundaries of governance, not just stating a general compliance objective.
28 / 45
Alex: "I've been reviewing the proposed capability model for 'Customer Onboarding'. The description states we have a 'Service Level Agreement' (SLA) for processing new customer accounts. However, I'm not sure what that actually *means* in terms of measurable performance – what metrics would we track to demonstrate successful onboarding?"This question tests understanding of how SLAs are practically applied within capability modeling. An SLA in this context isn't just a statement; it needs to be translated into measurable KPIs – quantifiable metrics that demonstrate performance. Options A and B correctly highlight the need for defining specific targets and associated KPIs, while options C and D misinterpret the purpose of an SLA as purely descriptive or security-focused respectively.
Alex is asking for a concrete definition, not a vague promise.29 / 45
Liam (Senior Architect) sends this Slack message during a code review:
'Okay team, I've noticed the 'Inventory Management' capability consistently returns slightly delayed data. The API calls are fine from the front-end, but the backend processing seems to be bottlenecking. We need to understand *why* it's lagging and whether we can proactively mitigate this without fundamentally changing how we handle inventory updates. Any ideas?'
Which of the following responses best addresses Liam's concern and aligns with capability modeling principles?The correct answer (option 1) demonstrates an understanding of capability modeling by focusing on *root cause analysis* within the defined 'Inventory Management' capability. It acknowledges the performance issue while staying aligned with the existing architecture and process – a key principle in capability modeling. Options A and B propose simplistic solutions without considering the broader capability context, and option C is too vague to guide an investigation. It's crucial to identify the *why* behind a problem within a capability before attempting a fix.
30 / 45
Liam's Slack message highlights a performance issue within the 'Inventory Management' capability. Which of the following responses best addresses this concern and aligns with capability modeling principles?
Consider Liam's focus on understanding *why* the data is delayed without fundamentally changing the process. The goal isn't just to fix the immediate problem, but to understand the root cause within the context of the capability's defined requirements.
Option 2 is correct because it directly addresses Liam's concern by proposing a systematic investigation – monitoring API response times. This aligns with capability modeling by focusing on measuring performance against defined requirements (the SLA) and using data to understand the root cause of the delay within the 'Inventory Management' capability. Options A and B represent reactive, potentially inefficient solutions; option C is appropriate but doesn't specifically connect to the core principles of capability analysis, while option D shifts blame without diagnosing the underlying problem.
31 / 45
Senior Dev: "I'm seeing a lot of inconsistencies in how we handle user authentication across the different microservices. The API response from AuthService is returning a JWT, but PaymentService isn't validating it properly – it's just trusting the header. This could lead to serious security vulnerabilities if an attacker can spoof the JWT. What should I add to my PR description to clearly communicate this issue and request changes?", The correct answer highlights the need for robust JWT validation. Simply stating an inconsistency isn't enough; developers need precise instructions on how to fix the vulnerability. A detailed schema definition and stricter validation (signature verification and expiration checks) are crucial steps to mitigate security risks—the other options either downplay the severity or offer insufficient guidance. This aligns with best practices for secure API design and proactive code reviews.
32 / 45
Sarah: "Hey team, I'm reviewing this PR for the 'Product Catalog' capability. The description mentions 'data governance,' but I'm not entirely clear on what that means in the context of our architecture. Specifically, it doesn't specify *which* data elements are governed or *how*. Should I push for more detail about the scope of data governance within this PR?
Mark: "Just add a note saying we're focusing on ensuring data quality and compliance with GDPR requirements."This scenario highlights the importance of precise language when discussing capability modeling. 'Data governance,' while related to compliance (as Mark suggests), is a broader concept that needs specific definition within the context of the 'Product Catalog' capability. Sarah's question correctly identifies that the PR description lacks detail about *which* data elements are governed and *how*, which is crucial for understanding the scope and impact as defined in the enterprise architecture. A robust explanation requires clarifying the boundaries of governance, not just stating a general compliance objective.
33 / 45
Alex: "I've been reviewing the proposed capability model for 'Customer Onboarding'. The description states we have a 'Service Level Agreement' (SLA) for processing new customer accounts. However, I'm not sure what that actually *means* in terms of measurable performance – what metrics would we track to demonstrate successful onboarding?"This question tests understanding of how SLAs are practically applied within capability modeling. An SLA in this context isn't just a statement; it needs to be translated into measurable KPIs – quantifiable metrics that demonstrate performance. Options A and B correctly highlight the need for defining specific targets and associated KPIs, while options C and D misinterpret the purpose of an SLA as purely descriptive or security-focused respectively.
Alex is asking for a concrete definition, not a vague promise.34 / 45
Liam (Senior Architect) sends this Slack message during a code review:
'Okay team, I've noticed the 'Inventory Management' capability consistently returns slightly delayed data. The API calls are fine from the front-end, but the backend processing seems to be bottlenecking. We need to understand *why* it's lagging and whether we can proactively mitigate this without fundamentally changing how we handle inventory updates. Any ideas?'
Which of the following responses best addresses Liam's concern and aligns with capability modeling principles?The correct answer (option 1) demonstrates an understanding of capability modeling by focusing on *root cause analysis* within the defined 'Inventory Management' capability. It acknowledges the performance issue while staying aligned with the existing architecture and process – a key principle in capability modeling. Options A and B propose simplistic solutions without considering the broader capability context, and option C is too vague to guide an investigation. It's crucial to identify the *why* behind a problem within a capability before attempting a fix.
35 / 45
Liam's Slack message highlights a performance issue within the 'Inventory Management' capability. Which of the following responses best addresses this concern and aligns with capability modeling principles?
Consider Liam's focus on understanding *why* the data is delayed without fundamentally changing the process. The goal isn't just to fix the immediate problem, but to understand the root cause within the context of the capability's defined requirements.
Option 2 is correct because it directly addresses Liam's concern by proposing a systematic investigation – monitoring API response times. This aligns with capability modeling by focusing on measuring performance against defined requirements (the SLA) and using data to understand the root cause of the delay within the 'Inventory Management' capability. Options A and B represent reactive, potentially inefficient solutions; option C is appropriate but doesn't specifically connect to the core principles of capability analysis, while option D shifts blame without diagnosing the underlying problem.
36 / 45
Senior Dev: "I'm seeing a lot of inconsistencies in how we handle user authentication across the different microservices. The API response from AuthService is returning a JWT, but PaymentService isn't validating it properly – it's just trusting the header. This could lead to serious security vulnerabilities if an attacker can spoof the JWT. What should I add to my PR description to clearly communicate this issue and request changes?", The correct answer highlights the need for robust JWT validation. Simply stating an inconsistency isn't enough; developers need precise instructions on how to fix the vulnerability. A detailed schema definition and stricter validation (signature verification and expiration checks) are crucial steps to mitigate security risks—the other options either downplay the severity or offer insufficient guidance. This aligns with best practices for secure API design and proactive code reviews.
37 / 45
Sarah: "Hey team, I'm reviewing this PR for the 'Product Catalog' capability. The description mentions 'data governance,' but I'm not entirely clear on what that means in the context of our architecture. Specifically, it doesn't specify *which* data elements are governed or *how*. Should I push for more detail about the scope of data governance within this PR?
Mark: "Just add a note saying we're focusing on ensuring data quality and compliance with GDPR requirements."This scenario highlights the importance of precise language when discussing capability modeling. 'Data governance,' while related to compliance (as Mark suggests), is a broader concept that needs specific definition within the context of the 'Product Catalog' capability. Sarah's question correctly identifies that the PR description lacks detail about *which* data elements are governed and *how*, which is crucial for understanding the scope and impact as defined in the enterprise architecture. A robust explanation requires clarifying the boundaries of governance, not just stating a general compliance objective.
38 / 45
Alex: "I've been reviewing the proposed capability model for 'Customer Onboarding'. The description states we have a 'Service Level Agreement' (SLA) for processing new customer accounts. However, I'm not sure what that actually *means* in terms of measurable performance – what metrics would we track to demonstrate successful onboarding?"This question tests understanding of how SLAs are practically applied within capability modeling. An SLA in this context isn't just a statement; it needs to be translated into measurable KPIs – quantifiable metrics that demonstrate performance. Options A and B correctly highlight the need for defining specific targets and associated KPIs, while options C and D misinterpret the purpose of an SLA as purely descriptive or security-focused respectively.
Alex is asking for a concrete definition, not a vague promise.39 / 45
Liam (Senior Architect) sends this Slack message during a code review:
'Okay team, I've noticed the 'Inventory Management' capability consistently returns slightly delayed data. The API calls are fine from the front-end, but the backend processing seems to be bottlenecking. We need to understand *why* it's lagging and whether we can proactively mitigate this without fundamentally changing how we handle inventory updates. Any ideas?'
Which of the following responses best addresses Liam's concern and aligns with capability modeling principles?The correct answer (option 1) demonstrates an understanding of capability modeling by focusing on *root cause analysis* within the defined 'Inventory Management' capability. It acknowledges the performance issue while staying aligned with the existing architecture and process – a key principle in capability modeling. Options A and B propose simplistic solutions without considering the broader capability context, and option C is too vague to guide an investigation. It's crucial to identify the *why* behind a problem within a capability before attempting a fix.
40 / 45
Liam's Slack message highlights a performance issue within the 'Inventory Management' capability. Which of the following responses best addresses this concern and aligns with capability modeling principles?
Consider Liam's focus on understanding *why* the data is delayed without fundamentally changing the process. The goal isn't just to fix the immediate problem, but to understand the root cause within the context of the capability's defined requirements.
Option 2 is correct because it directly addresses Liam's concern by proposing a systematic investigation – monitoring API response times. This aligns with capability modeling by focusing on measuring performance against defined requirements (the SLA) and using data to understand the root cause of the delay within the 'Inventory Management' capability. Options A and B represent reactive, potentially inefficient solutions; option C is appropriate but doesn't specifically connect to the core principles of capability analysis, while option D shifts blame without diagnosing the underlying problem.
41 / 45
Senior Dev: "I'm seeing a lot of inconsistencies in how we handle user authentication across the different microservices. The API response from AuthService is returning a JWT, but PaymentService isn't validating it properly – it's just trusting the header. This could lead to serious security vulnerabilities if an attacker can spoof the JWT. What should I add to my PR description to clearly communicate this issue and request changes?", The correct answer highlights the need for robust JWT validation. Simply stating an inconsistency isn't enough; developers need precise instructions on how to fix the vulnerability. A detailed schema definition and stricter validation (signature verification and expiration checks) are crucial steps to mitigate security risks—the other options either downplay the severity or offer insufficient guidance. This aligns with best practices for secure API design and proactive code reviews.
42 / 45
Sarah: "Hey team, I'm reviewing this PR for the 'Product Catalog' capability. The description mentions 'data governance,' but I'm not entirely clear on what that means in the context of our architecture. Specifically, it doesn't specify *which* data elements are governed or *how*. Should I push for more detail about the scope of data governance within this PR?
Mark: "Just add a note saying we're focusing on ensuring data quality and compliance with GDPR requirements."This scenario highlights the importance of precise language when discussing capability modeling. 'Data governance,' while related to compliance (as Mark suggests), is a broader concept that needs specific definition within the context of the 'Product Catalog' capability. Sarah's question correctly identifies that the PR description lacks detail about *which* data elements are governed and *how*, which is crucial for understanding the scope and impact as defined in the enterprise architecture. A robust explanation requires clarifying the boundaries of governance, not just stating a general compliance objective.
43 / 45
Alex: "I've been reviewing the proposed capability model for 'Customer Onboarding'. The description states we have a 'Service Level Agreement' (SLA) for processing new customer accounts. However, I'm not sure what that actually *means* in terms of measurable performance – what metrics would we track to demonstrate successful onboarding?"This question tests understanding of how SLAs are practically applied within capability modeling. An SLA in this context isn't just a statement; it needs to be translated into measurable KPIs – quantifiable metrics that demonstrate performance. Options A and B correctly highlight the need for defining specific targets and associated KPIs, while options C and D misinterpret the purpose of an SLA as purely descriptive or security-focused respectively.
Alex is asking for a concrete definition, not a vague promise.44 / 45
Liam (Senior Architect) sends this Slack message during a code review:
'Okay team, I've noticed the 'Inventory Management' capability consistently returns slightly delayed data. The API calls are fine from the front-end, but the backend processing seems to be bottlenecking. We need to understand *why* it's lagging and whether we can proactively mitigate this without fundamentally changing how we handle inventory updates. Any ideas?'
Which of the following responses best addresses Liam's concern and aligns with capability modeling principles?The correct answer (option 1) demonstrates an understanding of capability modeling by focusing on *root cause analysis* within the defined 'Inventory Management' capability. It acknowledges the performance issue while staying aligned with the existing architecture and process – a key principle in capability modeling. Options A and B propose simplistic solutions without considering the broader capability context, and option C is too vague to guide an investigation. It's crucial to identify the *why* behind a problem within a capability before attempting a fix.
45 / 45
Liam's Slack message highlights a performance issue within the 'Inventory Management' capability. Which of the following responses best addresses this concern and aligns with capability modeling principles?
Consider Liam's focus on understanding *why* the data is delayed without fundamentally changing the process. The goal isn't just to fix the immediate problem, but to understand the root cause within the context of the capability's defined requirements.
Option 2 is correct because it directly addresses Liam's concern by proposing a systematic investigation – monitoring API response times. This aligns with capability modeling by focusing on measuring performance against defined requirements (the SLA) and using data to understand the root cause of the delay within the 'Inventory Management' capability. Options A and B represent reactive, potentially inefficient solutions; option C is appropriate but doesn't specifically connect to the core principles of capability analysis, while option D shifts blame without diagnosing the underlying problem.
Frequently Asked Questions
What does the "Capability Modeling Vocabulary — Enterprise Architecture English Exercise" exercise cover?
Practice English for business capability modeling: capability maps, heat maps, gap analysis, and capability maturity language. 5 exercises.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
How many questions are in "Capability Modeling Vocabulary — Enterprise Architecture English Exercise"?
This exercise has 45 questions. Each one gives instant feedback with an explanation, so you can see exactly why an answer is right or wrong.
Do I need to create an account to save my progress?
No account is required. The progress bar and score are tracked in your browser for the current session -- the exercise is designed to be a quick, repeatable drill rather than something you resume later.
What happens if I get an answer wrong?
You'll see the correct answer highlighted immediately, along with a short explanation of why it's correct. Wrong answers aren't penalized beyond your score, and you can keep going through every question.
How is this exercise different from reading an article?
Articles explain vocabulary and concepts through prose, while exercises like this one are interactive drills -- multiple-choice questions -- that test and reinforce your recall of specific terms and phrasing.
Can I retry this exercise?
Yes -- use the "Try again" button on the results screen to reset your score and go through all the questions again from the start.
Where can I find more Enterprise Architecture Language exercises?
Browse the full Enterprise Architecture Language hub for related drills, or check the site-wide exercises index for other IT English topics.
Is this exercise suitable for beginners?
This exercise assumes basic familiarity with IT terminology. If a term feels unfamiliar, check the site Glossary for a plain-English definition before attempting the questions.
How often is new content like this published?
New exercises are added regularly across all categories, alongside new vocabulary sets and articles. Check back on the exercises hub to see what's new.