C1000-010 IBM Operational Decision Manager Standard V8.9.1 Application Development Practice Questions

Decision Center delegates security (authentication and authorization) to the underlying Java EE application server. The correct procedure is to configure the application server (like WebSphere or Liberty) to use the LDAP server as its user repository. Then, within the application server's security settings, the standard Decision Center roles (e.g., rtsAdministrator, rtsUser) are mapped to the corresponding groups defined in LDAP.

An Action Phrase is used to verbalize a method that performs an action (typically a void method or a setter). By creating an action phrase like 'apply a discount of {0}' and mapping it to the setDiscount method, the developer provides a natural language template for business users to use in the action part of a rule.

The RetePlus algorithm is optimized for inference and rule chaining, where the actions of one rule affect the conditions of another. It builds a network to efficiently evaluate rules. However, if there is little or no inference (few rules firing), the overhead of maintaining the Rete network can be greater than the benefit. The Sequential algorithm, which processes rules in a stateless manner, is often much faster in such scenarios. Changing the execution mode for the relevant rule tasks is a key performance tuning technique.

A BOM domain (or enumerated domain) is used to create a list of predefined, static values for a BOM attribute. When a business user authors a rule using this attribute, instead of a free-form text field, they are presented with a drop-down list of the allowed values. This improves rule authoring accuracy and consistency.

This is the most robust and scalable approach. Separating the rules into two decision services allows for completely independent governance, security, and deployment lifecycles. The Underwriting service can have a rigid, multi-step approval workflow, while the Marketing service can have a simpler one. This aligns with the organizational structure and requirements, providing maximum agility for the Marketing team without compromising the stability of the core risk rules. The client application would then orchestrate calls to both services.

In ODM, custom rule session interceptors are enabled by setting the ruleset.interceptor.className ruleset property to the fully qualified name of the interceptor class. During migration, deployment configurations and ruleset properties must be carefully reviewed and reapplied. It's a common oversight for these properties not to be carried over automatically, leading to the interceptor not being invoked by the rule engine. While the other options represent plausible issues, the direct mechanism for enabling an interceptor is this specific ruleset property.

For high-throughput, low-latency scenarios, network I/O is a major bottleneck. Loading the reference data into memory avoids database or microservice calls for every transaction. By using a static collection in the XOM and initializing it in a ruleset variable, the data is readily available to the rule engine. A background process can handle the daily refresh, ensuring the in-memory cache is up-to-date without impacting transactional performance. The other options introduce significant latency due to network calls or large payload sizes.

A State Phrase is used to verbalize a boolean attribute or a method that returns a boolean. By defining a state phrase like '{this} is premium' for the isPremium attribute, the developer allows business users to write natural language conditions such as 'if the policy is premium'. This directly translates to Policy.isPremium() == true in the underlying code.

The correct format for the RES REST API endpoint to execute a specific version of a ruleset includes the RuleApp name and version, followed by the ruleset name and version. The path is structured as /res/api/v1/ruleapps/{ruleAppName}/{ruleAppVersion}/rulesets/{rulesetName}/{rulesetVersion}. In this case, it is assumed the RuleApp version is 1.0, and the target ruleset version is 1.2. The other formats are incorrect.

This is true. Decision governance workflows are a property of the branch itself. When a workflow is set at the branch level, all rule artifacts within that branch, including newly created projects, are subject to that governance model. This ensures consistent change management and approval processes across the entire branch.