Which is a documented drawback of assigning a Dynamic Extension to a parameter?

Which is a documented drawback of assigning a Dynamic Extension to a parameter?

• A. It reduces performance negligible
• B. It allows inheritance of global settings
• C. Each parameter in each template must be maintained separately and they do not inherit system-wide settings
• D. It automatically applies to all templates

Answer: (C)

Dynamic Extension on a parameter creates a setup where the parameter’s configuration is tied to each template individually. That means you have to maintain every parameter in every template separately, and those parameters do not inherit global or system-wide settings. The consequence is a notable maintenance burden: any change to defaults or global policies must be replicated across all templates, increasing the chance of drift and inconsistency. This is why it’s described as a drawback. It doesn’t automatically apply to all templates, nor does it allow inheritance of global settings; those behaviors aren’t how this feature works, which is why the other statements don’t fit.

Dynamic Extension on a parameter creates a setup where the parameter’s configuration is tied to each template individually. That means you have to maintain every parameter in every template separately, and those parameters do not inherit global or system-wide settings. The consequence is a notable maintenance burden: any change to defaults or global policies must be replicated across all templates, increasing the chance of drift and inconsistency. This is why it’s described as a drawback. It doesn’t automatically apply to all templates, nor does it allow inheritance of global settings; those behaviors aren’t how this feature works, which is why the other statements don’t fit.