This mock exam covers IBM Cúram Social Program Management (SPM) across a balanced mix of functional/business-process topics (Integrated Case Management, Evidence & Verification, Eligibility & Entitlement, Participant/Provider Management, Universal Access, Task/Workflow, Outcome Management, Appeals/Investigation/Overpayment) and technical/configuration topics (Application Data Dictionary, Presentation Layer, Cúram Express Rules & Blueprints, Data Model, Integration/SOA, Security, Batch Processing, and the Development Environment). Each question has exactly one best answer. Attempt all 60 questions before checking the Answer Key. A score of 75% (45/60) or higher is a strong passing benchmark for self-assessment purposes. This is an original practice exam for study purposes and is not an official IBM certification product.
| Product Overview | 4 |
| Integrated Case Management | 5 |
| Evidence & Verification | 6 |
| Eligibility & Entitlement | 5 |
| Participant & Provider Management | 4 |
| Universal Access / Self-Service | 3 |
| Task Management & Workflow | 5 |
| Outcome Management | 2 |
| Appeals, Investigation & Overpayment | 6 |
| Application Configuration (ADD) | 4 |
| Presentation Layer | 4 |
| Rules Engine & Blueprints | 3 |
| Data Model & Persistence | 2 |
| Integration & SOA | 3 |
| Security | 2 |
| Batch Processing | 1 |
| Deployment & Development Environment | 1 |
What does IBM Cúram Social Program Management (SPM) primarily provide?
Which organization originally developed Cúram before IBM's acquisition?
In Cúram terminology, what is the central entity used to manage a client's engagement with an agency across multiple programs?
Which of the following is NOT a typical domain served by IBM Cúram implementations?
What is the primary purpose of the Integrated Case (IC) in Cúram?
Which Cúram concept allows evidence recorded once to be reused across multiple product delivery cases within an integrated case?
What is a 'Case Owner' typically responsible for in Cúram Integrated Case Management?
Which of the following best describes a 'Product Delivery Case' (PDC)?
What typically triggers eligibility and entitlement determination for a product delivery case?
What is 'Evidence' in Cúram?
Which component manages evidence-sharing rules and reuse across cases?
Which of the following is a standard verification status typically applied to a piece of evidence?
What happens to entitlement calculations when required evidence is recorded but not yet verified, depending on configuration?
What is the purpose of 'Evidence Types' configured in the Application Data Dictionary?
Why is evidence reusability a key Cúram design principle?
In Cúram, what is a 'Blueprint'?
What language/tool is commonly used to author Cúram business rules for eligibility and entitlement?
What is the difference between 'eligibility' and 'entitlement' in Cúram program processing?
Which tool is typically used by business/rule analysts to author and test Cúram Express Rules?
Why does Cúram separate rules (CER/Blueprints) from core Java code?
In Cúram, what is a 'Participant'?
What role does a 'Provider' typically play in Cúram?
Which concept allows Cúram to link related participants, such as household or family relationships?
What is typically tracked for a Provider in Cúram beyond basic contact details?
What is 'Universal Access' in the Cúram product suite?
Which benefit does a self-service portal like Universal Access provide to agencies?
What can a client typically do through a Cúram-based self-service portal?
What is the purpose of Cúram Task Management functionality?
What is a 'workflow' in the context of Cúram business process management?
Which term describes automatically routing generated tasks to the appropriate worker or team based on configured rules?
Why are workflows valuable in a Cúram implementation?
What might trigger the creation of a workflow-driven task in Cúram?
What does Cúram's Outcome Management functionality primarily support?
Outcome plans in Cúram are most commonly associated with which type of program area?
What is the purpose of the Appeals functionality in Cúram?
What does the Investigation module in Cúram typically support?
What is 'Overpayment' (or Debt) management used for in Cúram?
Which of these could commonly trigger an overpayment/debt case?
What outcome could an appeal typically result in?
Why is a formal appeals process important for social program agencies?
What is the Application Data Dictionary (ADD) in Cúram?
What is a benefit of using a meta-data-driven configuration approach like the ADD?
Which of the following is typically defined through Cúram's application configuration tools?
What is a 'Code Table' used for in Cúram configuration?
What technology historically underpins the Cúram Presentation Layer (server-rendered UI)?
What is the purpose of Cúram's UI-generation tooling from the ADD?
Why might a Cúram implementation still require manual UI customization despite generated screens?
What does the term 'Cúram Web Client' typically refer to?
What advantage does separating eligibility/entitlement logic into CER rules provide during legislative/policy changes?
What is typically validated after modifying a Blueprint or CER rule?
In Cúram, what is the relationship between a 'Product' and a 'Blueprint'?
What is a typical role of the underlying relational database (e.g., DB2/Oracle) in a Cúram deployment?
What is the purpose of database schema generation from the ADD?
How does Cúram commonly integrate with external systems (e.g., financial systems, other agency systems)?
Why might a Cúram implementation expose or consume web services?
What is a common consideration when integrating Cúram with an external payment/financial system?
What model does Cúram commonly use to control what functions/data a user can access?
What is the purpose of assigning workers to an 'Organization Unit' (Org Unit) in Cúram?
What is a typical use of Cúram batch processing?
What is the Cúram SDEJ (Software Development Environment for Java) primarily used for?
| # | Topic | Correct Answer | Explanation |
|---|---|---|---|
| 1 | Product Overview | B — A case management platform purpose-built for health and human services agencies | Cúram SPM is purpose-built to help government and human services agencies manage social programs such as benefits, child welfare, and health services — not a generic ERP, CRM, or supply-chain tool. |
| 2 | Product Overview | A — Cúram Software Ltd (Dublin, Ireland) | Cúram Software was an Irish company (Dublin) that IBM acquired in 2011, forming the basis of IBM Cúram Social Program Management. |
| 3 | Product Overview | B — Integrated Case | The Integrated Case (IC) is the umbrella case that consolidates a participant's evidence and links the various Product Delivery Cases across programs. |
| 4 | Product Overview | C — Point-of-sale retail inventory | Cúram targets social program domains (welfare, child services, health/Medicaid). Point-of-sale retail inventory is unrelated to its purpose. |
| 5 | Integrated Case Management | B — To serve as a single case that consolidates a participant's evidence and associated product delivery cases across programs | The Integrated Case brings together a participant's shared evidence and links to the individual Product Delivery Cases opened for specific programs/products. |
| 6 | Integrated Case Management | A — Evidence sharing via the Evidence Broker | The Evidence Broker manages how evidence is shared and reused across cases so citizens are not asked for the same information repeatedly. |
| 7 | Integrated Case Management | B — Overall coordination and management of the participant's case and assigned tasks | A Case Owner is the caseworker accountable for coordinating the client's overall case, including monitoring tasks and outcomes. |
| 8 | Integrated Case Management | B — A case created to manage the delivery of a specific product/benefit to a participant, including eligibility and entitlement processing | A PDC is opened for a specific product (e.g., a benefit) and drives eligibility/entitlement determination and ongoing delivery of that product. |
| 9 | Integrated Case Management | B — Recording or updating evidence and running the associated rules (Blueprints) | Evidence changes feed into the configured Blueprints/CER rules, which recalculate eligibility and entitlement. |
| 10 | Evidence & Verification | B — Structured facts about a participant or case (e.g., income, household, employment) recorded in the system | Evidence represents structured facts (income, household composition, employment, etc.) captured about a participant that feed rule processing. |
| 11 | Evidence & Verification | A — Evidence Broker | The Evidence Broker governs how and when evidence recorded for one case can be shared with or reused by other cases for the same participant. |
| 12 | Evidence & Verification | B — Unverified | Cúram tracks verification states such as Unverified, Verification Requested, Verified, and Verification Failed for recorded evidence. |
| 13 | Evidence & Verification | B — The system may calculate provisional entitlement while flagging the evidence as unverified, or block entitlement — depending on configured business rules | Whether unverified evidence blocks or merely flags entitlement processing is a configurable business rule decision, not a fixed universal behavior. |
| 14 | Evidence & Verification | A — To define the structure and fields of a category of evidence (e.g., Income, Absence) | Evidence Types are meta-data definitions describing the fields and structure of a category of facts an agency wants to capture. |
| 15 | Evidence & Verification | B — To avoid asking citizens for the same information repeatedly across programs, improving efficiency and citizen experience | A core Cúram value proposition is 'tell us once' — reusing shared evidence across programs to reduce burden on citizens and staff. |
| 16 | Eligibility & Entitlement | B — A rule structure used with Cúram Express Rules to determine eligibility and entitlement for a product | A Blueprint organizes the CER rules that determine eligibility and calculate entitlement for a specific product. |
| 17 | Eligibility & Entitlement | A — Cúram Express Rules (CER) | CER is Cúram's dedicated business rules language, designed to be more accessible to business/rule analysts than general-purpose code. |
| 18 | Eligibility & Entitlement | B — Eligibility determines whether a participant qualifies for a product; entitlement determines the amount/level of benefit received | Eligibility is a qualifying (yes/no) decision; entitlement calculates the specific amount or level of benefit for an eligible participant. |
| 19 | Eligibility & Entitlement | A — Cúram's rules authoring/modeling environment (e.g., Rules Studio) | Cúram provides a dedicated rules authoring/modeling environment that supports building, validating, and testing CER rules. |
| 20 | Eligibility & Entitlement | B — To let business/functional analysts configure and adjust program logic without extensive custom coding, improving agility | Separating rules from code lets agencies respond faster to policy/legislative changes by configuring rules rather than rewriting core application code. |
| 21 | Participant & Provider Management | B — Any person or organization that interacts with the agency, such as a client, provider, or related person | Participant is a broad concept covering any person or organization the agency deals with — clients, providers, employers, related persons, etc. |
| 22 | Participant & Provider Management | A — An entity or individual delivering services or benefits on behalf of the agency (e.g., a childcare provider) | Providers are organizations or individuals contracted or registered to deliver services (e.g., childcare, medical care) that the agency pays for or oversees. |
| 23 | Participant & Provider Management | A — Relationship management / person relationships | Cúram models relationships between participants (e.g., spouse, child, household member) to support case and eligibility processing that depends on household composition. |
| 24 | Participant & Provider Management | B — Contracts/agreements, qualifications, service capacity, and compliance information | Provider management typically includes contracting, credentialing/qualifications, capacity, and compliance tracking relevant to service delivery oversight. |
| 25 | Universal Access / Self-Service | A — A citizen/provider self-service portal enabling online applications, evidence submission, and case status viewing | Universal Access is Cúram's self-service capability allowing citizens and providers to interact online with the agency. |
| 26 | Universal Access / Self-Service | B — Reduces call center/counter volume by allowing clients to self-serve for applications and status checks | Self-service channels reduce demand on staff-facing channels by letting clients handle routine interactions themselves. |
| 27 | Universal Access / Self-Service | B — Submit applications, upload documents, report changes, and check case/benefit status | Self-service portals expose client-facing functions like applying for benefits, uploading verification documents, and checking case status. |
| 28 | Task Management & Workflow | A — To assign, prioritize, and track work items (tasks) for caseworkers | Task management generates, assigns, and tracks discrete units of work for caseworkers, often triggered by system events. |
| 29 | Task Management & Workflow | B — A defined, often graphically modeled, sequence of activities/steps that routes work according to business processes | Workflows model the steps and routing logic of a business process, ensuring tasks move through the correct sequence of activities. |
| 30 | Task Management & Workflow | A — Task/work distribution | Work/task distribution logic determines which worker or team a generated task should be routed to, based on configured criteria. |
| 31 | Task Management & Workflow | B — They enforce consistent business processes, ensure required steps aren't skipped, and support auditability | Workflows provide process consistency, ensure compliance steps are completed, and leave an auditable trail of case handling. |
| 32 | Task Management & Workflow | B — System-detected events such as a change in evidence, an approaching deadline, or a failed verification | Tasks are commonly generated automatically in response to business events like evidence changes, deadlines, or verification failures. |
| 33 | Outcome Management | A — Tracking and measuring progress toward client goals/outcomes (e.g., in case work or child welfare) | Outcome Management helps caseworkers set goals/outcome plans for clients and track progress toward those outcomes over time. |
| 34 | Outcome Management | B — Case work programs focused on well-being, such as child welfare or family services | Outcome-based case work is especially prominent in social service domains like child welfare, where tracking a family's or child's progress matters. |
| 35 | Appeals, Investigation & Overpayment | A — To allow participants to formally dispute a decision (e.g., denial or reduction of benefits) and have it reviewed | Appeals lets a participant contest an agency decision, triggering a formal review/reconsideration process. |
| 36 | Appeals, Investigation & Overpayment | A — Managing suspected fraud or program-integrity cases, including evidence gathering and case tracking | Investigation supports program integrity work — tracking suspected fraud or abuse cases and the evidence gathered during review. |
| 37 | Appeals, Investigation & Overpayment | A — Calculating and recovering benefits that were paid in excess of a client's correct entitlement | Overpayment/debt management identifies, calculates, and manages recovery of benefits overpaid relative to a client's actual entitlement. |
| 38 | Appeals, Investigation & Overpayment | A — A retroactive change in evidence that reduces a client's entitlement for a period already paid | Retroactive evidence changes that lower a client's entitlement for a period they were already paid for are a classic overpayment trigger. |
| 39 | Appeals, Investigation & Overpayment | A — The original decision being upheld, reversed, or modified after review | An appeal review can uphold, reverse, or modify the original decision depending on the findings. |
| 40 | Appeals, Investigation & Overpayment | B — It ensures due process and legal/regulatory compliance when clients are impacted by adverse decisions | Agencies are typically legally required to provide clients a fair, documented process to contest decisions affecting their benefits. |
| 41 | Application Configuration (ADD) | A — A meta-data-driven definition of the application's data model and structures, used to generate application artifacts (e.g., database schema, Java classes) | The ADD is the meta-model at the heart of Cúram's configuration-driven approach, from which schema, code, and other artifacts are generated. |
| 42 | Application Configuration (ADD) | B — It allows structured, consistent generation of application layers (data, business, UI) from a single definition, reducing manual coding and errors | Generating layers from a single authoritative meta-model improves consistency and reduces manual coding effort and error compared to hand-building each layer. |
| 43 | Application Configuration (ADD) | A — Evidence types, code tables, and business object structures | Configuration tools built around the ADD are used to define business data structures such as evidence types, code tables, and objects. |
| 44 | Application Configuration (ADD) | A — Storing valid values/lookup lists used across the application (e.g., a list of US states) | Code tables hold controlled lists of valid values (lookups) referenced throughout the application, such as states, relationship types, or statuses. |
| 45 | Presentation Layer | A — A Struts-based JSP framework with Cúram-specific tag libraries | Cúram's classic web presentation layer is built on a Struts-based JSP architecture, extended with Cúram-specific custom tag libraries. |
| 46 | Presentation Layer | A — To auto-generate baseline pages/screens consistent with the underlying data model, reducing manual UI coding | UI generation tooling produces baseline screens directly aligned to the configured data model, cutting down on manual page-building work. |
| 47 | Presentation Layer | B — To meet specific agency branding, usability, workflow, or business requirements not covered by defaults | Generated screens provide a functional baseline, but agencies commonly need custom branding, layout, or workflow refinements beyond the defaults. |
| 48 | Presentation Layer | B — The browser-based user interface used by caseworkers and/or citizens to interact with the application | The Web Client is the browser-based front end through which users (workers or citizens) interact with the Cúram application. |
| 49 | Rules Engine & Blueprints | B — Policy/rule changes can often be implemented and tested by configuring rules rather than rewriting core application code, speeding response to policy change | A key value proposition of CER/Blueprints is agility: agencies can adapt to legislative or policy changes by updating rules rather than the underlying codebase. |
| 50 | Rules Engine & Blueprints | B — The rule logic is tested (e.g., via test cases/scenarios) to confirm correct eligibility/entitlement outcomes before deployment | Rule changes should be tested against representative scenarios to confirm they produce correct eligibility/entitlement results before being promoted. |
| 51 | Rules Engine & Blueprints | A — A Product configuration references or is supported by Blueprints/rules that determine eligibility and entitlement processing for that specific benefit/service | Each configured Product is tied to the rule logic (Blueprints) that governs how eligibility and entitlement are determined for it. |
| 52 | Data Model & Persistence | A — Persisting case, participant, evidence, and product data generated/managed via the application's data layer | Cúram relies on a relational database to persist its business data — cases, participants, evidence, and product/entitlement records. |
| 53 | Data Model & Persistence | A — To keep the physical database structure consistent with the logical data model defined in configuration | Generating the schema from the ADD ensures the physical database stays aligned with the logical, configuration-defined data model. |
| 54 | Integration & SOA | B — Via web services/SOA-based integration interfaces and data exchange mechanisms | Cúram supports service-oriented, web-service-based integration patterns for exchanging data with external and partner systems. |
| 55 | Integration & SOA | A — To exchange data such as payment information, identity verification, or evidence with external/partner systems | Web services are commonly used to integrate with external systems for functions like payments, identity/verification checks, and evidence exchange. |
| 56 | Integration & SOA | A — Ensuring entitlement/payment data is transmitted accurately and reconciled to avoid over- or under-payments | Accuracy and reconciliation of payment data are critical to prevent overpayments or underpayments when integrating with financial systems. |
| 57 | Security | A — Role-based access control (RBAC), often combined with organizational unit structures | Cúram security is generally role-based, often layered with organizational structures to further scope access and case routing. |
| 58 | Security | A — To reflect the agency's organizational structure and help route/manage cases, security, and workload appropriately | Org Units model the agency's structure and are used alongside roles to help govern case assignment, security scoping, and workload management. |
| 59 | Batch Processing | B — Periodic/scheduled processing such as reprocessing eligibility, sending notifications, or running mass updates outside interactive user sessions | Batch jobs handle large-scale, scheduled processing like eligibility reprocessing, notices, and mass updates that don't require an interactive session. |
| 60 | Deployment & Development Environment | A — Providing developers with an environment/toolset to build, customize, and test Cúram application code and configuration | The SDEJ is the developer-facing environment/toolset used to build, customize, and test Cúram applications during implementation. |