An administrator wants to create a blueprint for a development environment that uses an existing...

To automate the creation of a new user in GitLab for every new development environment, the administrator should perform the following tasks within a Calm blueprint:

Create an HTTP pre-create task to create the user in GitLab via REST API. This task will send an HTTP request to the GitLab server with the user information and credentials, and receive a response with the user ID and status. The administrator can use the response to verify the user creation and store the user ID as a variable for later use.

Create runtime-editable variables for user and password in the blueprint. These variables will allow the administrator to specify the user name and password for the new GitLab user at the time of launching the blueprint. The variables can be passed as parameters to the HTTP pre-create task and used in the REST API call.

The other two options are not correct because:

Adding a task within the service to ask for user and password at runtime is redundant and unnecessary, as the runtime-editable variables can already provide this functionality.

Creating a task script to login with ssh to GitLab and create a random user and password is not a good practice, as it exposes the GitLab server to security risks and does not use the REST API that GitLab provides for user management. References:

Nutanix Certified Professional - Multicloud Automation (NCP-MCA) 6.5 Exam, page 17

Nutanix Calm User Guide, section “HTTP Task”

GitLab API Documentation, section “Create user”