Skip to main content
  1. Public practice questions
  2. AZ-104 Practice Exams | Azure Administrator Associate
  3. AZ-104 Case Study Set

Question 18 — AZ-104 Case Study Set

Given that the production deployment already returns the storage account name and runtime endpoint, which change would most directly reduce unnecessary discovery operations in Paideffort's pipeline? (Select one answer)

  1. Capture the ARM deployment outputs and pass those values directly to later application configuration stages.

  2. Run additional Azure CLI list and show commands after every deployment to rediscover the same resource properties.

  3. Store the storage account name permanently in the workflow and stop returning it from the ARM deployment.

  4. Replace the runtime endpoint output with a hardcoded endpoint assembled from the expected storage account name.

Correct answers

  1. Capture the ARM deployment outputs and pass those values directly to later application configuration stages.

Explanations

Correct Answer:

Capture the ARM deployment outputs and pass those values directly to later application configuration stages.

Explanation:

Paideffort's ARM template already returns both storageAccountName and storageEndpoint. Consuming these outputs avoids redundant resource discovery commands and gives downstream automation values associated directly with the completed deployment.

Wrong Answers:

Run additional Azure CLI list and show commands after every deployment to rediscover the same resource properties.

This is the current inefficient behavior. Paideffort already has the necessary information available through deployment outputs.

Store the storage account name permanently in the workflow and stop returning it from the ARM deployment.

The account name is generated from the environment and resource-group context. Hardcoding it separately would duplicate configuration and weaken deployment traceability.

Replace the runtime endpoint output with a hardcoded endpoint assembled from the expected storage account name.

The scenario requires runtime information from the deployed resource. Returning the actual endpoint is more reliable than reconstructing a property outside the deployment.