The project owner, Paul, asks a rule author, Bea, to update rules for the Spring release, and asks Adam to review and validate Bea's changes. After Bea finishes her updates, she notifies Adam. Adam…

Question

Options

• APaul forgot to assign Adam as a Tester.
• BAdam has rtsUser permissions, therefore, he cannot test rules.
• CAfter Bea finished her updates, she marked the status as Finished, which prevented
• DPaul needed to mark Bea's updates to the Spring release as Reviewed so that Adam

• A
  6% (3)
• B
  79% (41)
• C
  12% (6)
• D
  4% (2)

Explanation

Option B is correct because in rule management systems like IBM ODM (Operational Decision Manager), the rtsUser permission is a read-only/browse role - users with this role can view projects but cannot execute tests against rules. For Adam to validate Bea's changes, he would need a higher permission level such as rtsBuilder, which grants testing capabilities.

Why the distractors are wrong:

• A is incorrect because there is no generic "Tester" assignment in this system; access is controlled by permission roles, not task assignments.
• C is incorrect (and incomplete) because a rule author marking status as "Finished" does not lock out reviewers - workflow status and access permissions are separate concerns.
• D is incorrect because the project owner marking changes as "Reviewed" is a workflow step, not a prerequisite for a reviewer to access and test the project.

Memory tip: Think of rtsUser as a "read-the-shelf" library card - you can browse but you can't check things out or run experiments. Any role that needs to do something (build, test, validate) needs a higher-tier permission like rtsBuilder.

No community discussion yet for this question.