Question 4 of 10Implement and Manage Storage
CramHQ stores research clips and internal lab notes in separate containers within one storage account. A partner portal must let browsers fetch selected clip URLs without sign-in or per-request tokens, but users must not list the clip set or read lab notes. Which configuration best meets the requirement?
- AA. Set Allow Blob anonymous access to Enabled on the storage account; set the clip container's anonymous access level to Container; keep the notes container Private.
- BB. Set Allow Blob anonymous access to Enabled on the storage account; set both containers' anonymous access level to Blob; move the notes blobs to Archive.
- CC. Set Allow Blob anonymous access to Disabled on the storage account; set the clip container's anonymous access level to Blob; keep the notes container Private.
- DD. Set Allow Blob anonymous access to Enabled on the storage account; set the clip container's anonymous access level to Blob; keep the notes container Private.
Show answer and explanation
Answer: D
This uses the account setting as the prerequisite and exposes only direct reads of blobs in the clip container. The Blob level does not allow anonymous listing of the container, and the notes container remains authorized-only.
If you picked AWhy it is tempting: Container access sounds related because it lets unauthenticated users reach blobs in the clip container.
Why it is wrong: Use Blob public access when anonymous users need direct blob reads but must not list the container contents.
If you picked BWhy it is tempting: Both containers use the narrower Blob level, so the choice can look controlled at first glance.
Why it is wrong: Apply anonymous access only to the container that must be public, and keep unrelated protected containers private.
If you picked CWhy it is tempting: The clip container is set to the correct Blob level and the notes container stays private, so the lower-scope settings look right.
Why it is wrong: The storage account must allow anonymous blob access before any container-level anonymous access setting can take effect.
Question 5 of 10Deploy and Manage Azure Compute Resources
CramHQ deploys the same inference platform baseline into resource groups across several subscriptions. Each run changes region, naming prefixes, and capacity limits, and engineers have been editing the template before promotion, causing drift. Which recommendation best supports consistent promotion while allowing those per-environment differences?
- AA. Use one Bicep file, provide environment-specific .bicepparam files, and run the deployment from the tenant root so every subscription is reachable.
- BB. Use one Bicep file, provide environment-specific .bicepparam files, and run the deployment at the resource group that each environment owns.
- CC. Use one Bicep file, derive environment values from resource group tags during deployment, and run the deployment at the resource group that each environment owns.
- DD. Create one Bicep file per environment, store the environment values as variables, and run each deployment at the resource group that each environment owns.
Show answer and explanation
Answer: B
This keeps the declarative artifact unchanged while supplying approved values per environment. Starting the operation at the owning resource group matches the target resources and avoids creating template copies for promotion.
If you picked AWhy it is tempting: The tenant root sounds useful when several subscriptions are involved, and the parameter-file part is correct.
Why it is wrong: Choose the deployment scope based on where the target resources are created or updated, not on the broadest place that can see subscriptions.
If you picked CWhy it is tempting: Tags are already associated with the environment, so deriving values from them can seem centralized and convenient.
Why it is wrong: Deployment runs should use the intended template or Bicep artifact with explicit reviewed inputs, such as parameter files or supplied parameter values.
If you picked DWhy it is tempting: Separate files can look easy to review because each environment has its own artifact.
Why it is wrong: Use parameters for values that vary between environments; reserve template or Bicep changes for actual differences in resource structure or logic.
Question 6 of 10Deploy and Manage Azure Compute Resources
CramHQ exports an ARM template for a production resource group and shortens one existing resource block before adding a setting required by new inference workers. The deployment must change only the intended settings while leaving current nondefault configuration and unrelated resources in the group intact. What should you recommend?
- AA. Leave only the changed properties in the existing ARM template resource, deploy to the resource group in incremental mode, and verify with Azure Resource Manager what-if.
- BB. Keep the shortened ARM template resource, add explicit dependsOn entries for related resources, deploy in incremental mode, and verify with Azure Resource Manager what-if.
- CC. Keep the existing resource as a full ARM template declaration, add the needed property, preserve current nondefault settings, and deploy to the resource group in incremental mode after Azure Resource Manager what-if.
- DD. Keep the shortened ARM template resource, add the needed property, deploy to the resource group in complete mode, and verify with Azure Resource Manager what-if.
Show answer and explanation
Answer: C
This matches documented behavior: incremental mode leaves unrelated group resources unchanged, while included resources are reapplied from the template. Keeping the full declaration avoids resetting omitted nondefault properties.
If you picked AWhy it is tempting: Incremental mode does leave resources that are not in the template unchanged, so it can sound like a narrow update mode.
Why it is wrong: For a resource included in the template, the declaration is reapplied as the desired final shape; preserve needed nondefault properties in the template.
If you picked BWhy it is tempting: dependsOn is a real ARM template control, and adding explicit dependencies can look like a safer deployment structure.
Why it is wrong: dependsOn controls creation or update order; it does not change how omitted properties in a declared resource are handled.
If you picked DWhy it is tempting: Complete mode sounds rigorous because it reconciles the resource group against the template.
Why it is wrong: Use complete mode only when resources absent from the resolved template are intended to be removed from the deployment scope.
Question 7 of 10Implement and Manage Virtual Networking
CramHQ has a lab subnet with one network security group. An existing inbound custom rule at 200 denies TCP 1433 from VirtualNetwork to DB-ASG. Simulator VMs are in SIM-ASG, and database VMs are in DB-ASG. Only simulator VMs must reach the databases on 1433, while the broad block must still apply to all other VMs. Which change should you make?
- AA. Add an outbound network security group rule: source SIM-ASG, destination DB-ASG, TCP 1433, Allow, priority 100.
- BB. Add an inbound network security group rule: source SIM-ASG, destination DB-ASG, TCP 1433, Allow, priority 100.
- CC. Associate a new network security group to the database NICs with inbound source SIM-ASG, destination DB-ASG, TCP 1433, Allow, priority 100.
- DD. Add an inbound network security group rule: source SIM-ASG, destination DB-ASG, TCP 1433, Allow, priority 300.
Show answer and explanation
Answer: B
This creates a narrow allowance that is evaluated before the existing deny rule. The simulator-to-database packets match the allow first, while other VirtualNetwork sources still match the deny at 200.
If you picked AWhy it is tempting: The rule uses the right ASGs, port, action, and priority, so it looks like a targeted exception.
Why it is wrong: Match the NSG rule direction to the blocking rule and the evaluated traffic path. An inbound destination-side deny needs an inbound exception that is evaluated before it.
If you picked CWhy it is tempting: The rule itself has the right source, destination, port, action, and priority, so the attachment point can be easy to overlook.
Why it is wrong: When both subnet and NIC NSGs apply, the traffic must be allowed by the applicable rules at each point; a deny at one point still blocks the flow.
If you picked DWhy it is tempting: The rule has the right inbound direction and the correct SIM-ASG-to-DB-ASG targeting.
Why it is wrong: For matching NSG rules, lower numeric priority values are evaluated first, and processing stops at the first match.
Question 8 of 10Implement and Manage Virtual Networking
A hub virtual network in each Azure region already connects to CramHQ datacenters. A new plant workload virtual network in the same region must reach datacenter IP ranges and hub-hosted shared services over private addresses. Network engineers want the plant network to consume the existing regional path instead of deploying another virtual network gateway. Which peering configuration should you recommend?
- AA. On the hub-to-plant peering, enable Allow gateway transit; on the plant-to-hub peering, enable Use remote gateways.
- BB. On the hub-to-plant peering, enable Allow gateway transit; on the plant-to-hub peering, enable Allow forwarded traffic.
- CC. On the hub-to-plant peering, enable Allow forwarded traffic; on the plant-to-hub peering, enable Use remote gateways.
- DD. On the plant-to-hub peering, enable Allow gateway transit; on the hub-to-plant peering, enable Use remote gateways.
Show answer and explanation
Answer: A
This assigns the existing hub path to be usable by the peer and configures the plant network to consume that remote path. The plant can also reach hub-hosted private services over the peering.
If you picked BWhy it is tempting: The hub-side gateway transit setting is correct, and forwarded traffic sounds related to routing across networks.
Why it is wrong: Use remote gateways is the plant-side setting that lets the plant VNet consume the hub gateway; Allow forwarded traffic is a separate peering control.
If you picked CWhy it is tempting: Use remote gateways is required on the plant-to-hub peering, so the answer contains one important correct setting.
Why it is wrong: The gateway-owning VNet must allow gateway transit before another peered VNet can use that gateway.
If you picked DWhy it is tempting: The answer contains the two gateway-related settings, but places them on the wrong peering directions.
Why it is wrong: The VNet with the existing gateway allows gateway transit; the VNet without the gateway uses remote gateways.
Question 9 of 10Monitor and Maintain Azure Resources
A studio operations team discovers that an automated cleanup job corrupted a large data volume on a backed-up Azure VM that still runs correctly. Since the last clean backup, engineers applied OS and service hotfixes that must remain. The team must validate the recovered data before changing production. What should you recommend?
- AA. Use Replace existing disk from the last clean recovery point on the current VM, boot it, and validate the application data in place.
- BB. Restore the VM from the last clean recovery point as a new VM in the production subnet, validate it, and redirect users to the new VM.
- CC. Use File Recovery from the last clean recovery point, mount the recovery point on the VM, and copy the affected folders into production.
- DD. Restore disks from the last clean recovery point to a staging resource group, attach the restored data disk to a test VM, and promote the validated data.
Show answer and explanation
Answer: D
Restoring disks from the selected point creates recoverable disk artifacts without replacing the running VM. The affected data can be mounted and checked first, while current OS and service changes remain intact.
If you picked AWhy it is tempting: Replacing existing disks sounds direct because it uses the last clean recovery point on the affected VM.
Why it is wrong: Use replacement only when rolling back the VM disk state is acceptable. If production must remain unchanged until validation, restore recoverable data separately.
If you picked BWhy it is tempting: A new VM can be validated separately, so it appears to satisfy the testing requirement.
Why it is wrong: Use a full VM restore when the machine state needs recovery. For a healthy VM with damaged data, restore only the needed disk data and validate it separately.
If you picked CWhy it is tempting: File Recovery is useful when only a few known files or folders must be copied back.
Why it is wrong: Use file-level recovery for selective file or folder restore. Use disk-level restore when the damaged boundary is a disk or large volume that should be mounted and validated outside production.
Question 10 of 10Monitor and Maintain Azure Resources
CramHQ protects a Windows Server VM with Azure Site Recovery. During a scheduled drill, the team wants the newest replica state that can be started immediately in Azure; the test window cannot wait for Azure to incorporate any remaining replicated changes. Application quiescence is not the validation goal. Which recovery point choice should the administrator select?
- AA. Run the Azure Site Recovery test failover and select Latest processed as the recovery point.
- BB. Run the Azure Site Recovery test failover and select Latest (lowest RPO) as the recovery point.
- CC. Run the Azure Site Recovery test failover and select Custom, then choose the newest timestamp shown in the retention window.
- DD. Run the Azure Site Recovery test failover and select Latest app-consistent as the recovery point.
Show answer and explanation
Answer: A
Latest processed uses the newest recovery point that Azure Site Recovery has already prepared. Microsoft documents it as a low-RTO choice because no time is spent processing unprocessed data before failover.
If you picked BWhy it is tempting: Latest (lowest RPO) sounds like the freshest and safest option when a scenario asks for the newest replica state.
Why it is wrong: Choose the lowest-RPO recovery point only when the scenario can tolerate the time needed to process all replicated data first.
If you picked CWhy it is tempting: A custom timestamp can feel precise and controlled, especially when the stem emphasizes newest state.
Why it is wrong: Use a custom recovery point when a specific point in time is required, not when the goal is the newest processed point with minimal delay.
If you picked DWhy it is tempting: Application-consistent recovery sounds safer because it reflects a cleaner application state.
Why it is wrong: Choose an application-consistent recovery point when application quiescence or application-level consistency is the stated goal.