Is the following true about custom connectors in IdentityNow?Solution: Custom connector configurations can have account correlation settings defined.
Answer(s): A
Yes, custom connector configurations in SailPoint IdentityNow can have account correlation settings defined. Account correlation is used to link accounts from different sources to the correct identity in IdentityNow. When configuring a custom connector, it is possible to define how accounts from the connected system are correlated to existing identities based on attributes like usernames or other unique identifiers.Key Reference from SailPoint Documentation:Custom Connector Configuration: SailPoint allows for the definition of account correlation settings in custom connectors to ensure proper linking of external accounts to internal identities.
Is the following true about custom connectors in IdentityNow?Solution: Custom connector are developed and compiled inside identityNow.
Answer(s): B
No, custom connectors are not developed and compiled inside IdentityNow. Custom connectors are typically developed outside of the IdentityNow platform using a development environment and then tested and packaged before being uploaded to the platform. These connectors can be developed using tools provided by SailPoint, but the actual development process occurs externally, not directly within the IdentityNow environment.Key Reference from SailPoint Documentation:Custom Connector Development: Custom connectors are developed outside of the IdentityNow platform and then integrated into it for use.
Is the following true about custom connectors in IdentityNow?Solution: Custom connector are imported the identityNow UI.
Yes, custom connectors are imported into IdentityNow via the UI. After development and testing, the custom connector configuration is uploaded to the platform through the IdentityNow interface. This allows administrators to define how the connector interacts with external systems and specify settings like account aggregation, correlation, and provisioning.Key Reference from SailPoint Documentation:Connector Import Process: Custom connectors are uploaded into IdentityNow through the UI, where they can then be configured and used to connect to external systems.
Exhibit.The diagram represents me contents of a single Active Directory forest. Assume that all employees hove employeeType set to employee and contractors have employeeType set to contractor.is the following configuration valid for the given scenario?Solution:The customer needs to query only Employees from Domain A and Contingent Workers from Domain B Fotests:1. DN - dc=domains, dc=com;TLS =No; Server = server,domaina.com2. DN - dc=domaininb,dc=com;TLS =No; Server = server,domaina.com search DNS:1. DN - OU=users, DC=domains, DC=com; LDAP Filter = (employeeType=employee2. DN - OU=Contingent Workers, OU=Users, DC=domainb, DC=com
The configuration provided is not valid due to an error in the server specification for Domain B. The server for Domain B (domainb.com) is incorrectly set to server.domaina.com, which is not correct. Each domain in the Active Directory (AD) forest should have its own respective server. For Domain B, the correct server should be something like server.domainb.com, assuming that there are distinct domain controllers for each domain.Additionally, the search DN for Domain A appears to be valid as it correctly filters for employees with (employeeType=employee). The search DN for Domain B seems to be partially correct, as it targets the OU=Contingent Workers, but the issue lies with the incorrect server assignment.Key Reference from SailPoint Documentation:Active Directory Configuration: Each domain in a forest should be connected to its respective server, and incorrect server assignments between domains can cause LDAP search and synchronization issues. Proper domain controller assignment for both domaina.com and domainb.com is required.
Does the following use case correctly describe passthrough authentication?Solution: A user logs into identityNow using a password set in identityNow during registration.
Passthrough authentication in SailPoint IdentityNow refers to a method where the authentication process happens through a trusted identity provider (IdP), rather than using credentials stored directly in SailPoint IdentityNow. The key feature of passthrough authentication is that the user's login attempt is authenticated via external authentication mechanisms such as Active Directory, SAML-based Identity Providers (IdPs), or other federated identity providers.In the given use case, the user is logging into IdentityNow using a password set directly in IdentityNow during registration. This process describes local authentication (where IdentityNow manages the credentials), not passthrough authentication. Since passthrough authentication relies on external IdPs or federated systems, this case does not accurately describe passthrough authentication.
SailPoint IdentityNow Documentation on Authentication Methods.SailPoint IdentityNow Federation and SSO Configuration Guides.
Post your Comments and Discuss SailPoint IdentityNow-Engineer exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the IdentityNow-Engineer content, but please register or login to continue.