What of the following features are true about batch tokens in Vault?

Comprehensive and Detailed In-Depth Explanation:

Batch tokens are lightweight tokens in Vault, designed for high-performance use cases.

A: They are not persisted to storage, reducing backend load, as confirmed by the batch token tutorial.

C: In Vault Enterprise with DR Replication, batch tokens are replicated and remain valid across clusters when the secondary is promoted, per replication docs.

B: Batch tokens cannot be renewed; they have a fixed TTL, per the service vs. batch token comparison.

D: They cannot create child tokens, lacking features of service tokens.