Learn, Practice, and Improve with SAP C_LIXEA_2404 Practice Test Questions

Explanation:

In SAP LeanIX, IT Components represent the technical building blocks that support applications, such as software products, databases, libraries, and infrastructure elements. To accurately model these diverse technology assets, LeanIX provides specific subtypes that allow users to categorize IT Components consistently across the inventory.

The standard subtypes for IT Components include:
Software: Commercial or open-source software products
SaaS (Software as a Service) : Cloud-based software offerings
PaaS (Platform as a Service) : Cloud platform services
IaaS (Infrastructure as a Service) : Cloud infrastructure services
Hardware components: Physical infrastructure elements like servers, network devices, storage
Service: Managed services or other IT services

A. SaaS is a correct answer because it is a dedicated subtype for IT Components in LeanIX. When modeling cloud-based applications or services, the SaaS subtype helps distinguish these from on-premise software installations and is particularly useful for tracking hosting dependencies.

C. Server is a correct answer because it falls under the "Hardware components" subtype category. A server is a concrete example of an IT Component that would be modeled to represent the physical or virtual infrastructure running applications.

❌ Why Other Options Are Incorrect

B. Business process is incorrect because it is not an IT Component subtype. Business processes are modeled using Business Capability fact sheets in LeanIX, which represent what the organization does from a functional perspective, independent of the technology used. Business Capabilities are a fundamentally different fact sheet type in the LeanIX metamodel, focused on business architecture rather than technology infrastructure.

D. Hardware is incorrect in this context because while "Hardware components" is indeed a valid IT Component subtype, the option is presented simply as "Hardware." In LeanIX, the precise subtype name is "Hardware components." More importantly, the question asks for fact sheet subtypes, and between "Server" (a specific instance that would use the Hardware components subtype) and "Hardware" (the category name), "Server" is the correct answer as it represents a tangible example of an IT Component that would be modeled using one of the available subtypes.

📚 References
SAP LeanIX Help Portal: IT Component Fact Sheet documentation

✅ Explanation:

In SAP LeanIX, the Completion Score is a metric that measures how completely a specific Fact Sheet has been populated with relevant information. It is calculated based on the percentage of completed fields on that Fact Sheet, providing immediate visual feedback to users about what information is still missing or requires attention.

❌ Why Other Options Are Incorrect

A. Data quality across the entire workspace is incorrect because completion scores are calculated at the individual Fact Sheet level, not aggregated across the workspace. While workspace-level reports can display completion scores for multiple Fact Sheets, the metric itself assesses individual Fact Sheets, not the entire workspace collectively.

B. Data quality of a fact sheet is partially related but inaccurate. The Completion Score specifically measures completeness (whether fields are filled), which is just one dimension of data quality. Data quality also encompasses accuracy, consistency, timeliness, and validity—aspects not measured by the Completion Score. The Quality Seal is the LeanIX feature that addresses overall data reliability after human verification, making it distinct from the automated completion calculation.

D. Data completeness across the entire workspace is incorrect because the Completion Score is not a workspace-wide aggregate metric. LeanIX provides dashboards and reports that can show average completion scores across Fact Sheets, but the metric itself is defined and calculated at the individual Fact Sheet level, not as a workspace composite.

📚 References

SAP LeanIX Help Portal: "Completion Score" documentation
LeanIX Academy: Data Quality Management module (Lesson: Understanding Completion Scores)

Explanation:

IT Components represent the technical software and hardware assets (e.g., databases, operating systems, cloud services, or frameworks) that support an Application. In LeanIX, they define the Technology Stack. While an Application provides functional value to a business user (e.g., "Payroll System"), the IT Component represents the underlying technology required to run it (e.g., "Oracle Database 19c").

Why the other options are incorrect:

A. Business processes:
These describe how a company operates (e.g., "Order-to-Cash"). In LeanIX, these are mapped to the Business Context or Process Fact Sheets, not the technical layer.

B. Technical applications:
This is a common distractor. In LeanIX, Applications are high-level software functional units used by business users. IT Components are the lower-level dependencies of those applications. If you can log into it to do a job, it’s usually an Application; if it’s a library or server supporting that login, it’s an IT Component.

C. Users of the system:
These are mapped via User Groups (e.g., "Finance Department") or Subscriptions. They represent the "Who," whereas IT Components represent the "With What."

References
LeanIX Academic Concepts: The Meta-model defines the Provider (IT Component) → Consumer (Application) relationship.

Explanation:

A is Correct: A core goal of APA is transparency. By linking applications to cost data, EAs can identify "Total Cost of Ownership" (TCO), helping the business decide where to divest (retire) or invest (modernize).

B is Correct:
Assessing "Technical Fitness" is a pillar of APA. Using the Lifecycle attribute on Fact Sheets allows EAs to see which applications are running on outdated software (IT Components), which creates security and operational risks.

