Pass the SailPoint Identity Security Engineer IdentityNow-Engineer Questions and answers with CertsForce

No, the provided steps are not correct. The sequence of actions is misplaced:

Step 1: Before clicking "Test Connection," you need to download or procure the VA image and import it into the virtualization platform.

Step 6: After logging in and changing the password, the next step is to configure the networking settings, not downloading the image again.

Step 12: After uploading the config.yaml, you should proceed with testing the connection to ensure the VA is correctly configured and can communicate with IdentityNow.

Corrected Steps:

Download / procure the VA image.

Configure networking configurations (as needed).

Click Test Connection on the VA configuration.

References:

SailPoint IdentityNow Virtual Appliance Installation and Configuration Guide.

SailPoint IdentityNow Virtual Appliance Test Connection Documentation.

No, deleting the access profile is not the correct way to meet the requirement of removing approval for access requests. The access profile defines the entitlements and permissions that users can request for an application. Deleting it would remove the entire ability to request access, rather than just removing the approval workflow. The correct step would be to modify the approval settings in the access profile (as explained in Question 44), not to delete it.

Key Reference from SailPoint Documentation:

Access Profile Management: Modifying approval settings in the access profile is the appropriate step to meet management's new requirement, not deleting the profile itself.

Yes, "Create Account" is a valid operation type for the Web Services connector in SailPoint IdentityNow. The Web Services connector is designed to interact with REST or SOAP APIs, allowing it to perform operations such as account creation, updating, or deleting accounts on external systems. The "Create Account" operation is a standard function used when provisioning new identities to external applications or systems through the connector.

References:

SailPoint IdentityNow Web Services Connector Operations Guide.

SailPoint IdentityNow Web Services Connector API Provisioning Documentation.

No, this statement is incorrect. While IdentityNow does use TLS (Transport Layer Security) for securing data in transit, TLS is not a hashing algorithm; it is a protocol used for encryption to ensure secure communication over networks. Additionally, IdentityNow uses hashing algorithms for securely storing passwords and answers to security questions (e.g., SHA-256 or bcrypt), but it does not use TLS for hashing these values. Hashing algorithms are one-way functions that help store sensitive data securely by converting them into irreversible fixed-length representations.

TLS protects data during transmission by encrypting it, while hashing is used for securing stored data such as passwords.

References:

SailPoint IdentityNow Encryption and Security Practices Documentation.

SailPoint IdentityNow Password Hashing and Encryption Mechanisms Guide.

Yes, verifying that the Virtual Appliance (VA) has connectivity to the internet is a critical step when troubleshooting a "failed" status in IdentityNow. The VA requires internet connectivity to communicate with SailPoint IdentityNow’s cloud services for synchronization, updates, and other key functions. If the VA is unable to reach the internet, it can lead to a failed status. Logging in to the VA’s console to test network connectivity (e.g., using ping or curl commands) is an important step in diagnosing the issue.

Key Reference from SailPoint Documentation:

VA Internet Connectivity Troubleshooting: SailPoint recommends checking the network connectivity as one of the first steps when the VA shows a failed status.

https://identityNowacme.com is not typically considered a vanity URL. While it includes the "identityNow" term, it does not appear to follow the format of a vanity URL, which generally includes a company-specific subdomain (like my) and a custom domain (example.com). In this case, the URL is more generic and lacks the branding or simplicity typically associated with vanity URLs.

Key Reference from SailPoint Documentation:

Vanity URL Structure in IdentityNow: Vanity URLs typically feature a customized subdomain that reflects the organization’s branding, and identityNowacme.com does not fit this pattern.

Yes, a non-production tenant is typically used for testing new features before they are deployed to the production environment. This allows administrators to validate functionality, identify potential issues, and ensure the features work as expected without affecting the live users and operations.

Key Reference from SailPoint Documentation:

Testing New Features in Non-Production: SailPoint advises using non-production environments for testing new functionalities to safeguard production environments from untested changes.

No, verifying that the VA is configured for automatic updates by setting autoupdate=true in the config.yaml file is not directly related to troubleshooting a failed status on the VA. While keeping the VA updated is important for long-term stability and functionality, the configuration for automatic updates does not resolve immediate connection or service failure issues. The troubleshooting focus should be on network connectivity, service status, and log reviews.

Key Reference from SailPoint Documentation:

VA Autoupdate Configuration: Configuring the VA for automatic updates is a best practice for maintaining up-to-date software but is not a direct troubleshooting step for addressing an immediate VA failure.

No, a user with Report-admin level permissions cannot invite new users to IdentityNow. The Report-admin role in IdentityNow is restricted to managing reports—this includes generating, viewing, and managing access to reports but does not extend to user management tasks such as inviting new users. Only users with Admin, Org Admin, or other higher-level roles with explicit user management permissions can invite new users to the platform.

References:

SailPoint IdentityNow Role-Based Access Control Documentation.

SailPoint IdentityNow Permissions Matrix for Admin Roles.

Yes, this example accurately describes an IdentityNow data flow for password changes in an Active Directory environment. When a user changes their password in IdentityNow, the request is sent to the virtual appliance, which then communicates with the IQService host. The IQService is responsible for making changes to Active Directory. This flow reflects the standard procedure for password management using IdentityNow with Active Directory, where the virtual appliance and IQService coordinate to complete the password change.

References:

SailPoint IdentityNow Password Management Documentation.

SailPoint IdentityNow IQService and Virtual Appliance Data Flow Guide.