CIS-APM Practice Questions

For effective cost management, applications should be categorized in a way that facilitates strategic financial decisions. Grouping applications by their business value (how critical they are to the business) and their lifecycle stage (e.g., new, stable, or end-of-life) provides a powerful framework. This approach, often aligned with the TIME model (Tolerate, Invest, Migrate, Eliminate), allows an organization to identify low-value, high-cost applications for retirement and justify investment in high-value applications, thereby optimizing overall IT spend.

A. Categorizing by regulatory compliance is primarily for risk and legal management, not the most direct method for optimizing costs across the portfolio.

B. Grouping by support contracts is too granular and operational; it doesn't provide the strategic business context needed for effective cost management decisions.

D. Grouping by user location is a logistical categorization that is generally irrelevant to an application's intrinsic value or its associated costs.

1. ServiceNow Product Documentation. (2024). Application rationalization. "Rationalize applications by using the information gathered in the assessment process and categorizing them in the APM portal... The assessment is based on the business value, cost, usage, and risk of the application."

2. ServiceNow Product Documentation. (2024). Application category. "Application categories are used to group business applications for evaluation and analysis... You can create your own categories based on the TIME model." The TIME model explicitly uses business value and technical fit to guide investment/divestment decisions.

To assess an application's overall health and its contribution to the organization, APM utilizes a multi-dimensional approach. Categorizing applications by both their technical health (e.g., architecture, stability, maintainability) and their business value (e.g., criticality, usage, financial performance) provides a holistic view. This two-axis model, often visualized in a bubble chart, allows portfolio managers to identify which high-value applications are in poor technical health (and need investment) and which low-value, unhealthy applications are candidates for retirement. This method is fundamental to the APM rationalization process.

A. Categorizing by business criticality alone assesses an application's importance but ignores its technical condition, providing an incomplete picture for health assessment.

C. Application license cost is a financial metric; it does not provide any insight into the technical stability, performance, or architectural soundness of the application.

D. End-user feedback measures user satisfaction or functional fit, which is a component of business value, but it does not directly assess the underlying technical health.

1. ServiceNow Product Documentation. Application rationalization. This section describes using indicators for business value, technical risk, and cost to evaluate applications. The combination of these factors, including technical health, is key.

2. ServiceNow Product Documentation. APM portal and dashboards. The documentation describes the "Application 4-quadrant analysis" bubble chart, which plots applications based on their technical score and business value score to aid in decision-making.

3. ServiceNow Community. (2021). APM Fundamentals. Section: "Application Assessment." This training material explains that assessments are based on indicators grouped into categories like Business Value, Technical Risk, and Cost.

Hardware Asset Management (HAM) tracks the entire lifecycle of hardware assets, from procurement to disposal. This includes critical data points like purchase date, warranty expiration, end-of-support, and end-of-life dates. This Hardware Lifecycle information is a direct input into APM's technical risk assessment. An application running on aging, unsupported, or out-of-warranty hardware poses a significant technical risk to the business. APM uses this data to make informed decisions, such as planning to migrate the application to new infrastructure or retiring it.

A. Software Lifecycle. This information is provided by Software Asset Management (SAM), which focuses on software entitlements, compliance, and end-of-life dates for software, not hardware.

B. Business Capability. This is a concept from business architecture that describes what a business does; it is mapped to applications within APM, not provided by HAM.

C. Application Capability. This describes what an application can do (its features/functions) and is not information that originates from the HAM process.

1. ServiceNow Product Documentation. (2023). Hardware Asset Management. "Manage the physical, financial, and contractual aspects of your hardware assets throughout their lifecycle." Section: Hardware Asset Management.

2. ServiceNow Product Documentation. (2023). Technology Portfolio Management. "TPM gives you visibility into your technologies and their lifecycles... Use this information to assess the risk of business applications that run on a specific technology." TPM integrates HAM and SAM data for this purpose. Section: Technology Portfolio Management.

3. ServiceNow Common Service Data Model (CSDM) 4.0 White Paper. (2022). The model illustrates the relationship between Business Applications, Application Services, and the underlying Hardware CIs (cmdbcihardware). Lifecycle data on the hardware CI directly impacts the risk profile of the application. p. 25, "Manage Technical Services" Domain.

Architectural Artifacts in APM are the collection of design documents, models, and diagrams that describe an application's structure, behavior, and integration with other systems. This includes solution architecture diagrams, data flow diagrams, and technical specifications. They are critical because they provide the necessary context for evaluating an application's technical health, its alignment with enterprise architecture standards, and its ability to support business processes. This information is essential for making strategic decisions regarding application modernization, consolidation, or retirement.

