Help load-balance authentication requests.

Translate LDAP directory information for the Primary instance.

Allow the administrator to add users when the Primary instance is down.

Allow a single PASSCODE to be accepted on multiple RSA Authentication Agents.

The Replica is first promoted to a Primary instance.

The Replica instance is in a different domain from the Primary instance.

The database service on the Replica instance is running in Offline mode.

The Replica does not have a network connection to the Primary instance.

False

B. True

multiple Replica instances

Risk-Based authentication capability

On-Demand authentication capability

Business Continuity Option (BCO) capability

On-demand codes have a 5-minute synchronization window.

Token expiration dates are based on the date of the token’s first use.

Calculation of a tokencode involves the use of Universal Coordinated Time.

An administrator can configure the tokencode change interval on an RSA SecurID token.

Tokencode calculations are performed by both the RSA Authentication Manager instance and RSA SecurID tokens.

Changing a password or PIN

Creating an individual PIN policy

Requesting a replacement token

Resynchronizing an RSA SecurID token

The ability to track a user's login and logout time (RADIUS accounting).

Auser's default login name becomes their password (RADIUS login synchronization).

The computer time setting is verified remotely by the RADIUS client (remote time service).

The user Profile and Attribute Value Pair matches their tokencode (RADIUS token matching).