SailPoint Exam IdentityNow-Engineer Topic 2 Question 12 Discussion

Actual exam question for SailPoint's IdentityNow-Engineer exam

Question #: 12
Topic #: 2

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.

AYes

BNo

Show Suggested Answer

Suggested Answer: B

No, the statement 'This item is complete' is vague and does not represent any actionable configuration when implementing a JDBC connector. An IdentityNow engineer needs to focus on specific technical configurations like setting up schemas, defining SQL queries, mapping attributes, and ensuring the correct service account permissions. Simply stating 'This item is complete' is not a valid step in the implementation process.

SailPoint IdentityNow JDBC Connector Implementation Checklist.

SailPoint IdentityNow Configuration and Implementation Documentation.

by Matthew at Mar 21, 2025, 08:25 AM

Limited Time Offer

25%

Off

Get Premium IdentityNow-Engineer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Jacklyn

3 months ago

This is definitely the way to go. No need to overcomplicate things. Just keep it simple and make sure it all works as intended.

upvoted 0 times

Yuki

2 months ago

B) No

upvoted 0 times

...

Reynalda

2 months ago

I agree, keeping it simple is key.

upvoted 0 times

...

Lawrence

2 months ago

A) Yes

upvoted 0 times

...

Gerri

3 months ago

Haha, I guess manually changing the state is the 'old school' way of doing it. Maybe they'll add a 'Lifecycle State Randomizer 3000' in the next update to make things more exciting!

upvoted 0 times

Louann

1 months ago

I prefer the manual way, keeps me on my toes!

upvoted 0 times

...

Louvenia

2 months ago

B) No

upvoted 0 times

...

Carma

2 months ago

Haha, that would definitely make things more interesting!

upvoted 0 times

...

Stephane

2 months ago

A) Yes

upvoted 0 times

...

Dorthy

3 months ago

I agree with Lenita, the solution provided seems logical and efficient for testing lifecycle state transitions.

upvoted 0 times

...

Bethanie

3 months ago

Sounds like a solid testing strategy. I would also recommend checking the audit logs to verify the state changes are being properly recorded.

upvoted 0 times

Laine

3 months ago

B) No

upvoted 0 times

...

Niesha

3 months ago

A) Yes

upvoted 0 times

...

Kristian

3 months ago

This looks good to me. I appreciate the attention to detail in the solution. Testing these kinds of workflows is crucial to ensure everything is working as expected.

upvoted 0 times

Alesia

1 months ago

User 4: A) Yes

upvoted 0 times

...

Jacob

1 months ago

User 3: A) Yes

upvoted 0 times

...

Avery

1 months ago

User 2: B) No

upvoted 0 times

...

Yong

2 months ago

User 1: A) Yes

upvoted 0 times

...

Michael

2 months ago

User 4: A) Yes

upvoted 0 times

...

Valentine

2 months ago

User 3: A) Yes

upvoted 0 times

...

Shasta

2 months ago

User 2: B) No

upvoted 0 times

...

Tora

2 months ago

User 1: A) Yes

upvoted 0 times

...

Leota

3 months ago

Yes, this seems like a thorough and practical approach to testing lifecycle state transitions. I like how it covers all the key steps - configuring the states, finding a test identity, manually changing the state, and verifying the results.

upvoted 0 times

...

Long

3 months ago

I disagree, I think there might be a better way to test lifecycle state transitions.

upvoted 0 times

...

Lenita

3 months ago

Yes, I think that is the recommended way to test lifecycle state transitions in IdentityNow.

upvoted 0 times

...