Skip to content

Quiz: Business Services and IT Portfolio Management

Test your understanding of business and technical services, portfolio management, technical debt, SLAs, and system integration with these review questions.

1. Which characteristic most clearly distinguishes a business service from a technical service?

  1. Business services are managed by IT departments, while technical services are managed by external vendors and cloud providers
  2. Business services are customer-visible capabilities that deliver direct business value, while technical services are internal IT capabilities consumed by other services rather than end users
  3. Business services require SLA agreements, while technical services operate on a best-effort basis without formal commitments
  4. Business services run in production environments, while technical services run only in development and staging environments for testing purposes
Show Answer

The correct answer is B. The defining characteristic of a business service is customer or business-user visibility—capabilities like "Online Banking" or "Order Processing" that directly deliver value and are meaningful to non-technical stakeholders. Technical services like "Authentication Service" or "Notification Hub" are internal capabilities consumed by other applications and services, not directly by end users. This distinction determines ownership, communication style, and impact reporting during incidents.

Concept Tested: Business Service

2. An organization wants to report the financial impact of a database server failure to executives. Which capability provided by graph-based business service mapping makes this possible?

  1. The graph database stores financial data alongside infrastructure data, enabling cost queries on any infrastructure component
  2. Graph traversal from the failed infrastructure component upward through applications and technical services to business service nodes retrieves the revenue impact and customer count properties stored on those business services
  3. Business service mapping requires a separate financial system integration that calculates impact independently of the graph database
  4. Graph databases automatically calculate financial impact by counting the number of nodes affected and multiplying by a standard cost-per-node metric
Show Answer

The correct answer is B. Business service nodes in the graph carry properties like revenue_impact_per_hour and customer_count. When a database fails, graph traversal follows dependency relationships upward—from the database through applications and technical services to the business service nodes at the top. The financial impact properties stored on those business service nodes can then be aggregated and reported. This traversal happens in milliseconds, enabling real-time business impact reporting during incidents.

Concept Tested: Business Service Mapping

3. In the Application Portfolio Management (APM) quadrant framework, an application assessed as high business value but low technical quality would be classified in which category?

  1. INVEST — because high business value justifies continued investment regardless of technical quality
  2. RETIRE — because low technical quality indicates the application should be decommissioned
  3. MIGRATE — because the application is worth preserving but needs re-platforming or modernization
  4. TOLERATE — because the combination of high value and low quality requires accepting the status quo until resources become available
Show Answer

The correct answer is C. MIGRATE indicates an application with high business value that justifies investment but requires modernization due to poor technical quality. The application is too valuable to retire but too problematic to keep as-is. Migration efforts might include re-platforming on modern infrastructure, refactoring the codebase, or replacing it with a modern equivalent that preserves the business capability while improving technical health.

Concept Tested: Application Portfolio

4. Why do graph databases provide a significant advantage over traditional spreadsheet-based tools for application portfolio rationalization decisions?

  1. Graph databases support more columns and rows than spreadsheets, enabling larger inventories to be stored without performance degradation
  2. Graph databases automatically generate executive dashboards without requiring manual report creation from raw data
  3. Graph databases capture dependency relationships between applications, so rationalization decisions account for the impact of retiring or migrating an application on all dependent systems
  4. Graph databases are faster than spreadsheets at sorting and filtering large lists of applications by cost or business value
Show Answer

The correct answer is C. The critical advantage of graph-based portfolio management is dependency awareness. A spreadsheet might identify an application as a "retire" candidate based on low value and poor quality, but a graph traversal may reveal it has 30 downstream dependents. Retiring it requires migrating all those dependents first—a multi-year program, not a simple decommission. Without dependency context, portfolio decisions are frequently wrong; with graph-based dependency analysis, they are grounded in complete impact understanding.

Concept Tested: Application Portfolio

5. Technical debt is described using a financial metaphor. What does the "interest" on technical debt represent in an IT context?

  1. The annual software licensing costs for outdated applications that have not been upgraded to current versions
  2. The ongoing productivity costs of working with suboptimal code and systems—slower development velocity, higher defect rates, increased maintenance effort, and greater outage frequency
  3. The depreciation expense recorded on balance sheets for capitalized software assets that decline in value over time
  4. The interest charges paid to vendors when software maintenance contracts are renewed late or allowed to lapse
Show Answer

The correct answer is B. The technical debt metaphor maps financial debt concepts to IT: the principal is the accumulated shortcuts and deferred work, while the "interest" is the ongoing cost of living with that debt. Every sprint, teams pay interest by working slower in the tangled codebase, spending more time fixing bugs, dealing with outages from fragile integrations, and struggling with security vulnerabilities. This interest compounds over time, eventually making the system nearly impossible to change—the "debt crisis" equivalent of bankruptcy.

Concept Tested: Technical Debt

