Q: 5
Tokenization requires two distinct ________
Options
Discussion
Option A is the way to go here. Multi-cloud with real-time replication minimizes both downtime and data loss, which daily backups or cold sites just can't match. D is a trap, since uptime SLAs don't guarantee true continuity.
What if the CRM vendor only supports a single cloud API, wouldn’t A be impossible in that case?
D
Daily backup (B) seems closest from official guide practice questions, but not sure if it hits "minimal downtime".
B
A , saw a similar scenario on an exam and A was the best pick for lowest downtime/data loss.
Definitely A for this one. Multi-cloud plus real-time replication gives you the best shot at both low RTO and RPO-way better than daily backups or cold site options. Cloud provider guarantees (D) aren't nearly enough if the CRM is truly critical. I think this matches ISC2's focus, but let me know if you see it differently.
A because D is a classic trap here. Uptime guarantees aren't the same as actual data redundancy, and B is good for backups but doesn't minimize downtime the way real-time replication does. Pretty sure A matches what ISC2 expects, agree?
I don't think it's B. A is the one that really covers minimizing downtime and data loss since real-time replication across multiple clouds means instant failover with up-to-date data. Backups like in B might save you, but you'd lose hours of transactions and take longer to restore. Pretty sure ISC2 is going for A here, unless I'm missing something?
A , because B is tempting but it's just backups not real-time. D is a classic distractor, uptime SLAs don't guarantee DR for your org. A matches the "minimize both downtime and data loss" part best.
Be respectful. No spam.