nerdexam
CompTIA

CV0-003 · Question #285

A cloud deployment engineer is modifying versions of the existing template image to instantiate new VMs. The engineer accomplishes this through the cloud self-service portal. After the version is…

The correct answer is D. Assign new IPs to the newly created VMs by changing and running the deployment template; and. After a template version change, a new VM with no connectivity most likely received an incorrect or conflicting IP assignment from the updated deployment template, which must be corrected and redeployed.

Troubleshooting

Question

A cloud deployment engineer is modifying versions of the existing template image to instantiate new VMs. The engineer accomplishes this through the cloud self-service portal. After the version is changed and a new VM is successfully started, it does not have any connectivity, and all ping tests to other VMs fail. Which of the following would be the BEST approach to solve the problem?

Options

  • AStart the console session to the VM; check network static routes; test the ping to default gateway
  • BDelete the VM; create a new flavor; turn on network service; add the new image to the template
  • CDelete the VM; check the IP assignment and planning; modify configuration in the deployment
  • DAssign new IPs to the newly created VMs by changing and running the deployment template; and

How the community answered

(36 responses)
  • A
    3% (1)
  • B
    11% (4)
  • C
    3% (1)
  • D
    83% (30)

Why each option

After a template version change, a new VM with no connectivity most likely received an incorrect or conflicting IP assignment from the updated deployment template, which must be corrected and redeployed.

AStart the console session to the VM; check network static routes; test the ping to default gateway

Checking static routes and pinging the default gateway from a console session diagnoses symptoms but does not address the root cause of an incorrect IP assignment introduced by the template version change.

BDelete the VM; create a new flavor; turn on network service; add the new image to the template

Creating a new flavor and re-enabling network service adds unneeded complexity and does not target the IP configuration error introduced by the template update.

CDelete the VM; check the IP assignment and planning; modify configuration in the deployment

Deleting the VM and manually modifying configuration is less efficient and less repeatable than correcting the deployment template, and does not prevent the same error on future deployments.

DAssign new IPs to the newly created VMs by changing and running the deployment template; andCorrect

Changing a template version can introduce incorrect IP address assignments or leave network parameters undefined, causing all connectivity to fail from the moment the VM is instantiated. Updating the deployment template with correct IP assignments and re-running it corrects the configuration at the source without unnecessary VM deletion or manual intervention.

Concept tested: IP configuration in cloud VM deployment templates

Source: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-launch-templates.html

Topics

#VM deployment#network connectivity#IP assignment#deployment templates

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full CV0-003 Practice