1V0-603 · Question #108
Your company is moving cloud providers from Amazon EC2 to VMware vCloud Air. The IaaS Administrator is cleaning up the remaining components. What is a valid component that the IaaS administrator can…
The correct answer is C. Amazon AWS Endpoint. See the full explanation below for the reasoning.
Question
Your company is moving cloud providers from Amazon EC2 to VMware vCloud Air. The IaaS Administrator is cleaning up the remaining components. What is a valid component that the IaaS administrator can remove?
Options
- AAmazon AWS Data Collector
- BAmazon AWS Data Templates
- CAmazon AWS Endpoint
- DAmazon AWS Instantiator
How the community answered
(47 responses)- A13% (6)
- B6% (3)
- C79% (37)
- D2% (1)
Community Discussion
4The answer is C, Amazon AWS Endpoint, and if you have ever actually decommissioned a cloud integration in vRealize Automation you will recognize this immediately. The Endpoint is the registered connection that ties vRA back to the AWS account, and removing it is exactly what an IaaS Administrator owns in the vRA hierarchy. Data Collectors are infrastructure-level agents that can serve multiple endpoints, so you would not necessarily yank those just because one cloud provider is going away. Templates are more of a catalog-layer concern and sit above the IaaS Administrator's lane. The exam is testing whether you know that the Endpoint object is the discrete, removable hook that represents a specific external cloud connection, and the IaaS Administrator is the role with the authority and scope to clean that up during a migration like this.
The answer is C, the Amazon AWS Endpoint. The Endpoint is the actual registered connection object inside vCloud Connector that ties your vCloud Air organization to the AWS environment, so once you are fully off EC2 it is the clean, sanctioned thing to remove. The Data Collector is infrastructure-level plumbing that can serve multiple endpoints and is not AWS-specific, the Templates can still carry value if you ever need to reference old workload sizing, and Instantiator is straight-up not a real VMware construct, it is a trap option. When I sat the exam I almost second-guessed myself on A because I had spent the week before studying Data Collectors and they felt very "AWS-specific" in my head, but I remembered that the Collector talks to many endpoints and you decommission the Endpoint first, which snapped me back to C.
Took this one on my actual exam and almost second-guessed myself, but think of a cloud endpoint like the electrical outlet in your old apartment, it is the physical connection point to that provider, so when you move out you cap off that outlet, meaning you remove the Amazon AWS Endpoint, option C. The other choices sound plausible but they are not real removable objects in vCloud Automation Center, and once I remembered that an endpoint is simply the registered connection to a cloud account, the answer locked right in.
Solid analogy, and the registration angle is exactly right, though I would add that before you delete that AWS endpoint in vCAC you want to confirm no active blueprints or reservations are still pointing at it, otherwise you will leave orphaned catalog items that fail silently on provision.