A. Network configurations are a type of artifact, but this option is too specific and doesn't cover the full scope.

C. Historical performance records are operational data used for monitoring, not design documents that define the architecture.

D. Data logs are raw, operational outputs from systems, not the formal documentation that constitutes architectural artifacts.

1. ServiceNow Product Documentation. (2023). Application Portfolio Management. "Manage technology portfolio". "Store and manage architectural artifacts, such as solution designs and diagrams, to support architectural reviews and decision-making."

2. The Open Group. (2018). The TOGAF® Standard, Version 9.2. Part IV: Architecture Content Framework, Section 35.2, "Artifacts". This standard, foundational to enterprise architecture, defines artifacts as work products describing an aspect of the architecture, including catalogs, matrices, and diagrams.

The Application Portfolio Management (APM) maturity model begins with establishing a foundational inventory. Level 1, "Applications Under Management," is characterized by creating a comprehensive, single system of record for all business applications and assigning clear ownership. The scenario described, where the company has achieved these two specific goals, perfectly aligns with the definition of this initial maturity level. They have not yet progressed to assessing or rationalizing the portfolio, which occurs in subsequent levels.

B. Level 2: Basic Rationalization: This level involves assessing applications against criteria like business value and technical risk, which is not mentioned in the scenario.

C. Level 3: Advanced Rationalization: This level uses deeper integrations and data for strategic alignment and roadmapping, far beyond the described state.

D. Level 4: Continuously Optimized Portfolio: This is the highest level, focusing on continuous improvement and proactive management, which the company has not yet reached.

ServiceNow Product Documentation, "Application Portfolio Management," Doc ID: apm-release-notes, Section: "APM guided setup." The guided setup for APM implementation follows the maturity model, starting with "Categorize and assess" which requires a complete inventory (Level 1) as a prerequisite.

ServiceNow Product Documentation, "APM maturity model," Doc ID: cAPMMaturityModel, Section: "Level 1: Inventory." This section explicitly states, "The first step is to create a comprehensive inventory of all business applications and establish ownership."

In the context of an APM Maturity Model, a "Mature" or "Optimized" level signifies a shift from reactive, project-based activities to a proactive, institutionalized process. Continuous improvement of the application landscape is the hallmark of this stage. It involves ongoing monitoring, regular portfolio reviews, and dynamic adjustments based on changing business needs and technology landscapes. This contrasts with lower maturity levels, which are characterized by initial inventory creation, manual analysis, and one-time rationalization efforts. A mature practice integrates APM into the organization's core strategic planning and governance cycles.

A. Automating decommissioning for all applications is impractical and risky; strategic, case-by-case decisions are a sign of maturity.

C. Relying on manual analyses is characteristic of lower maturity levels; mature organizations leverage automation and integrated data.

D. Identifying legacy applications is a foundational APM activity, typically accomplished at earlier stages of maturity.

1. ServiceNow. (2022). Application Portfolio Management (APM) Maturity Model White Paper. "At the highest level of maturity (Optimized), the organization engages in continuous portfolio optimization. APM is embedded in enterprise architecture and strategic planning, enabling proactive and continuous improvement." (ServiceNow White Paper WP-APM-Maturity-Model, p. 5).

2. The Open Group. (2018). TOGAF® Standard, Version 9.2. In the Architecture Capability Maturity Model, higher levels emphasize "a focus on continuous improvement" and having a "managed and measured process." (The Open Group Library, C182, Section 48.6, Architecture Capability Maturity Model).

In Application Portfolio Management, applications are often assessed using a model like TIME (Tolerate, Invest, Migrate, Eliminate). When an application is placed in the "Retire" or "Eliminate" category, it signifies that the application has low business value and/or high cost/risk, making it a candidate for removal from the portfolio. The immediate and logical next action is to create and execute a plan for decommissioning the application, which involves retiring the technology, archiving necessary data, and redirecting users to alternative solutions.

A. Investing in development is the opposite action, reserved for applications with high business value that are worth enhancing.

B. Migrating to the cloud is an action for applications that are valuable but may benefit from a more modern infrastructure, not for those being retired.

D. Reassigning an application does not solve the underlying issues of low value or high cost that led to the "Retire" classification.

1. ServiceNow Product Documentation. "Application rationalization". ServiceNow, Release: Washington DC. Accessed May 2024. (This section explains that the outcome of categorizing an application for elimination is to plan its retirement).

