SailPoint IdentityNow-Engineer Exam Dumps

Yes, this statement is correct. When setting up a Virtual Appliance (VA) cluster, SailPoint does indeed create an asymmetric key pair based on a user-provided passphrase. This key pair is used for secure communication between the Virtual Appliance and the IdentityNow tenant. The asymmetric encryption model uses a public-private key pair where the private key is stored securely within the VA, and the public key is shared with the IdentityNow tenant to establish a secure, encrypted communication channel. This setup ensures that data exchanged between the VA and the IdentityNow tenant remains protected.

SailPoint IdentityNow Virtual Appliance Security Guide.

SailPoint IdentityNow Asymmetric Encryption and Key Management Documentation.

Yes, this is the recommended way to test lifecycle state transitions in IdentityNow. To validate how lifecycle states function, administrators can manually set up and enable lifecycle states for testing purposes. By selecting a test identity that is not already in the target state, manually transitioning that identity to the target state using the admin user interface provides a direct and controlled way to observe the transition. The results can be verified in the identity's activity page, where changes in the lifecycle state will be logged, helping to ensure that the lifecycle state functions as expected.

SailPoint IdentityNow Lifecycle Manager Documentation.

SailPoint IdentityNow Lifecycle State Configuration Guide.

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.

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.

Yes, a certification item can be reassigned multiple times during a certification campaign. If a reviewer is unable to certify an item or needs another individual to review the access, they can reassign the certification to a different reviewer. This reassignment functionality allows flexibility in handling access certifications and ensuring the right person evaluates the access. There are no limits on how many times an item can be reassigned, making it a versatile feature within the certification process.

SailPoint IdentityNow Certification Reassignment Feature Documentation.

SailPoint IdentityNow Certification Workflow Guide.