A developer updated a blueprint to ensure that the IP address of the VM is reserved in IPAM as part of the deployment process. The developer noticed that when new VMs are created, they still get a…

The correct answer is B. Developer created a post-create task for reserving the IP address. The most likely reason for this behavior is that the developer created a post-create task for reserving the IP address. A post-create task is executed after the VM is created and powered on, which means that the VM already obtained a DHCP IP address before the task is run. To…

Monitor and Troubleshoot Automation

Question

A developer updated a blueprint to ensure that the IP address of the VM is reserved in IPAM as part of the deployment process. The developer noticed that when new VMs are created, they still get a DHCP IP address and not a reserved IP address. What is the most likely reason for this behavior?

Options

ADeveloper created a pre-create task for reserving the IP address
BDeveloper created a post-create task for reserving the IP address
CDeveloper forgot to save the updated blueprint
DDeveloper forgot to publish the updated blueprint

How the community answered

(31 responses)

A
3% (1)
B
71% (22)
C
16% (5)
D
10% (3)

Explanation

The most likely reason for this behavior is that the developer created a post-create task for reserving the IP address. A post-create task is executed after the VM is created and powered on, which means that the VM already obtained a DHCP IP address before the task is run. To reserve the IP address in IPAM as part of the deployment process, the developer should create a pre- create task instead. A pre-create task is executed before the VM is created and powered on, which allows the task to reserve the IP address in IPAM and assign it to the VM.

Topics

#IPAM#blueprint task ordering#pre-create task#post-create task

Community Discussion

No community discussion yet for this question.

Full NCP-MCA Practice