What are the aspects of a Multi-Target Application (MTA) model in the lifecycle management of distributed applications? Note: There are 3 correct answers to this question.

Question

Options

• AConfiguration
• BIntegration
• CDependencies
• DCI/CD
• EComposition

• A
  90% (26)
• B
  7% (2)
• D
  3% (1)

Explanation

An MTA (Multi-Target Application) model is a descriptor-based approach (typically mta.yaml) used in SAP environments to package and deploy distributed applications. Configuration (A) is correct because the MTA descriptor defines properties and parameters for each module and resource in the target environment. Dependencies (C) is correct because the MTA model explicitly captures requires/provides relationships between modules and resources to ensure correct deployment ordering. Composition (E) is correct because an MTA is fundamentally a declared grouping - a "composition" - of multiple modules and resources that together form one deployable unit.

Integration (B) is a capability concern handled by middleware or integration platforms, not a structural pillar of the MTA model itself. CI/CD (D) describes a pipeline practice external to the MTA descriptor; the MTA model governs what gets deployed and how it's wired together, not the automation pipeline that triggers deployment.

Memory tip: Think "CCD without the middle" - Composition, Configuration, Dependencies. An MTA answers three questions: What pieces exist? (Composition), How are they set up? (Configuration), What needs what? (Dependencies).

No community discussion yet for this question.