After an initial deployment of vRealize Operations (vROps) and configuration of the vCenter Cloud Account, an administrator notices that a vSphere Solution's Default Policy was created. What is the…

Question

Options

• AThe default policy setting has been defined by another administrator.
• BThis policy was added during the installation of the vROps management pack for vSphere.
• CAll the default policy settings are inherited from the base settings.
• DSettings of this policy are defined during the vROps OVF deployment.

• A
  2% (1)
• B
  2% (1)
• C
  89% (47)
• D
  8% (4)

Explanation

Option C is correct because vROps uses a hierarchical policy inheritance model - the vSphere Solution's Default Policy automatically inherits all its settings from the Base Policy (the system-wide root policy), which is why it appears fully configured without any manual input.

Why the distractors are wrong:

• A is wrong because the Default Policy is system-generated upon Cloud Account configuration, not manually created by any administrator.
• B is wrong because the vSphere management pack installation enables the vSphere Solution but does not define or populate the Default Policy settings - that's handled by the policy hierarchy.
• D is wrong because the OVF deployment only provisions the vROps appliance infrastructure; policy settings for vSphere Solutions are not configured at that stage.

Memory tip: Think of vROps policies like a CSS stylesheet cascade - the Base Policy is the "parent" stylesheet, and the Default Policy is a "child" that inherits everything from it unless explicitly overridden. No parent = no settings, which is why Base Settings are always the origin.

No community discussion yet for this question.