Java Core Classes and Threads

The Property-Set method is the standard way to update property values in activity steps. It efficiently sets property values without requiring direct Java code. Option B's AtSetValue is incorrect, and Option A's Java method is not the recommended approach in PRPC.

The Property-Map-Value method evaluates a 1D map value rule using a single row input. The Property-Map-ValuePair method evaluates a 2D map value rule, which accepts both a row input and a column input to look up a value.

Property-Map-Value calls a Rule-Obj-MapValue with a single row input. Property-Map-ValuePair calls the same Rule-Obj-MapValue but passes a single row AND a single column input, allowing lookups that depend on two dimensions. Option A is incorrect about the number of calls. Option B incorrectly mentions 'two row inputs'. Option D incorrectly mentions 'multiple row inputs'.

Property-Seek-Value is used to invoke backward chaining. In backward chaining, the system seeks a value only when needed (on-demand) rather than deriving it proactively. This is a lazy evaluation approach where the value is computed when first requested.

The Exit-Activity method is specifically designed to terminate the current activity's processing and return control to the calling activity. This is the standard method name used in Pega/Process Commander for activity termination, unlike Activity-End or End-Activity which are not valid method names in the system.

The Property-Set method is the standard, recommended approach in Pega PRPC for updating property values within an activity. This method is specifically designed for property manipulation and provides proper error handling and validation. Java methods should be avoided for simple property updates, and AtSetValue is not a standard Pega method.

Property-Map-Value passes a single row input to a Rule-Obj-MapValue, while Property-Map-ValuePair passes both a row input and a column input. The 'Pair' in the name refers to the two-dimensional lookup (row + column), not multiple row inputs or calling the rule twice.

When conditions can be used in Preconditions (to control whether an activity executes) and Transitions (to control flow between steps). They are NOT used directly in step methods, parameters, or loop conditions - those use different expressions.

Blacklist validation is weak because it tries to block known bad inputs, which attackers can easily bypass using alternative encodings, alternate representations, or obfuscation that the filters do not cover. Distractors incorrectly blame hardcoding, HTTP POST complexity, or confuse blacklists with whitelist-oriented regular expressions.

The hashPassword method requiring both password and accountName parameters allows for account-specific salting, which improves security by preventing the same password from hashing identically across different accounts. The single-parameter versions would be less secure. Option C is incorrect due to incorrect method naming convention (lowercase 'p').

The verifyPasswordStrength() method is a void method, meaning it performs validation and likely throws an exception or sets internal state rather than returning a value. This is common for validation methods that enforce security policies by throwing exceptions when requirements aren't met.

The isAuthorizedForData() method checks whether the current user is authorized to access or modify a specific data object. It returns a boolean value (true if authorized, false otherwise). It does not return text, numeric identifiers, or a void type, as authorization is a binary status check.

CSRF tokens are typically generated as random strings that can be embedded in forms or HTTP headers. The getCSRFToken() method returns a String token value, not numeric types like Integer or BigInteger, which would be unsuitable for token representation.

The sign method in the security API accepts a single String parameter (data) and throws SecurityException. Options A and B incorrectly include a key parameter, while option C is missing the required exception declaration that security operations typically need.

The seal method requires both data and timestamp parameters and throws SecurityException. Options C and D are missing the required timestamp parameter that seal operations need, while option B throws the wrong exception type.