Refer the Exhibit. An administrator is testing a newly created Windows 2016 template in VMware Aria Automation Assembler. While using the Test option from within the VMware Aria Automation template…

Question

Exhibit

Options

• AThe administrator did not associate a cloud zone to the project.
• BDuring the machine allocation phase. VMware Aria Automation Assembler could not find
• CThe administrator did not add a cloud account.
• DThe network profile created did not have the correct capability tag.

• A
  12% (5)
• B
  27% (11)
• C
  7% (3)
• D
  54% (22)

Explanation

Option D is correct because VMware Aria Automation Assembler uses capability tags to match template resource requests with available infrastructure profiles - if the network profile lacks the tag that the template's constraint is looking for, the allocator cannot find a suitable network during the provisioning phase, which produces the exhibited error. Option A is wrong because a missing cloud zone association would prevent any deployment from being attempted at all, surfacing a different and earlier error about no available deployment targets. Option C is similarly wrong because the absence of a cloud account is a foundational configuration gap that would block cloud zone setup entirely, not cause a late-stage allocation failure during template testing. Option B is a truncated distractor that describes a symptom (allocation failure) rather than a root cause, making it a rephrasing of the error itself rather than an explanation for it.

Memory tip: Think of capability tags as a key-and-lock system - the template holds a key (constraint tag) and goes looking for a lock (capability tag on the network profile); if no lock matches, the door won't open and deployment fails.

No community discussion yet for this question.