An implementer activates every IRM-related plugin “just in case” without a checklist. What practice should replace that approach?
Select an answer to reveal the explanation.
Short Explanation
“Just in case” plugin shopping turns the instance into a flea market of half-configured apps. The checklist says activate what the agreed use case needs—nothing more on day one. Scope first, then licenses and plugins follow the plan.
Full Explanation
Checklist-driven IRM implementations activate plugins and applications that support the signed-off use cases, reducing unused surface area and configuration drift. Indiscriminate activation complicates testing, roles, and support without advancing outcomes. Deliberate activation matched to scope is the planning standard.