Master SailPoint IdentityNow-Engineer Exam with Reliable Practice Questions
Upgrade to Premium
Is this statement correct about security and/or encryption of data?
Solution: identityNow uses a hashing algorithm for secure encryption of data in transit and uses TLS for hashing passwords and the answers to security questions
Correct : B
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.
SailPoint IdentityNow Encryption and Security Practices Documentation.
SailPoint IdentityNow Password Hashing and Encryption Mechanisms Guide.
Start a Discussions
Is this the recommended way to test lifecycle state transitions in IdentityNow?
Solution: Configure and enable lifecycle states. Find a test identity that is not in the target lifecycle state. Manually change the test identity lifecycle state to the target state from the admin user interface Verify the results of the lifecycle slate in the identity's activity page.
Correct : A
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.
Start a Discussions
Does this example accurately describe an IdentityNow data flow?
Solution:
1. An IdentityNow engineer clicks "start manual aggregation".
2. The IdentityNow tenant contacts the Active Directory domain controller.
3. The domain controller sends a list of accounts to the virtual appliance.
4. The virtual appliance masks sensitive information and sends a list of accounts to the IdentityNow tenant.
Correct : B
No, this example does not accurately describe an IdentityNow data flow. The step where the domain controller sends a list of accounts directly to the virtual appliance is incorrect. Instead, during manual aggregation, the virtual appliance is responsible for initiating the connection to the domain controller (or other authoritative source), retrieving account data, and then sending the results to the IdentityNow tenant. Sensitive information is masked before sending the data from the virtual appliance to the IdentityNow tenant, but the domain controller does not interact directly with the IdentityNow tenant.
SailPoint IdentityNow Aggregation Process Documentation.
SailPoint IdentityNow Virtual Appliance Data Flow Guide.
Start a Discussions
Does this example accurately describe an IdentityNow data flow?
Solution:
1. The IdentityNow engineer logs into the virtual appliance and creates a new identity profile.
2. The virtual appliance contacts the IdentityNow tenant to synchronize the identity profile.
3. The IdentityNow tenant provisions accounts to source systems.
4. The IdentityNow tenant sends an API call to the virtual appliance with confirmation that accounts were provisioned
Correct : B
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.
SailPoint IdentityNow Identity Profile Configuration Guide.
SailPoint IdentityNow Virtual Appliance and Tenant Data Flow Documentation.
Start a Discussions
Does this example accurately describe an IdentityNow data flow?
Solution:
1. Identity data is aggregated from an authoritative source.
2. The aggregated data is used to build an identity model.
3. Accounts are provisioned to source systems.
4 Identity attributes are periodically synchronized to write-enabled systems
Correct : B
No, this example does not accurately describe the complete data flow in IdentityNow. While it correctly mentions identity aggregation and the building of an identity model, the third step, 'Accounts are provisioned to source systems,' is not always part of the identity aggregation process. Provisioning is typically a separate workflow initiated by access requests or certification decisions, not directly tied to identity aggregation. Additionally, the periodic synchronization of identity attributes happens as part of identity refreshes but is not necessarily tied to provisioning accounts in all cases.
SailPoint IdentityNow Aggregation and Identity Model Documentation.
SailPoint IdentityNow Provisioning Workflow Guide.
Start a Discussions