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

Explanation

On-the-fly creation refers to the ability of a user to create a brand-new Fact Sheet directly from a relation field or a search bar while they are already editing another Fact Sheet.

For example, if you are editing an Application called "Payroll Plus" and you realize the IT Component "PostgreSQL 15" doesn't exist in the database yet, you don't have to leave the page. You can simply type the name into the relation field and select "Create New." This keeps the architect's workflow seamless and ensures that missing dependencies are captured immediately.

Why the other options are incorrect:

B. The real-time creation of fields:
Field creation (adding new attributes like "Cost" or "Criticality") is an administrative task handled in the Meta-model configuration area. This cannot be done "on-the-fly" by standard users while editing data.

C. Relations being created and deleted in real-time:
While relations are updated in real-time, "on-the-fly" specifically describes the instantiation of a new Fact Sheet object, not just the linking of existing ones.

D. The process of duplicating existing section or fact sheet types:
Duplication or "Cloning" is a specific feature, but it is not what LeanIX means by the technical term "on-the-fly."

References

SAP LeanIX User Documentation (Inventory Management): Describes on-the-fly creation as a "usability feature" that allows for the rapid expansion of the inventory during data maintenance.

Explanation:

A Business Capability Model (BCM) defines "what" a business does (e.g., "Accounts Payable") rather than "how" it does it. This abstraction is critical for bridging the gap between technical teams and business leadership.

Why A is correct:
The BCM acts as a common language. By mapping technical assets to capabilities, EAs can communicate with stakeholders in terms they understand. It removes technical jargon and focuses on the functional building blocks of the enterprise.

Why D is correct:
By linking Applications to Business Capabilities, you can see exactly which parts of the business are supported by IT. This "Business-to-IT" mapping ensures that IT investments are prioritized for the most critical capabilities, preventing "shadow IT" or redundant software spend.

Why the other options are incorrect:

B. It enables you to identify what hardware an application is dependent on:
This is the role of the IT Component Fact Sheet and the Technical Stack view. Business Capabilities are high-level business functions; they do not track physical servers or hardware dependencies.

C. It shows all detailed processes within a company:
This is a common distractor. Processes describe the sequential "how" (the flow of tasks), while Capabilities describe the "what" (the ability to perform a function). LeanIX recommends keeping the Capability Map at a high level (usually 2-3 levels deep) rather than documenting every granular process.

References

SAP LeanIX Documentation (Business Capability Mapping): States that the BCM is the "primary structure" for communicating the value of IT to the business.

LeanIX Best Practices: A solid BCM allows for Gap Analysis—identifying business areas that lack sufficient IT support or have excessive, overlapping application coverage.

✅ Explanation

In SAP LeanIX, automations are a no-code feature that enables administrators to establish workflows triggered by specific events on fact sheets, helping eliminate manual tasks and ensure data quality .

A. By navigating to administration is correct because the official SAP documentation explicitly states that automations are managed exclusively in the administration area. According to the SAP Help Portal: "Only admin users can manage automations. To view and configure automations, in the administration area, navigate to Automations" . The documentation further confirms: "In the workspace Administration area, select the Automations section under Advanced Settings" . This is the designated path for administrators to access, create, and manage all automation configurations.

❌ Why Other Options Are Incorrect

B. By navigating to dashboard is incorrect because the dashboard is designed for visualizing data and reports, not for administrative configuration. Automations require access to advanced settings that are only available in the administration area .

C. By navigating to fact sheet is incorrect because while automations affect fact sheets and their triggers are based on fact sheet events, the configuration and management of automations themselves happen centrally in the administration area, not within individual fact sheets .

D. By navigating to collaboration + automations is incorrect because although collaboration features (like to-dos, comments, and surveys) relate to automations , there is no navigation path called "collaboration + automations." The collaboration tab is for viewing assigned to-dos and surveys, not for configuring automations .

📚 References

SAP Help Portal: "Automations" documentation
SAP Help Portal: "To-Dos (Administration)"

Explanation:

These two attributes are the "Golden Metrics" in SAP LeanIX for Application Portfolio Management. Together, they allow architects to plot every application on the TIME Matrix (Tolerate, Invest, Migrate, Eliminate).

B. Functional fit:
This attribute measures how well an application supports the business capabilities and requirements it is intended for. Common values include Poor, Adequate, Strong, and Excellent. A low functional fit suggests the application is no longer meeting user needs.

