Which solution is a viable option to capture user identification when Active Directory is not in use?
Which solution is a viable option to capture user identification when Active Directory is not in use?
When Active Directory is not in use, capturing user identification would require an alternative method that does not rely on the directory services provided by Active Directory or similar systems. An Authentication Portal provides a way for users to manually authenticate themselves, allowing for user identification regardless of the presence of an Active Directory. This makes it a viable solution for scenarios where Active Directory is not in use.
I think that best answer is "Authentication portal"
Same here
CIE is dependent upon on-prem AD or Cloud Azure AD. https://docs.paloaltonetworks.com/cloud-identity/cloud-identity-engine-getting-started/get-started-with-the-cloud-identity-engine/learn-about-the-cloud-identity-engine#id3f7f173a-ab4b-4040-b82e-86944d8b769b The components of the Cloud Identity Engine deployment vary based on whether the Cloud Identity Engine is accessing an on-premises directory (such as Active Directory) or a cloud-based directory (such as Azure Active Directory). There is nothing like Authn portal on PA, its actually Captive Portal. If we go word-by-word then CIE is the answer otherwise Authn Portal is. Very ambiguous question.
"capture" - it's D
Answer would be D
ABC - all have to do with active directory. Answer is D
i think it's D, for my side.
i think it's D, for my side.
Has to be D. Active directory is not in use..
a b c - all have to do with active directory. answer is D
"when active directory is not in use" so it can't be CIE. D is the corret answer