The SAP LeanIX SaaS Discovery feature, part of the SaaS Management Platform (SMP), is designed to automatically identify all Software-as-a-Service (SaaS) applications being used across an organization. It achieves this by integrating with key enterprise systems such as financial, HR, and Single Sign-On (SSO) providers. The primary goal is to create a comprehensive, real-time inventory of the entire SaaS landscape, including unsanctioned "shadow IT." Once discovered, these applications can be linked to the SAP LeanIX Enterprise Architecture workspace for governance, cost optimization, and risk management within the overall IT landscape.

B. This describes a platform update or a continuous deployment process for the SAP LeanIX application itself, not the function of discovering other SaaS applications used by the organization.

C. SaaS Discovery identifies the applications (the technical asset), not the abstract business capabilities they support. Mapping discovered applications to business capabilities is a subsequent enterprise architecture management activity.

1. SAP Help Portal

SAP LeanIX SaaS Management Platform

"Discover" section. The documentation states

"The Discover module in SMP provides a comprehensive overview of all SaaS applications used within your organization... It integrates with various systems like financial

HR

and single sign-on (SSO) to automatically identify SaaS subscriptions and usage." This confirms the function of discovering applications.

2. SAP LeanIX Official Product Documentation

"SaaS Management" page. The product overview highlights the core capability: "Automatically discover all SaaS applications—including shadow IT—to create a single source of truth." This directly supports the purpose of discovering applications

not code updates or business capabilities.

On-the-fly creation in SAP LeanIX refers to the functionality that allows a user to create a new Fact Sheet directly from a relation field within an existing Fact Sheet. When a user needs to establish a link to a Fact Sheet that does not yet exist, they can type the name of the new entity in the relevant field and create it instantly, without navigating away from their current screen. This process streamlines data entry and ensures that the data model can be populated contextually and efficiently as information becomes available. The new Fact Sheet is created and the relation to it is established simultaneously.

B. The real-time creation of fields: This is incorrect. Creating fields is an administrative action that modifies the data model itself and is not a standard user function performed "on-the-fly" during data entry.

C. Relations being created and deleted in real-time: This is too general. While relations are managed in real-time, the specific term "on-the-fly creation" refers to the creation of a new Fact Sheet object, not just the relation itself.

D. The process of duplicating existing section or fact sheet types: This describes cloning or templating, which are administrative configuration tasks, not a dynamic method for creating new Fact Sheet instances during regular use.

1. SAP Help Portal - SAP LeanIX Application Portfolio Management: In the section describing how to manage data

the documentation explicitly states: "To add a relation

go to the corresponding relation field... If the Fact Sheet you want to link to does not exist yet

you can create it on the fly. Simply type the name of the new Fact Sheet and click on the Create option."

Source: SAP Help Portal

SAP LeanIX

User and Administration Guide

"Working with Fact Sheets"

subsection "Create Relations".

2. SAP Learning - LIXFND SAP LeanIX Foundation Courseware: The foundational training materials for SAP LeanIX introduce core concepts for users. The module on "Fact Sheet Fundamentals" demonstrates the process of creating a new Fact Sheet from within an existing one as a key efficiency feature

referring to it as on-the-fly creation.

Source: SAP Learning Hub

Course LIXFND

Unit: "Working with Fact Sheets".

In the context of Enterprise Architecture (EA), an application is a logical construct that serves as a crucial link between business strategy and IT infrastructure. Its fundamental purpose is to automate processes and deliver functionality that supports business capabilities (D). To perform its function, any application is inherently dependent on and relies on IT components (B) such as servers, databases, and operating systems for execution and data storage. These two characteristics define the application's role and dependencies within the layered EA framework.

A. Clear technical ownership: This is an essential governance attribute for managing an application effectively, but it is not an intrinsic characteristic of the application itself. An application can exist without clear ownership.

C. Provides hosting information: Hosting information is metadata describing an application's deployment instance (e.g., on-premise, cloud). It is an attribute about the application, not a fundamental characteristic of what it is.

1. SAP LeanIX Documentation: The LeanIX data model explicitly defines these relationships. The Application Fact Sheet is designed to be linked to Business Capabilities (via a "supports" relation) and to IT Components (via a "requires" relation)

illustrating these core characteristics.