2. ServiceNow Product Documentation. "Demand and project creation in APM". ServiceNow, Release: Washington DC. Accessed May 2024. (This page describes creating demands or projects from APM, including "decommissioning projects" for applications marked for retirement).

ServiceNow APM is fundamentally integrated with the Common Service Data Model (CSDM). APM populates and utilizes key configuration item (CI) classes within the CSDM's "Design" and "Manage Technical Services" domains. Specifically, it manages the "Business Application" [cmdbcibusinessapp] CI class, which represents a piece of software used by the business. APM then extends the model by creating relationships between these Business Applications and other CSDM elements like Business Capabilities and Application Services [cmdbciserviceauto]. This provides the essential business context to the technical CIs managed in the CMDB.

B. APM uses existing CSDM tables; it does not automate the creation of the core CSDM framework itself.

C. This is factually incorrect; APM is a primary consumer and populator of key data constructs within the CSDM framework.

D. While APM provides context that benefits ITOM and ITSM, its direct interaction is with the data model (CSDM), not consolidating workflows.

1. ServiceNow White Paper. (2023). CSDM 4.0: A CMDB Framework for the Digital Age. This document explicitly places Business Application, a core APM element, within the Design domain of the CSDM framework. Figure 3: CSDM Conceptual Model.

2. ServiceNow Product Documentation. (2024). Application Portfolio Management and CSDM. "Application Portfolio Management (APM) uses data from the CSDM framework... The business application table [cmdbcibusinessapp] is the central CI of APM." Section: How APM uses CSDM.

Application Categorization is a foundational process in APM that involves grouping applications based on multiple dimensions, not just one. This structured classification provides a holistic view, enabling IT leaders to understand how each application contributes to business objectives (business value) and its operational stability and sustainability (technical health). This comprehensive insight is crucial for making strategic decisions about resource allocation, modernization efforts, and retirement, thereby aligning IT investments directly with business priorities.

A. It automates the application deployment process.

This is incorrect. Categorization is an analytical process for decision support, distinct from deployment automation tools like CI/CD pipelines.

B. It allows IT teams to categorize applications based on performance metrics alone.

This is incorrect. Effective categorization uses a multi-criteria approach, including business value, cost, risk, and user satisfaction, not just performance.

D. It reduces the need for application updates.

This is incorrect. Categorization often highlights applications that are technically obsolete and in critical need of updates or replacement.

1. ServiceNow Product Documentation. (2024). Application Portfolio Management. "Group and categorize your business applications to get a comprehensive list of your applications. You can assess the applications based on the scores that you derive from the information that you provide in the business application form." Section: Application categorization.

2. ServiceNow Product Documentation. (2024). Assess an application. "You can assess an application to evaluate its business value, cost, and risks. The assessment helps you to decide whether to invest, sustain, or replace the application."

3. Johansson, B., & Wiberg, M. (2011). Application portfolio management: a systematic literature review. In ECIS 2011 Proceedings. Paper 188. This review discusses how APM frameworks categorize applications to support investment and rationalization decisions based on business value and technical condition.

System architecture diagrams are specifically designed to visually represent the components of a system and their interrelationships. In the context of APM, these diagrams are essential for illustrating how business applications connect to each other and to the underlying infrastructure components like servers, databases, and networks. This visualization is critical for impact analysis, identifying dependencies for migration planning, and understanding potential points of failure. Other options listed are financial or qualitative and do not depict technical structure.

A. Financial reports

This is incorrect. Financial reports provide cost data but do not illustrate the technical connections between systems.

B. Application cost analysis

This is incorrect. This is a financial artifact focused on the total cost of ownership, not the technical architecture or dependencies.

D. End-user satisfaction surveys

This is incorrect. These surveys provide qualitative feedback on user experience, not a visualization of technical infrastructure dependencies.

1. ServiceNow Product Documentation. (2024). Application Portfolio Management. The APM module integrates with the CMDB and dependency mapping features. "Use dependency views to see the infrastructure that supports an application service." This dependency view is a form of system architecture diagram.

2. Lankhorst, M. (2013). Enterprise Architecture at Work: Modelling, Communication and Analysis (3rd ed.). Springer. Chapter 5, "The Architecture Viewpoints and Views," explains how architecture diagrams (views) are used to communicate the structure and dependencies of systems to different stakeholders.

3. MIT OpenCourseWare. (2016). 15.571 The Corporation in the Age of Information Technology, Fall 2016. Lecture notes on Enterprise Architecture emphasize using diagrams to map applications to technology infrastructure to manage complexity and dependencies.