E is Correct:
This refers to Roadmapping. An assessment isn't just a snapshot; it maps the "As-Is" (current), "Was" (past), and "To-Be" (future) states to ensure the portfolio aligns with long-term strategy.

Why the other options are incorrect:

C. Organize applications according to IT components:
While applications are linked to IT components, "organizing" them this way is a technical mapping task, not the primary goal of a Portfolio Assessment. APA typically organizes applications by Business Capabilities to show business value.

D. Conduct daily surveys:
While LeanIX uses Surveys to gather data, doing them daily is a distractor. Surveys for APA are typically conducted once or twice a year (periodic "data crawls") to ensure data quality without causing "survey fatigue."

References
LeanIX Best Practices (Application Portfolio Management): SAP LeanIX defines the APA process through the TIME Model (Tolerate, Invest, Migrate, Eliminate)

Explanation:

SAP LeanIX recommends the Member role for the vast majority of users within an organization to foster a collaborative Enterprise Architecture culture.

Why A is correct: T
he "Member" role allows users to contribute to the inventory by creating and editing Fact Sheets, participating in Surveys, and maintaining the data they own (e.g., as an Application Owner). This aligns with the LeanIX philosophy that EA is a crowdsourced effort, not a siloed task for a few architects.

Why B is incorrect:
The Admin role grants full technical control over the workspace, including Meta-model configuration, user management, and API settings. Assigning this to everyone would pose a massive security and data integrity risk.

Why C is incorrect:
The Viewer role is strictly "read-only." While it allows users to see reports and Fact Sheets, it prevents them from contributing data or updating their own application profiles. If everyone were a Viewer, the data would quickly become outdated (shelfware).

References
SAP LeanIX Documentation (User Management): LeanIX explicitly defines the Member as the standard role for collaborators to ensure high data quality through decentralized ownership.

Explanation

In SAP LeanIX, the Application Fact Sheet represents software applications within an organization's IT landscape. Based on the LeanIX metamodel, applications have two defining characteristics that establish their position in enterprise architecture.

B. Relies on IT components to function is correct because applications depend on technical infrastructure and software building blocks. In LeanIX, this relationship is explicitly modeled by linking Application Fact Sheets to IT Component Fact Sheets (such as databases, servers, and software products) to document the complete technology stack. Understanding these dependencies is essential for impact analysis, risk assessment, and transformation planning.

D. Supports business capabilities is correct because applications exist to enable business functions. Business Capability Fact Sheets represent what an organization does, and applications are linked to them to demonstrate how IT supports business activities. This relationship aligns IT with business goals and is fundamental to Application Portfolio Management. LeanIX even provides smart recommendations when linking applications to business capabilities to ensure correct documentation.

❌ Why Other Options Are Incorrect

A. Clear technical ownership is incorrect because ownership in LeanIX (via subscription roles like "Responsible") relates to data governance and accountability, not a defining technical characteristic of what an application is. Ownership is an organizational attribute, not an inherent property of an application's function or structure.

C. Provides hosting information is incorrect because hosting information pertains to where applications run, which is captured through relationships to IT Components (servers, cloud services). Applications consume hosting services; they do not provide them. This confuses the application with the infrastructure supporting it.

📚 References

SAP LeanIX Help Portal: Application Fact Sheet documentation
SAP C_LIXEA_2404 Exam Syllabus: Domain "Modeling and Documentation"

Explanation:

The purpose of the Diagrams component in SAP LeanIX is to move beyond lists and tables to create a visual representation of the IT landscape that is easy for human stakeholders to digest.

Why C is Correct:
LeanIX follows a "Data-Driven" approach. Diagrams are not static drawings; they are views built on top of the Inventory. This allows architects to simplify complex technical environments into high-level visuals (like a Business Capability Map or a Data Flow Diagram) to facilitate decision-making with business leaders.

Why D is Correct:
This is the functional core of the feature. Diagrams allow you to visualize how Applications interact with one another (Data Flows) and how they fit into the broader Enterprise Architecture structure (e.g., Free-draw or Data-flow diagrams).

Why the other options are incorrect:

A. To calculate data insights:
While diagrams visualize insights, they do not calculate them. Calculation and data aggregation (such as TCO or counting Fact Sheets) happen within the Reports section or via the Metrics module.

B. To build the interface to SAP LeanIX reports:
This is technically backward. Reports are pre-defined, data-driven templates (like the Landscape or Matrix report). Diagrams are a separate tool used for custom modeling and flow visualization; they are not the "interface" used to build reports.

References

SAP LeanIX Documentation (Diagrams): The documentation defines diagrams as a tool to "model and visualize complex relationships" that cannot be easily captured in standard reports.