Source: SAP LeanIX User Documentation

"Fact Sheet types"

Section on Application Fact Sheet relations.

2. The Open Group Architecture Framework (TOGAF) Standard

Version 10: The TOGAF standard

a foundational EA methodology

defines the Application Architecture domain as the bridge between Business and Technology Architectures. It describes applications as supporting business processes and being deployed on technology infrastructure.

Source: The TOGAF Standard

10th Edition

Part II: TOGAF Architecture Development Method (ADM)

Chapter 9: Phase C: Application Architecture. This chapter details how applications are defined to support business activity.

3. University Courseware - MIT Sloan School of Management: In established EA literature taught at institutions like MIT

applications are consistently positioned in a middle layer that serves the business layer and is supported by the technology layer.

Source: Weill

P.

& Ross

J. W. (2009). Enterprise Architecture as Strategy: Creating a Foundation for Business Execution. Harvard Business Review Press. Chapter 2

"The Foundation for Execution

" describes the core diagrams of EA

which visually represent applications supporting business processes and running on technology infrastructure.

The Quality Seal feature in SAP LeanIX is a core component of its data governance framework. Its purpose is to establish a formal review and approval workflow for Fact Sheets. This ensures that the information is accurate, complete, and current. By assigning clear roles and responsibilities (e.g., Accountable, Responsible), the process promotes accountability and encourages stakeholders to collaborate on maintaining high-quality data. The seal visually indicates the quality status of a Fact Sheet (e.g., Approved, In Review), which builds trust in the enterprise architecture repository and supports a rigorous, yet collaborative, governance model.

B. This is incorrect because the Quality Seal process does not inherently restrict all modifications. Instead, it manages changes by requiring a re-approval to maintain the "Approved" status, ensuring quality control.

C. This is incorrect because the Quality Seal represents the outcome of a deliberate, manual review and approval workflow by designated stakeholders. It is the opposite of an automatic approval system.

1. SAP Help Portal - SAP LeanIX Documentation

"Fact Sheet Quality Seal": "The Quality Seal feature in SAP LeanIX helps you to establish a governance process for your Fact Sheets. It allows you to define a workflow for reviewing and approving Fact Sheets... This process promotes accountability and collaboration

as stakeholders are clearly defined and involved in the data validation process." (This source directly supports the concepts of a governance process

clear responsibilities

and collaboration mentioned in option A).

2. SAP LeanIX Documentation

"Data Governance & Quality": "With the Quality Seal

you can define a process for how Fact Sheets are approved. This ensures that only high-quality

verified information is used for decision-making... It assigns clear ownership and facilitates a collaborative approach to data maintenance." (This reference reinforces that the feature is about a defined process

quality verification

ownership

and collaboration

aligning perfectly with answer A).

In the SAP LeanIX data governance model, the Application Owner is the individual primarily responsible for the business-related aspects of an application. A key responsibility is to assess the application's "Functional Fit," which evaluates how well the application's features and functions meet the current and future needs of the business. This assessment is crucial for making informed decisions within Application Portfolio Management (APM), such as whether to invest in, maintain, or retire an application.

B. Developing an IT strategy is a high-level, strategic task typically performed by senior IT leadership, such as the CIO or Chief Enterprise Architect, not individual application owners.

C. Managing the technical implementation and maintenance of application integrations is the responsibility of solution architects, integration specialists, or development teams.

D. Documenting technical IT performance, such as server uptime or response times, is a function of IT operations or infrastructure management teams.

1. SAP Help Portal

SAP LeanIX Documentation

"Assess Your Applications": This section details the process of evaluating applications based on metrics like Functional Fit and Technical Fit. It implicitly and explicitly assigns the responsibility for business-related assessments

such as Functional Fit

to the business or application owners who have the most profound knowledge of the application's value to the business.

Reference: SAP Help Portal

SAP LeanIX

"Application Portfolio Management

" section on "Assess Your Applications."

2. SAP Help Portal

SAP LeanIX Documentation

"Subscriptions and Notifications": The documentation on subscriptions defines roles like "Responsible" or "Accountable

" which are typically fulfilled by the Application Owner. This role is tasked with maintaining the accuracy and completeness of the Fact Sheet data

which includes core assessment fields like Functional Fit.

Reference: SAP Help Portal

