Database validation establishes whether financial transactions have been persisted correctly and whether related records remain consistent across the application's underlying data structures.

Option B provides the most complete combination of database-focused assertions among the available choices.

Row-count verification confirms that the expected number of records exists after the transaction. Key-field validation checks important attributes such as transaction identifiers, monetary amounts, account references, currencies, and processing status.

Referential integrity validation confirms that related database records maintain valid relationships. For example, a financial transaction should reference an existing customer account and any applicable ledger or payment records.

Timestamp validation verifies whether transaction creation and update events were recorded within the expected processing period.

UiPath supports database access through its Database Activities package. The Run Query activity executes SQL statements and returns results in a DataTable, which can then be evaluated using testing verification activities.

Option A includes browser responsiveness, which is not a database-integrity assertion. Option C introduces UI rendering and selector stability. Option D focuses primarily on presentation-layer confirmations.

Official UiPath Reference(s): Database Activities — Run Query; Activities; Testing Activities — Verify Expression With Operator.