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
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
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.
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.
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