If you see 'error comparing selected policies' in Policy History, what is the likely cause?

• A. Only 1 policy is selected for comparison
• B. Policies must be identical
• C. Policy History is unavailable
• D. User lacks permission

Answer: (A)

The key idea here is that the policy comparison feature needs at least two policies to compute differences. If you see an error about comparing selected policies, it almost always means only one policy was chosen for the comparison. There’s nothing to contrast against, so the tool can’t perform a comparison and flags an error.

So, select two or more policies (or two versions of a policy) to compare, and the tool will show the differences between them. The other options don’t fit because:

• If policies were identical, the comparison would simply show no differences, but the operation would still run if multiple policies were selected.

• If Policy History were unavailable, you’d expect a system-wide access or availability issue, not an error tied to the act of selecting only one item.

• If the user lacked permission, you’d see a permission-denied message, not an error about comparing the selected policies.