What API version replaces the target org metadata completely when you deploy permission sets and profile changes?

What API version replaces the target org metadata completely when you deploy permission sets and profile changes?

• A. API version 38.0
• B. API version 40.0 and later
• C. API version 39.0 or earlier
• D. API version 41.0

Answer: (B)

When you deploy profiles and permission sets, the behavior of the metadata deployment changes with API version. In API version 40.0 and later, deploying these types replaces the target org’s metadata for those types completely with what you package. In other words, the target’s profile and permission set definitions become exactly what you deploy—nothing from the previous state is left unless it’s included in the deployment. This full-replacement behavior makes deployments predictable across environments, but it also means you must include the full desired configuration in your package to avoid missing or unintended settings being carried over. Prior versions didn’t enforce this full replace as strictly, which could lead to partial updates or drift if configurations weren’t completely mirrored in the deployment package. So the version that ensures complete replacement is 40.0 and later.

When you deploy profiles and permission sets, the behavior of the metadata deployment changes with API version. In API version 40.0 and later, deploying these types replaces the target org’s metadata for those types completely with what you package. In other words, the target’s profile and permission set definitions become exactly what you deploy—nothing from the previous state is left unless it’s included in the deployment. This full-replacement behavior makes deployments predictable across environments, but it also means you must include the full desired configuration in your package to avoid missing or unintended settings being carried over.

Prior versions didn’t enforce this full replace as strictly, which could lead to partial updates or drift if configurations weren’t completely mirrored in the deployment package. So the version that ensures complete replacement is 40.0 and later.