Template Manager supports template-level overrides to determine after how many days a user's Epic-Crystal subscription should be inactivated.

Template Manager supports template-level overrides to determine after how many days a user's Epic-Crystal subscription should be inactivated.

• A. Not supported
• B. True
• C. Requires additional license
• D. Not configurable

Answer: (B)

The feature being tested is the ability to customize when a user’s Epic-Crystal subscription is inactivated using template-level overrides. This means you can set the inactivation timing differently for each template, rather than applying one global rule to all subscriptions. Because Template Manager does support these per-template overrides to determine how many days pass before inactivation, the statement is correct. In practice, you’d configure the number of days directly within each template’s settings to tailor the lifecycle for different templates. The other options would contradict this capability, since the feature does exist and doesn’t require an extra license or removal of configurability.

The feature being tested is the ability to customize when a user’s Epic-Crystal subscription is inactivated using template-level overrides. This means you can set the inactivation timing differently for each template, rather than applying one global rule to all subscriptions. Because Template Manager does support these per-template overrides to determine how many days pass before inactivation, the statement is correct. In practice, you’d configure the number of days directly within each template’s settings to tailor the lifecycle for different templates. The other options would contradict this capability, since the feature does exist and doesn’t require an extra license or removal of configurability.