Administering Cloud EPM: The Platform Beneath the Business Processes · Module 7 · Provisioning at Scale
Lab: design the synchronization and test the leaver
Lesson 87 of 201 · 2 min
An hour and a quarter, and the title names the graded part. Seven deliverables. A written synchronization design for Northwind: source, target, filter scope, attribute mapping, schedule, and an owner on each side. Synchronization configured between two identity domains, with a joiner and a leaver tested — or, on the follow-along path, a complete configuration plan with the same tests specified. A filter scope justified against Northwind's population. Application roles assigned to synchronized groups, demonstrating the division of labour. A password policy matching a stated corporate standard, with a note on what it does and does not govern once SSO is enabled. A written change process agreed with the notional identity team: what happens when a group is renamed, when a new group needs access, and when synchronization fails. And a monitoring plan for synchronization health. The acceptance criteria. THE LEAVER PATH IS EXPLICITLY TESTED, NOT ASSUMED. The filter scope…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Administering Cloud EPM: The Platform Beneath the Business Processes, with a certificate on completion and a fourteen-day refund window.
In this module: Module 7 · Provisioning at Scale
- 1Why manual provisioning fails
- 2What synchronization does and does not carry
- 3Synchronizing across identity domains
- 4Synchronizing specific users and groups
- 5Synchronizing from an external directory
- 6Groups for application-level role assignment
- 7Password policies
- 8Email notifications and password resets
- 9What breaks
- 10Lab: design the synchronization and test the leaver