C. Technical fit:
This measures the technical quality, stability, and maintainability of the application. It considers factors like architecture standards, ease of integration, and technical debt. A low technical fit often indicates that the application is difficult to support or is running on obsolete technology.

Why the other options are incorrect:

A. Operational fit:
While "Operational" health is a real-world concept, it is not a standard, default attribute in the LeanIX Meta-model. Operational concerns are usually captured under the "Technical Fit" umbrella or via specific "IT Component" lifecycles.

D. IT health score:
This is a distractor. While LeanIX can calculate various scores using the Metrics module or custom dashboards, there is no single out-of-the-box attribute called "IT health score." Instead, health is derived from the combination of Functional Fit, Technical Fit, and Business Criticality.

References

SAP LeanIX Documentation (APM Metrics): Explicitly identifies Functional Fit and Technical Fit as the two key dimensions for application assessment.

Explanation

IT Security (along with Risk and Compliance officers) uses SAP LeanIX to gain visibility into the technical vulnerabilities of the organization. Because LeanIX maps Applications to their underlying IT Components, IT Security teams can instantly identify which business areas are at risk when a specific piece of software (like an outdated database or library) reaches its "End of Life" (EOL) or has a known vulnerability (CVE).

Why the other options are incorrect:

B. Customer Service:
While Customer Service uses specific Applications to do their jobs, they are generally "Consumers" of the IT landscape. They do not use LeanIX data to manage the organization's technical compliance or risk frameworks.

C. IT Support:
IT Support (Help Desk) typically focuses on reactive troubleshooting and ticket management (often via tools like ServiceNow). While they benefit from knowing an application's owner, the strategic task of managing compliance and risk across the entire tech landscape is a higher-level governance function belonging to Security and EA teams.

References

SAP LeanIX Use Case (Technology Risk Management): This module is specifically designed for IT Security and EA teams to mitigate risks arising from obsolete technology and non-compliant software versions.

Explanation

Application Rationalization is the practice of strategically identifying which applications should be kept, replaced, retired, or consolidated.

Why B is correct:
By identifying applications with low functional value or high maintenance costs, organizations can retire unnecessary software. This directly reduces licensing fees, hosting costs, and the labor required for support and maintenance.

Why D is correct:
In large organizations, different departments often use different tools for the same purpose (e.g., three different project management tools). Rationalization identifies these overlaps. Consolidating these into a single standard reduces complexity and increases the organization's purchasing power with vendors.

Why the other options are incorrect:

A. It helps implement data quality initiatives:
While good data quality is a prerequisite for a successful rationalization project (you can't rationalize what you don't accurately track), the purpose of the initiative itself is portfolio optimization, not the improvement of the data governance process.

C. It provides an overview of the as-is IT landscape:
This describes Inventory Management or Transparency. While rationalization uses the "As-Is" view as a starting point, its specific goal is to change the landscape into a more efficient "To-Be" state, rather than just documenting what currently exists.

References

SAP LeanIX Use Case (Application Portfolio Management): LeanIX defines rationalization as the process of "cutting the tail" of the portfolio to free up budget for innovation.

Explanation

The Comments feature (found in the "Collaboration" tab of any Fact Sheet) is designed specifically for communication and data governance. It allows users to start a discussion thread directly on a record.

Why A is correct:
If a user notices an error or has a question about an application's lifecycle, they can tag the owner in a comment. This creates a transparent audit trail of the discussion. Crucially, it allows a Member or Viewer to provide feedback or seek clarification without having to manually "Edit" the Fact Sheet fields, which they might not have the permission or the specific data to do.

❌ Why Other Options Are Incorrect

Why B is incorrect:
The Quality Seal indicates whether the data is up-to-date. Breaking the seal signifies that the data needs review, but it is a status indicator, not a communication tool for seeking specific clarifications.

Why C is incorrect:
To-Dos are task-oriented. While they can be used to request an update, they are generally used for structured workflows (e.g., "Review this Fact Sheet by Friday") rather than a conversational exchange or a quick question.

Why D is incorrect:
Surveys are formal data collection campaigns sent to many users at once. They are too "heavy" for a simple clarification and are used for bulk data enrichment rather than ad-hoc updates.

References

SAP LeanIX Documentation (Collaboration): Describes comments as the primary way to "discuss Fact Sheet content with other users" while maintaining a history of the conversation.