Self-Service (formerly Calm) automatically cleans up the database every 3 months. This regular maintenance task helps manage database size and performance by removing old and unnecessary data.
Reference:
Nutanix Calm documentation on Database Cleanup.
Nutanix Best Practices for Calm Maintenance.

The macro @@{calm_runbook_name}@@ is included in the Macros Virtual Machine Common Properties. This macro provides the name of the runbook that is being executed, which is useful for referencing and logging purposes within tasks and scripts.
Reference:
Nutanix Calm documentation on Macros.
Nutanix Best Practices for Using Macros in Calm.

The archived application logs within Prism Central can be found under Services > Calm > Settings. Calm automatically archives run logs of the deleted applications and custom actions that are older than three months. The administrator can download the archives within 7 days from the time of archive creation. For a running application, data is not archived for the system-generated Create actions. Reference: Nutanix Support & Insights

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. Reference:
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"

When configuring Playbooks to automate the scaling of CPU and memory resources for VMs, the administrator should consider the following prerequisites:
CPU can be added to a powered on VM if the guest OS supports it. This is also known as hot-plug CPU. The administrator should check the compatibility of the guest OS and the hypervisor before enabling this feature. For example, Windows Server 2019 supports hot-plug CPU on AHV, ESXi, and Hyper-V, but not on XenServer1.
Memory can be removed from a powered on VM if the guest OS supports it. This is also known as hot-unplug memory. The administrator should check the compatibility of the guest OS and the hypervisor before enabling this feature. For example, Linux supports hot-unplug memory on AHV, ESXi, and XenServer, but not on Hyper-V2.
VM must be powered off to add CPU if the guest OS does not support hot-plug CPU. This is also known as cold-plug CPU. The administrator should plan for the downtime required to power off and power on the VM after adding CPU.
VM must be powered off to reduce memory if the guest OS does not support hot-unplug memory. This is also known as cold-unplug memory. The administrator should plan for the downtime required to power off and power on the VM after reducing memory. Reference: Nutanix Multicloud Automation Administration (NMCAA), page 10; Nutanix Certified Professional - Multicloud Automation (NCP-MCA), section 3; Nutanix Support Portal - Guest OS Compatibility Matrix