1Y0-A15 · Question #14
Scenario: An engineer must convert a single volume of a physical disk on a physical machine to a virtualized instance in Citrix Xen Virtual Appliance format. The XenConvert 2.01 tool has been…
The correct answer is A. XenConvertCli P2Xva Server 2003 C:N:misc IE. See the full explanation below for the reasoning.
Question
Scenario: An engineer must convert a single volume of a physical disk on a physical machine to a virtualized instance in Citrix Xen Virtual Appliance format. The XenConvert 2.01 tool has been downloaded and the engineer has chosen to utilize the Tool's command line interface to perform the required conversions. The following is information about the current environment:
Workload Name: Server 2003 Physical Volume: C:
Destination Folder: N:misc Hostname: XenVA Username: root Password: Password 123 Which command must the administrator run in order to complete the required conversion?
Options
- AXenConvertCli P2Xva Server 2003 C:N:misc IE
- BXenConvertCli P2Vhd Server2003 C:N:-misc XenVA
- CXenCovertCli P2XenServ Server 2003 N:misc root Password123IE
- DXenConvertCli P2XenServer Server2003 C:N:miscXenVA root Password123IE
How the community answered
(46 responses)- A74% (34)
- B13% (6)
- C4% (2)
- D9% (4)
Community Discussion
7
Kemal J.Feb 1, 2026A is your answer, because the scenario explicitly calls for XVA format conversion, so P2Xva is the correct conversion type, and the parameters line up with the given workload name, source volume, and destination folder without dragging in XenServer credentials that only apply when you are pushing directly to a live host.
Orla P.Jan 18, 2026Option A, though that destination path really should have a backslash before misc.
Samuel O.Jan 21, 2026Good catch on the backslash, Orla, and worth adding that if anyone is scripting that path in a batch file or registry entry, missing that separator will silently drop files into the wrong directory with no error thrown.
Carlos M.Feb 10, 2026Honestly I kept staring at D because it had all the fields filled in and looked the most "complete," but then I noticed the question specifically says XVA format, not XenServer, so P2Xva is the right conversion type and the destination is just the folder plus workload name with no hostname or credentials needed for a local XVA conversion. A is the one.
Samuel O.Feb 13, 2026Option A is the move, but why does P2Xva not need hostname credentials here?
Jovan I.Jan 31, 2026The conversion type here is P2XenServ because you are pushing the workload to a XenServer host, not packaging a local XVA file, and option C is the only one that includes both the hostname and the credentials in the right positional order for the CLI syntax. Yeah the workload name has a space and the destination looks a little off, but C is still the closest match to what XenConvert 2.01 actually expects when you are doing a physical-to-XenServer job with auth parameters.
Carlos M.Feb 2, 2026Jovan, the correct answer is A because XenConvert 2.01 CLI syntax for a P2XenServer job puts the conversion type flag before the destination host, and option A matches that order with the proper parameter names, while C has the credential arguments in the wrong sequence relative to what the tool actually parses. The space in the workload name being quoted correctly in A is also part of what makes it the right pick, not just a cosmetic detail.