Review the steps.
1._____________________________________.
2 Import the virtual appliance (VA) image to the virtuahzation platform.
3. Start the VA.
4. Log in to the VA using the default credentials.
5. Change the password for the SailPoint user.
6______________________________________
7. Create a new VA cluster in IdentityNow.
8. Create a new VA configuration in IdentityNow.
9. Download / procure the config.yaml.
10. Configure the keyPassphrase in the config.yaml.
11. Upload the config.yaml into the VA.
12._____________________________________
Solution: 1. Configure networking configurations (as needed) 6. Click Test Connection on the VA configuration. 12. Download / procure the VA image.
No, the provided steps are incorrect. Specifically:
Step 1: Before importing the Virtual Appliance (VA) image, you need to first download or procure the VA image from SailPoint. Only then can you proceed with importing the image into the virtualization platform.
Step 6: After changing the password for the SailPoint user, the next logical step is to configure the networking settings (if needed) to ensure the VA can communicate with the IdentityNow tenant.
Step 12: The final step should not be to download the VA image again. Instead, after configuring the config.yaml, you should test the connection to ensure the VA can properly communicate with IdentityNow.
Corrected Steps:
Download / procure the VA image.
Configure networking configurations (as needed).
Click Test Connection on the VA configuration.
SailPoint IdentityNow Virtual Appliance Setup Guide.
SailPoint IdentityNow Virtual Appliance Networking Configuration.
A customer wants to configure a virtual appliance (VA) to use a static IP address. Does this file on the VA need to be modified to perform the configuration?
Solution: /home/sailpoint/proxy.yaml
The /home/sailpoint/proxy.yaml file is used for proxy settings, not for configuring the Virtual Appliance to use a static IP address. This file is typically modified to configure outbound proxy settings for the VA if it needs to route traffic through a proxy server. Static IP address configuration is handled elsewhere, at the operating system or network configuration level.
SailPoint IdentityNow Virtual Appliance Proxy Configuration Documentation.
SailPoint IdentityNow Network Settings Documentation.
When preparing for a manager certification campaign is this a step that is considered a best practice before the campaign preview is generated?
Solution: validate the email template. Certification Due
Yes, validating the email template (e.g., Certification Due) is a best practice before the campaign preview is generated. Communication during a certification campaign is key to ensuring that managers are aware of their tasks and deadlines. Validating the email templates helps ensure that the messaging is clear, correct, and aligned with the campaign's objectives. It also ensures that any necessary details, such as deadlines, instructions, and links to the certification tasks, are properly included.
Proper validation of email templates helps avoid communication issues that could delay or negatively impact the campaign's success.
SailPoint IdentityNow Certification Campaign Email Templates Guide.
SailPoint IdentityNow Best Practices for Campaign Communication.
Is this statement accurate regarding SailPoint's multi-tenant processing environment?
Solution: identityNow admins have the option to choose how often updates to their tenant occur.
No, IdentityNow administrators do not have the option to choose how often updates to their tenant occur. As part of SailPoint's multi-tenant SaaS platform, updates are managed and controlled by SailPoint and are pushed out automatically to all tenants. Administrators do not have the ability to schedule or defer updates, as this ensures all customers are running on the latest and most secure version of the software.
SailPoint IdentityNow SaaS Release and Update Policy.
SailPoint IdentityNow Multi-Tenant Environment Overview.
Is the following true about custom connectors in IdentityNow?
Solution: Custom connector are developed and compiled inside identityNow.
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.
