SailPoint IdentityNow-Engineer SailPoint Certified IdentityNow Engineer Exam Practice Test

Answer : B

In this scenario, the Virtual Appliances (VAs) should not reside in the DMZ (B), which is typically used for hosting services that need to be exposed to both internal and external networks, like web servers or email gateways. However, VAs require more direct and secure access to internal resources like Active Directory and databases. The VA needs to reside where it has secure and reliable connectivity to internal resources like Active Directory and database servers, which would be in the internal network.

Key Reference from SailPoint Documentation:

VA Placement Guidance: Virtual Appliances are placed within the internal network, where they can securely connect to Active Directory, databases, and other internal applications for synchronization and provisioning tasks.

Answer : A

Yes, the search syntax @accounts( source.name:'AD' AND state:'disabled' ) is correct for finding identities with disabled AD accounts. In this case, the query filters accounts based on the state being 'disabled,' which is valid and effective for identifying disabled accounts.

Key Reference from SailPoint Documentation:

Search by Account State: Using state:'disabled' is an accurate way to search for disabled accounts in SailPoint IdentityNow.

Answer : A

Yes, SailPoint IdentityNow APIs can be accessed and utilized by external clients such as cURL or Postman. These tools are commonly used for testing and interacting with RESTful APIs, and they work seamlessly with IdentityNow's API framework. For example, developers can use Postman or cURL to make API calls for various actions like managing identities, querying data, and triggering provisioning events.

Key Reference from SailPoint Documentation:

API Integration with Tools: SailPoint IdentityNow supports third-party tools like cURL and Postman for API interaction, as these clients can handle HTTP requests, which is how IdentityNow's APIs communicate.

Answer : A

Yes, SailPoint uses a proprietary fairness algorithm to manage and distribute workloads in its multi-tenant environment. This algorithm ensures that resources are allocated fairly among tenants, preventing any single tenant from consuming excessive resources at the expense of others. It helps maintain system performance and stability, balancing the processing load and providing equitable access to shared infrastructure in a multi-tenant setup.

SailPoint IdentityNow Multi-Tenant Architecture Documentation.

SailPoint IdentityNow Resource Allocation and Fairness Algorithm Guide.

Answer : A

Yes, the search syntax @accounts( source.name:'AD' AND state:'disabled' ) is correct, as it matches the necessary criteria for finding disabled AD accounts. This query searches for accounts in the AD source where the account state is set to 'disabled,' which effectively filters for the desired result.

Key Reference from SailPoint Documentation:

Correct Syntax for Disabled Accounts: The search correctly identifies accounts with a disabled state using this syntax.

Answer : B

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.

Answer : A

Yes, reviewing the log files in the /home/sailpoint/log directory is a standard troubleshooting step for diagnosing a failed VA. The log files, such as relay.log, vs_agent.log, and others, can provide detailed error messages and insights into what might be causing the VA failure, such as connectivity issues, service failures, or configuration problems.

Key Reference from SailPoint Documentation:

Log Files for VA Troubleshooting: SailPoint's best practices for troubleshooting VA issues involve reviewing log files to check for error messages or warnings that can help identify the root cause of the failure.