nerdexam
Broadcom-VMware

2V0-31.24 · Question #62

An attempt upgrade an existing cloud proxy for use with VMware Aria Automation fails with a manifest access error. What is a possible reason?

The correct answer is B. The /opt/vmware/var/lib/vami/update/provider/provider-runtime.xml manifest file that is. A manifest access error during an upgrade attempt of an existing cloud proxy for use with VMware Aria Automation is likely due to incorrect access permissions on the manifest file. The file located at /opt/vmware/var/lib/vami/update/provider/provider-runtime.xml must have the…

Section 7 - Troubleshoot VMware Aria Automation

Question

An attempt upgrade an existing cloud proxy for use with VMware Aria Automation fails with a manifest access error. What is a possible reason?

Options

  • AThe /opt/vraware/var/lib/vami/update/provider/provider-runtime.xml manifest file that is
  • BThe /opt/vmware/var/lib/vami/update/provider/provider-runtime.xml manifest file that is
  • CThe version of the cloud proxy is newer as the version supported by your VMware Aria
  • DThe /opt/vraware/var/lib/vami/update/provider/provider-runtime.xml manifest file that was used

How the community answered

(34 responses)
  • A
    15% (5)
  • B
    71% (24)
  • C
    9% (3)
  • D
    6% (2)

Explanation

A manifest access error during an upgrade attempt of an existing cloud proxy for use with VMware Aria Automation is likely due to incorrect access permissions on the manifest file. The file located at /opt/vmware/var/lib/vami/update/provider/provider-runtime.xml must have the correct permissions to be accessed and used during the upgrade process. If the permissions are incorrect, the system will not be able to read or modify the file, leading to the manifest access

Topics

#cloud proxy upgrade#manifest file#upgrade error#troubleshooting

Community Discussion

No community discussion yet for this question.

Full 2V0-31.24 Practice