What is the difference between SCIM provisioning and provisioning via custom scripts?

• A. SCIM eliminates the need for provisioning entirely.
• B. SCIM is a legacy protocol; scripting is modern.
• C. SCIM standardizes provisioning; scripts are custom but less scalable.
• D. Custom scripts are always better for scalability.

Answer: (C)

SCIM provisioning is about a standardized way to create, update, and delete user accounts across many applications. Because SCIM defines a common data model and a standard set of operations, it lets you automate lifecycle management with one interoperable protocol. That standardization enables scalable, consistent provisioning across diverse systems without writing bespoke code for each app.

Provisioning with custom scripts is built per application, using that app’s specific API, data formats, and authentication. It works for a few systems, but as the number of apps grows, maintenance becomes heavy: you must map attributes per app, keep scripts up to date with API changes, and handle multiple authentication methods. This makes it less scalable and more brittle over time.

So the idea that SCIM standardizes provisioning while scripts are custom but less scalable best captures the practical difference. It also avoids claiming that provisioning would disappear with SCIM, and it explains why scripts aren’t inherently superior for large-scale environments.