To prevent unauthorized traffic from the IP range 103.1.200.0/24, you would need to log in to the CyberArk Identity Admin portal and define this range as a blocked IP range. This effectively prevents any traffic from these IP addresses from accessing the CyberArk Identity portal, thereby reducing the vulnerability to unauthorized access attempts from this specific range.

The setting 'Continue with additional challenges after failed challenge' in the Authentication Policy indicates that even if the initial challenge (e.g., password) fails, subsequent challenges (MFA) will continue to be presented to the user. Therefore, if users have set up the CyberArk Mobile Authenticator as an MFA, they will still receive the push notification even if they mistyped their password. Also, if the first factor is a password and the user is an Active Directory user but Active Directory is unavailable, the user will not be able to authenticate using Active Directory credentials and will see the message 'Active Directory not available,' making the setting irrelevant in this scenario.





Leaving the setting as Default (--) typically means that the system's default behavior will apply. For notifications in multi-device environments, the default behavior will most likely be to send the push notification to all enrolled devices to ensure the user gets it on one of their devices. This promotes accessibility and ensures a higher chance that the user will receive and act on the notification promptly.