SAP LeanIX

"Getting Started

" section on "Fact Sheet Subscriptions and Notifications."

SAP LeanIX uses a standard Application Portfolio Management (APM) methodology to assess the health and value of applications. The two primary, default attributes for this assessment are Functional Fit and Technical Fit. Functional Fit evaluates how well an application supports business capabilities and user needs. Technical Fit assesses the quality of the underlying technology, considering aspects like maintainability, scalability, and alignment with architectural standards. Together, these two dimensions form the basis for the TIME (Tolerate, Invest, Migrate, Eliminate) model, a core feature for strategic application portfolio decisions within SAP LeanIX.

A. Operational fit: While a relevant concept, "Operational Fit" is not a standard, default assessment attribute in SAP LeanIX; its aspects are typically covered under Functional Fit or Business Criticality.

D. IT health score: This is typically a calculated or aggregated metric derived from other primary attributes like Functional and Technical Fit, not a default input attribute itself.

1. SAP Help Portal - SAP LeanIX Documentation: In the section on Application Portfolio Management

the core assessment methodology is described. It states

"The assessment is based on two dimensions: Functional Fit and Technical Fit. These dimensions are used to categorize applications in the Application Portfolio matrix..."

Source: SAP Help Portal

SAP LeanIX

Application Portfolio Management

"Assess Your Application Portfolio".

2. SAP LeanIX Product Documentation - Data Model: The official data model for the Application Fact Sheet lists "functionalFit" and "technicalFit" as default fields within the assessment section.

Source: SAP LeanIX Developer Documentation

"Data Model

" Section: Fact Sheet Types > Application.

3. University Courseware on Enterprise Architecture: Enterprise Architecture frameworks taught in academic settings often use a two-dimensional matrix for portfolio analysis. The most common axes are business value (or functional fit) and technical condition (or technical fit)

which aligns directly with the SAP LeanIX default model.

Source: MIT Sloan School of Management

Course 15.571 "The Corporation in the 21st Century

" Lecture Notes on IT Portfolio Management.

SAP LeanIX dashboards serve as personalized home pages, allowing users to monitor key metrics and access relevant information. A core function is the ability to customize these dashboards by adding, removing, and arranging panels. These panels are essentially embedded reports, charts, or other data visualizations that provide insights into the enterprise architecture. Therefore, users can both view embedded reports and customize their own dashboards to fit their specific needs and roles, making these the primary available options.

A. Creating new report types: This is an administrative or developer-level function. Standard users can create new reports from existing types, but they cannot create entirely new report types from the dashboard interface.

D. Changing dashboard views automatically: This feature, such as a slideshow or automatic rotation of views, is not a standard, documented capability of the SAP LeanIX dashboard functionality for end-users.

1. SAP Help Portal

SAP LeanIX Enterprise Architecture

Dashboards: "Dashboards are configurable home pages in LeanIX. You can configure your own dashboards to get a personalized overview of the data that is most relevant to you... You can add panels to a dashboard to display reports

saved searches

factsheet subscriptions

and more." This source directly supports the ability to customize dashboards (C) and view embedded reports as panels (B).

2. SAP Help Portal

SAP LeanIX Enterprise Architecture

Reporting: This section details how users can access and create reports based on predefined types. It distinguishes between using existing report types and the administrative setup of these types

implicitly confirming that creating new types is not a standard user dashboard function (making A incorrect). The documentation does not mention any feature for automatically changing dashboard views (making D incorrect).

The IT Component fact sheet in the SAP LeanIX data model is used to represent technology elements. These elements are broadly classified into categories such as Software, Hardware, or Service. Each category has more specific subtypes. 'SaaS' (Software as a Service) is a standard subtype for the Software category, describing a software delivery model. 'Server' is a standard subtype for the Hardware category, representing a specific type of physical or virtual equipment.

B. Business process: This is a distinct, top-level fact sheet type within the SAP LeanIX meta-model, used to describe business operations, not a subtype of a technology element.

D. Hardware: This is a high-level category for an IT Component, not a specific subtype. Subtypes under the Hardware category are more granular, such as 'Server', 'Storage', or 'Network Device'.

1. SAP Help Portal - SAP LeanIX: Fact Sheet Types. The official documentation outlines the standard data model. The "IT Component" section details its purpose and structure