6. An organization's Online Banking business service promises 99.95% uptime (SLA). It depends on four technical services, each with a 99.9% uptime SLA. What does composite SLA analysis reveal about this situation?

  1. The composite uptime of four 99.9% components is 99.6%, which is lower than the promised 99.95% business service SLA—indicating an SLA gap that risks breach
  2. The composite uptime is always equal to the lowest individual component SLA, so 99.9% composite matches the business service SLA closely enough
  3. The composite uptime is the average of all component SLAs, so four components at 99.9% produces a composite of 99.9%, close enough to the 99.95% target
  4. The composite uptime equals the highest component SLA, so the best-performing component at 99.9% determines the achievable business service uptime
Show Answer

The correct answer is A. Composite SLA is calculated by multiplying the individual component uptimes: 0.999 × 0.999 × 0.999 × 0.999 ≈ 0.996, or 99.6% uptime. This is significantly lower than the promised 99.95%, representing roughly 4× more downtime than the business SLA allows. Graph-based SLA analysis reveals this gap before it causes customer-visible breaches, enabling organizations to either improve component reliability through redundancy or renegotiate business SLAs to reflect technical reality.

Concept Tested: Service Level Agreement

7. Which of the following best describes the "digital estate" concept in modern IT management?

  1. The physical real estate (data centers, office buildings, server rooms) owned or leased by an organization to house IT infrastructure
  2. The complete inventory of all digital resources controlled by an organization, including applications, servers, cloud services, SaaS subscriptions, licenses, and IoT devices across all environments
  3. The portion of an organization's IT portfolio that has been fully digitized from paper-based processes and is now managed electronically
  4. The set of digital intellectual property assets including software source code, proprietary algorithms, and patented technologies developed internally
Show Answer

The correct answer is B. The digital estate is the comprehensive inventory of all digital resources regardless of where they live (on-premises, cloud, SaaS) or how they were acquired (IT-managed, business-purchased, contractor-managed). It goes beyond traditional IT asset management to encompass cloud consumption, SaaS subscriptions, and IoT devices that may sit outside traditional IT governance. Managing the full digital estate is critical for security (no untracked attack surfaces), cost optimization, and strategic planning.

Concept Tested: Digital Estate

8. Why does integration complexity grow exponentially rather than linearly as the number of systems in an enterprise increases?

  1. Integration software becomes increasingly complex to configure as more systems are added, requiring exponentially more administrative work per integration
  2. The number of potential point-to-point integration pairs follows a combination formula (n×(n-1)÷2), so doubling systems from 10 to 20 more than quadruples the potential integration points from 45 to 190
  3. Integration middleware servers reach capacity limits as traffic increases, requiring exponentially more hardware investment to support additional systems
  4. Integration protocols become increasingly incompatible as more systems are added, requiring exponentially more translation and transformation logic
Show Answer

The correct answer is B. With n systems, the number of possible point-to-point integration pairs is n×(n-1)÷2. With 10 systems this is 45 integrations; with 20 systems it's 190 integrations; with 100 systems it's 4,950 integrations. This combinatorial explosion is why architectural patterns like API gateways, service meshes, and event buses are critical—they replace point-to-point connections with hub-and-spoke or event-driven patterns that scale more manageably as system count grows.

Concept Tested: System Integration

9. A legacy system runs critical payroll processing but was last updated 8 years ago, uses a technology platform no longer supported by its vendor, and is understood by only two employees approaching retirement. What graph-based query metric would most effectively flag this system as high priority for risk mitigation?

  1. The number of rows in its associated database tables, which indicates how much data would need to be migrated during modernization
  2. A composite risk score combining technology age, expert scarcity, vendor support status, and the number of critical business services depending on it
  3. The system's annual maintenance cost compared to the average cost of applications in the same business unit
  4. The number of API endpoints the system exposes, which determines how difficult integration with a replacement system will be
Show Answer

The correct answer is B. A composite legacy risk score combining multiple risk dimensions provides the most actionable signal. Technology age and vendor support loss indicate increasing security and operational risk. Expert scarcity (knowledge concentration in two employees) creates a "key person risk" where those employees' departure or unavailability could make the system unmodifiable. The number of dependent business services determines the blast radius of failure. This multi-factor scoring, computable via graph queries, prioritizes the systems most likely to cause catastrophic business disruption.

Concept Tested: Legacy System

10. A technical service has 15 different business applications calling it—all with different SLA requirements. How should this influence the SLA set for the technical service itself?

  1. The technical service SLA should match the average of all 15 calling applications' SLAs to balance cost and performance requirements fairly across consumers
  2. The technical service SLA must equal or exceed the most demanding consumer's SLA requirement, since all consumers depend on it and the weakest link determines the achievable service level
  3. The technical service does not need a formal SLA because only business-facing services require SLA commitments for customer accountability
  4. The technical service SLA should be set at the lowest consumer's SLA requirement to minimize operational cost and investment in the shared component
Show Answer

The correct answer is B. A shared technical service must meet the SLA requirements of its most demanding consumer. If the technical service has lower availability than one of its consumers promises to their end users, that consumer will inevitably breach their SLA whenever the technical service fails. Graph analysis of all consumers and their SLA requirements reveals the highest common requirement that the technical service must achieve—and may justify investment in redundancy or performance improvements to meet that requirement across all 15 consumers.

Concept Tested: Technical Service