The Infinite Apps feature is part of the CyberArk Identity Browser Extension. It simplifies the process of adding SaaS user-password applications that are not listed in the CyberArk Identity App Catalog. The feature includes the App Capture utility, which automatically discovers the username and password fields on a web application’s login page. Once discovered, it adds the application to the portal’s Apps page, allowing it to be deployed with single sign-on capabilities to user portals and devices. If the App Capture utility cannot automatically discover the fields, it provides the option to select them manually. Additionally, users can add applications to their user portal Apps pageand devices using the browser extension, subject to configuration settings managed by the “Allow users to add personal apps” policy.
References: This information can be found in the CyberArk documentation for adding web applications using CyberArk Identity Infinite Apps1.
Questions 5
What is considered an "Identity Provider Initiated" login to an application?
Options:
A.
After signingin to the CyberArk Identity portal, a userlaunches a SAML app by clickingan apptile.
B.
After visitinga third-party web app, a user is redirected to CyberArk Identity for authentication.
C.
A user visits a third party web appdirectly and signs in with local credentials.
D.
A user signs in to the CyberArk Identity portal and takes a screenshot of the portal to send to IT.
An “Identity Provider Initiated” login refers to a scenario where the authentication process begins at the identity provider rather than the service provider. In the context of CyberArk Defender Access, this occurs when a user first signs into the CyberArk Identity portal and then initiates access to an application by clicking on a SAML app tile. This process ensures that the user is authenticated through CyberArk Identity before being granted access to the application, thus providing a secure single sign-on (SSO) experience.
References: The explanation is based on the standard practices of SSO and the specific workflow of CyberArk Identity as an identity provider, which is documented in CyberArk’s official resources123.
Questions 6
Which CyberArk Identity service do you use to find a list of pre-built app connectors?
The CyberArk Identity service that provides a list of pre-built app connectors is the AppCatalogue. This feature allows users to access and manage a variety of application connectors that are designed to facilitate integration with CyberArk Identity for Single Sign-On and Multi-Factor Authentication.
References: The information is supported by CyberArk’s documentation, which mentions the availability of pre-built app templates within the CyberArk Identity Application Network as part of their collaboration program1.
Questions 7
What can cause users to be prompted for unrecognized MFA factors, such as a wrong phone number or unregistered MFA factor?
Options:
A.
Someone installed the CyberArk Identity mobile app on a different phone with their credentials.
B.
The administrator switched authentication profiles.
C.
They mistyped their username.
D.
Someone registered their phone number to the wrong username.
When users are prompted for unrecognized MFA factors, it is often due to a discrepancy between the identity information they are providing and the information registered in the MFA system. If a user mistypes their username, the system may not recognize them and therefore prompt them with MFA challenges that are not associated with their account. This is a common security measure to prevent unauthorized access.
References: This explanation is based on general principles of MFA systems and their operation. For the most accurate and detailed explanation, please refer to the official CyberArk Defender Access (ACC-DEF) study guide and course documentation, which can be found through the CyberArk training portal1.
