2V0-622 · Question #186
An administrator is deploying ESXi 6.x hosts using Auto Deploy and wants the image profile to be available, even after closing and opening a new PowerCLI window. Which command can be used to ensure th
The correct answer is B. Export-EsxImageProfile. To persist an image profile across PowerCLI sessions, it must be exported to a file on disk rather than kept only in memory.
Question
An administrator is deploying ESXi 6.x hosts using Auto Deploy and wants the image profile to be available, even after closing and opening a new PowerCLI window. Which command can be used to ensure that image profiles are preserved across PowerCLI sessions?
Options
- ASet-EsxImageProfile
- BExport-EsxImageProfile
- CSave-EsxImageProfile
- DPreserve-EsxImageProfile
How the community answered
(57 responses)- A5% (3)
- B91% (52)
- C2% (1)
- D2% (1)
Why each option
To persist an image profile across PowerCLI sessions, it must be exported to a file on disk rather than kept only in memory.
Set-EsxImageProfile modifies properties of an existing in-memory image profile but does not write it to disk for cross-session persistence.
Export-EsxImageProfile saves the image profile to a ZIP or ISO file on disk, making it available in future PowerCLI sessions. Because Auto Deploy image profiles created in-session exist only in memory, exporting is the correct method to ensure they survive session restarts. This cmdlet is the standard PowerCLI command for serializing image profiles for reuse.
Save-EsxImageProfile is not a valid PowerCLI cmdlet and does not exist in the VMware Image Builder module.
Preserve-EsxImageProfile is not a valid PowerCLI cmdlet and does not exist in any VMware PowerCLI module.
Concept tested: Persisting ESXi image profiles across PowerCLI sessions
Source: https://developer.broadcom.com/powercli/latest/vmware.vimautomation.imagecustomization/commands/export-esximageprofile
Topics
Community Discussion
No community discussion yet for this question.