SAILPOINT-CERTIFIED-IDENTITYNOW-ENGINEER · Question #78
Refer to the following diagram. For this strategy, all virtual appliances (VAs) are deployed in a single VA cluster, with all VAs running concurrently. Some of these VAs are in the primary data…
The correct answer is B. No. No, reconfiguration within IdentityNow is not required to connect to the disaster recovery (DR) VAs, which makes this scenario not a disadvantage. When properly configured, all VAs (including DR VAs) in a cluster are part of the same logical unit, meaning that failover to the…
Question
Refer to the following diagram. For this strategy, all virtual appliances (VAs) are deployed in a single VA cluster, with all VAs running concurrently. Some of these VAs are in the primary data center, and others {called OR VAs) are deployed in a DR data center. While using this strategy, is this a disadvantage? Solution: A reconfiguration will be required within identityNow to connect to the disaster recovery VAs. If there are many sources configured, this will cause overhead in performing this failover
Options
- AYes
- BNo
How the community answered
(18 responses)- A22% (4)
- B78% (14)
Explanation
No, reconfiguration within IdentityNow is not required to connect to the disaster recovery (DR) VAs, which makes this scenario not a disadvantage. When properly configured, all VAs (including DR VAs) in a cluster are part of the same logical unit, meaning that failover to the DR VAs should happen seamlessly without manual intervention or significant reconfiguration. IdentityNow handles the failover automatically, directing traffic to the DR VAs when primary VAs become While there might be some overhead in a manual failover scenario for certain configurations, the use of a single VA cluster helps mitigate this by ensuring the system can failover without needing complex reconfigurations for every source.
Topics
Community Discussion
No community discussion yet for this question.