Free SailPoint IdentityNow-Engineer Practice Exam with Questions & Answers | Set: 2

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.

SailPoint IdentityNow allows HTML editing of email templates to customize the look, feel, and content of notifications. Administrators can modify email templates using HTML to include company branding, custom messages, and specific formatting based on their organization's communication needs.

SailPoint provides out-of-the-box email templates for common scenarios such as access requests, password resets, or provisioning notifications. Administrators can enhance these templates using HTML and inline CSS to personalize the messages for their users.

Key Reference from SailPoint Documentation:

Email Template Customization in IdentityNow: SailPoint supports the editing of email templates via HTML to meet specific organizational requirements. Administrators can navigate to the email templates section within the admin interface and update the HTML content as needed.

Yes, an access profile can be acknowledged during certifications. During access certification campaigns, reviewers can review access profiles as part of the items that need to be certified. They can either approve or revoke access to the access profiles, just like they would with individual entitlements. This ensures that users' access to these bundled entitlements is regularly reviewed and compliant with organizational policies.

References:

SailPoint IdentityNow Certification Campaigns Guide.

SailPoint IdentityNow Access Profile Certification Documentation.

The Web Services connector in IdentityNow does not exclusively support JSON content-types; it also supports XML as a content type for communication. JSON (JavaScript Object Notation) is widely used, but the connector is flexible and can be configured to handle XML-based APIs as well, depending on the requirements of the target system. Thus, it does not only support JSON.

References:

SailPoint IdentityNow Web Services Connector Documentation.

SailPoint IdentityNow Web Services Connector Content-Type Configuration Guide.

No, this example does not accurately describe an IdentityNow data flow. The incorrect part of this flow is that identity profiles are not created within the Virtual Appliance (VA). Identity profiles are created and managed directly within the IdentityNow tenant, not the VA. Additionally, the provisioning process is handled by the IdentityNow tenant through provisioning tasks and API calls to the VA for execution, but the VA does not initiate identity profile creation or manage the full synchronization of those profiles.

References:

SailPoint IdentityNow Identity Profile Configuration Guide.

SailPoint IdentityNow Virtual Appliance and Tenant Data Flow Documentation.

No, IdentityNow administrators do not have the option to choose how often updates to their tenant occur. SailPoint operates a multi-tenant SaaS model, where updates are rolled out centrally by SailPoint on a predefined schedule. SailPoint controls and manages updates to ensure consistency and security across all tenants. This means that all tenants receive updates automatically as part of SailPoint’s continuous delivery model, without the ability for individual admins to control or delay updates.

References:

SailPoint IdentityNow SaaS Release Management Guide.

SailPoint IdentityNow Multi-Tenant Environment Overview.

Yes, loading entitlement descriptions is considered a best practice before generating the campaign preview for a manager certification campaign. Providing clear and concise entitlement descriptions ensures that managers reviewing access during the certification process have a full understanding of what each entitlement or role entails. This helps in making informed decisions regarding whether an individual’s access should be approved or revoked.

Without proper descriptions, the campaign participants might have difficulty evaluating access, which can lead to inefficiencies or errors in the certification process.

References:

SailPoint IdentityNow Certification Campaign Best Practices.

SailPoint IdentityNow Campaign Preparation Guidelines.

Yes, the SCIM 2.0 Connector is the most suitable connector for this use case. The system described is a modern, cloud-based web application that exposes a fully compliant SCIM 2.0 interface and uses OAuth 2.0 client credentials for authentication. SCIM (System for Cross-domain Identity Management) is a standardized protocol designed to simplify identity management in cloud applications. The SCIM 2.0 Connector in SailPoint IdentityNow is specifically built to integrate with systems that provide a SCIM interface, making it the ideal connector for this scenario.

References:

SailPoint IdentityNow SCIM 2.0 Connector Guide.

SailPoint IdentityNow Cloud-Based Integration Documentation.

Yes, the fact that the disaster recovery (DR) VAs are not being utilized until a disaster recovery event occurs is a disadvantage. In this strategy, the DR VAs remain idle, leading to underutilization of resources. These VAs could otherwise handle workloads during normal operations to improve efficiency, distribute load, or reduce latency, especially if they are geographically closer to specific target systems. Relying on DR VAs only during failover scenarios limits their potential to optimize performance and balance loads in day-to-day operations.

References:

SailPoint IdentityNow Virtual Appliance Clustering and Disaster Recovery Documentation.

SailPoint IdentityNow High Availability and DR Strategies.

No, when deploying the Virtual Appliance (VA) using the AWS deployment option, the IdentityNow engineer does not need to convert the VA image. SailPoint provides an AWS-compatible Amazon Machine Image (AMI) that can be directly used to deploy the VA in AWS without any additional conversion steps. The AMI is shared with the customer’s AWS account, allowing for a streamlined deployment process.

Key Reference from SailPoint Documentation:

VA Deployment in AWS: SailPoint provides a ready-to-use AMI for AWS deployments, and no image conversion is necessary for this deployment method.