Microsoft AZ-104 Exam Dumps, Practice Test Questions

The decorator controls the number of instances that may deploy in the same batch, not the total iteration count. A batch size of eight permits all eight requested resources to start together, preserving the provider collision risk. For a provider requiring serial operations, the appropriate batch size is one.

Unique resource names prevent name conflicts but do not change concurrent scheduling of operations that the provider serializes internally. The scenario explicitly says the provider rejects parallel operations for its logical service, so merely renaming the eight deployments leaves the temporal collision unresolved. Control loop concurrency rather than only resource identifiers.

Incremental and Complete deployment modes concern how resources not in a template are handled, not whether items inside a Bicep loop execute in sequence. Using Complete mode can create deletion risk for unspecified resources and is not a provider-concurrency control. The desired behavior comes from the loop batching decorator.

Repeating names can create a malformed type/name path. Bicep has a direct parent relationship so guessing string segments is unnecessary.

Dependency ordering cannot repair an invalid child resource identifier. A parent symbolic reference and the relative child name avoid doubling the parent's name.

A correct nested type is insufficient when the child identifier repeats the parent name in a relative-name declaration. Use the parent property with a proper relative child name.

A resource group is not a VM child extension and cannot be provisioned by falsely nesting it under an existing group deployment.

The existing keyword references a resource assumed to be present; it does not create the new group. Because a new resource group is a subscription-scoped resource, the root needs the matching subscription target scope before a child module can deploy into it.

Pointing the command at a different pre-existing resource group does not change the file's ability to declare a new group resource. The compilation and scope mismatch remains; a subscription-scoped root and a module scoped to the newly created group are required.

Outputs expose values after a deployment but do not themselves enforce creation order. Returning the VM name cannot ensure that its network interface was available first.

A parameter can supply a resource name, but does not on its own express an ARM deployment dependency. The VM could still be scheduled before the NIC is provisioned.

Conditional deployment determines whether resources exist in the template, not their required creation order. The dependency must be represented in ARM deployment semantics.

Resource dependency references establish deployment order, not a request to delete the referenced storage account.

The reference establishes ordering requirements rather than enforcing concurrent deployment. A dependent resource must wait for the referenced resource when required.

Template dependency ordering does not grant resource-provider permissions. The deployment identity still needs appropriate Azure RBAC rights.

Budgets monitor costs and cannot supply resource names, SKUs, or regions to an ARM deployment.

Provider namespaces identify Azure service types and cannot be arbitrarily changed to express environment values. This would make deployments invalid.

Repeated template edits introduce configuration drift and risk accidental cross-environment values. Parameterizing was meant to avoid that fragility.

Duplicate resource declarations with the same name/type do not create five uniquely named accounts; they are a template-maintenance error.

dependsOn controls ordering of resource operations, not the number of resource instances or their distinct names.

An ARM resource condition decides whether to deploy the one declaration; it does not iterate and emit five independent resources.

Complete mode may remove resources not represented in the template, putting the third unrelated account at risk rather than preserving it.

Complete-mode semantics can delete applicable resources omitted from the template, which is the risk the operator wants to avoid.

What-if may warn about predicted deletion but does not change complete-mode semantics. Deploying anyway would still endanger the omitted resource.

An ordinary string output is visible in deployment output material. A description is human-readable metadata, not a confidentiality mechanism, so the generated credential would still violate the stated history and logging restriction.

Changing the type to int both corrupts the credential representation and does not constitute secure output handling. Bicep secure outputs are deliberately constrained to string and object; other data must be wrapped or serialized appropriately.

A secure input parameter protects the value while supplied to the deployment but does not automatically mark an ordinary generated output as sensitive. The requirement explicitly rules out output visibility in CLI and deployment history; the output itself must be declared @secure() with a protected downstream handling path.

Hardcoding names can drift when the deployment uses parameters or generated identifiers. It also fails to capture the actual resource ID returned by ARM.

A tag can hold arbitrary metadata but is not a guaranteed structured output containing the created resource’s ARM ID. The workflow needs an explicit deployment output.

DependsOn changes deployment ordering rather than returning a value for downstream consumption. It cannot replace an output declaration.

Parallel hardcoded execution risks using an incorrect or unavailable resource ID. It discards the dependency information already exposed by the module output.

Declaration order alone does not establish a resource dependency in Bicep. Passing the subnet module's output to the VM module creates the actual data dependency and deployment order.

The existing keyword addresses an already-deployed resource; it does not communicate a newly created module output to another module or automatically infer a missing NIC subnet ID.