A banking client is complaining about the cost of putting applications onto the mainframe. They are considering deploying IBM Financial Transaction Manager, but have not yet decided the platform…

Question

Options

• ASecure Service Container solution
• BNew Application solution
• CPayments Pricing solution
• DApplication Development and Test solution

• A
  6% (2)
• B
  14% (5)
• C
  78% (28)
• D
  3% (1)

Explanation

Payments Pricing (C) is correct because IBM Financial Transaction Manager is specifically designed for payment and financial transaction processing, and the Payments Pricing solution ties software costs directly to transaction volumes - meaning as the application grows and processes more transactions, pricing scales proportionally rather than being fixed to traditional MIPS/MSU consumption metrics.

Option A (Secure Service Container) is a deployment and security isolation model for running encrypted workloads on LinuxONE/IBM Z - it addresses security, not transaction-based cost alignment.

Option B (New Application) offers reduced container pricing to incentivize net-new z/OS workloads, but it's time-limited and not tied to transaction throughput scaling.

Option D (Application Development and Test) provides discounted pricing for non-production environments only and has no relevance to production transaction-rate matching.

Memory tip: Think "FTM = Financial Transactions Manager → Payments Pricing." Both share the concept of counting transactions - when you see IBM FTM paired with a growing transaction workload, the pricing model that tracks with it is always the one named after payments.

No community discussion yet for this question.