listing 'Software' and 'Hardware' as categories. It provides 'SaaS' as an example subtype for Software and 'Server' as an example subtype for Hardware. The "Business Process" is documented as a separate

distinct fact sheet type. (Accessed via SAP Help Portal for SAP LeanIX documentation).

2. LeanIX GmbH (Now part of SAP): The LeanIX Poster for Enterprise Architects. This official resource visually represents the meta-model

clearly distinguishing between the Business Capability

Process

User Group

Application

IT Component

and Project fact sheets. It shows that IT Components can be of type Software or Hardware

with subtypes like Server being part of the model. (This poster is a standard reference provided by the vendor).

The To-Do feature in SAP LeanIX is specifically designed to create and assign actionable tasks related to a fact sheet. Users can create a To-Do for a specific person (e.g., the responsible subscriber) to request an update, provide missing information, or clarify a data point. This allows for a formal, trackable request for change without the user directly altering the fact sheet's content. The feature includes statuses (Open, In Progress, Done) and deadlines, making it an effective tool for managing data quality and governance workflows.

A. Comments: Comments are used for general discussion and collaboration on a fact sheet. While a user could suggest an update in a comment, it is not a formal, trackable task and may be overlooked.

B. Quality Seal: The Quality Seal is a mechanism to certify the review status and data quality of a fact sheet (e.g., 'Approved', 'In Review'). It does not allow users to propose changes.

D. Surveys: Surveys are designed for collecting data from multiple stakeholders in a structured manner, often to populate or update many fact sheets at once, not for proposing a specific, ad-hoc update on a single fact sheet.

1. SAP Help Portal - SAP LeanIX Documentation

"To-Dos": "To-Dos are a powerful feature in LeanIX to create and assign tasks related to Fact Sheets. They are particularly useful for data quality management

enabling you to ask colleagues to provide or update information." This source directly validates that To-Dos are the mechanism for requesting updates.

2. SAP Help Portal - SAP LeanIX Documentation

"Collaboration and Notification Features": This section details the different collaboration tools. It distinguishes between Comments for discussion and To-Dos for actionable tasks

clarifying their distinct purposes.

3. SAP Help Portal - SAP LeanIX Documentation

"Fact Sheet Quality Seal": This document explains that the Quality Seal's purpose is to "establish a clear process for reviewing and approving the quality of your Fact Sheets

" confirming it is a status indicator

not a change proposal tool.

A solid business capability model is fundamental to enterprise architecture in SAP LeanIX because it serves as the primary bridge between business strategy and IT execution. It provides a stable, high-level view of what the business does, creating a common language that both business and IT stakeholders can understand (A). This shared understanding is crucial for collaboration. By mapping applications, projects, and technologies to these business capabilities, enterprise architects can ensure that all IT investments and activities are directly justified by and aligned with specific business needs and strategic objectives, preventing technology-driven silos (D).

B. A business capability model describes what a business does, not the underlying technology. Identifying hardware dependencies is a function of mapping the application and technology layers of the architecture.

C. This confuses capabilities with processes. A capability is what a company can do (e.g., "Invoice Management"), while a process describes how it is done. Capability models are abstractions, not detailed process flows.

1. SAP LeanIX Documentation

"Business Capability Maps: The Rosetta Stone for Business and IT": This official guide states

"Business capabilities are the single most important element for linking IT to the business. They describe what a business is doing..." It emphasizes that capabilities create a "common language" (supporting A) and are used to "align IT with business goals" (supporting D). (Accessed via SAP LeanIX Product Documentation portal).

2. SAP LeanIX Whitepaper

"The Ultimate Guide to Business Capability Modeling": Section "Why are Business Capabilities so important?" explains that they "provide a common language for business and IT" and "are the key to aligning IT with business goals." This directly validates answers A and D. The paper also clarifies

"Business capabilities are not business processes

" which invalidates option C.

3. The Open Group

"TOGAF® Standard

10th Edition

" Part II: Architecture Development Method (ADM)

Phase B: Business Architecture: Section 6.3.3

"Business Capabilities

" describes capabilities as a view of the business that is "stable in the face of organizational and process change." It highlights their role in "articulating the business strategy" and linking it to other architectural domains

which is the essence of alignment (supporting D).