Loading...
Loading...
Browse 8 real-world technical and behavioral interview questions about Change management. Review scenarios, edge cases, and architectural best practices.
Entitlements change through deployment paths that no access review inspects, so the only reliable detection is a snapshot of effective permissions diffed on every release, with the diff cleared by someone who did not ship it.
Permission data is as privileged as the code that reads it, so a bulk write to it needs the same review, staged rollout and reversibility as a deploy. Derive grants from a source of truth rather than stamping them, assert tenant invariants continuously, and know how long a cached decision keeps the mistake alive.
Blast radius is a property of the change process, not of the redundancy diagram - identical config applied to both halves of a resilient pair fails both. You need staged exposure with soak time, subscriber-visible health checks, a management path that survives the outage, and a rollback that has been executed.
Removing humans from production moves the privilege into the pipeline, so the boundary becomes who can change what it runs and which identity it assumes. Duties are separated by branch protection, environment approvals and deploying by digest, and it fails when one change alters both code and workflow.
Configuration, feature flags, content and reference data, schema migrations, infrastructure definitions and dependency updates all change production behaviour, and most organisations ship them through channels that were designed to be faster than the release pipeline.
Correlation is a traversal of the inventory graph, and an upgrade changes exactly the part being traversed. Model planned as well as as-built state, carry the set of resources a change touches as data, scope suppression to that set rather than to the time window, and confirm recovery positively.
Start from the business problem and the place where work actually waits, then change the system around the teams - funding, governance, handoffs, utilisation targets. Transformations disappoint because the team-level ceremonies are adopted and the management system that produced the delay is left untouched.
Own the decision publicly without pretending you authored it, find out individually what each person believes they have lost since the answers differ, then either win back real scope or say honestly that the team is now smaller than its ambitions. Quiet resistance costs you the team faster than the reorg did.