Microsoft AZ-104 Practice Test 47
Question 460
A stateless API should scale according to concurrent HTTP requests without tuning VM autoscale. Which Azure service setting fits?
- Create an unused container registry and expect it to autoscale an HTTP-serving workload by request volume.
- Configure HTTP ingress scaling on Azure Container Apps.
- Set Container Apps ingress to internal and assume concurrent HTTP requests automatically scale replica count.
- Deploy a container group using Azure Container Instances.
Explanation
Correct Answer
B:Container Apps supports HTTP concurrency-based scaling with managed replicas. VMSS CPU autoscale addresses a different hosting model. This matters here because a stateless API should scale according to concurrent HTTP requests without tuning VM autoscale. Which Azure service….
Incorrect Answers
A:A registry stores images; it does not serve or autoscale HTTP requests. A Container Apps HTTP scale rule addresses the stated concurrency requirement.
C:Ingress controls reachability, not the replica scale thresholds. Configure an eligible HTTP scale rule and its concurrency limit.
D:ACI runs isolated container workloads without maintaining a cluster control plane. It is suitable for simple short-duration tasks. This matters here because a stateless API should scale according to concurrent HTTP requests without tuning VM autoscale. Which Azure service….
Question 461
A security team wants all HTTP requests to an App Service site redirected to HTTPS. Which setting should be enabled?
- Upgrade to a plan that supports deployment slots without enabling HTTPS Only.
- Configure App Service access restrictions to allow approved source addresses and deny the rest.
- Validate staging content, warm-up requests, sticky settings and target routing before slot swap.
- Turn on HTTPS Only for the App Service app.
Explanation
Correct Answer
D:HTTPS Only enforces secure transport for inbound web requests. A valid certificate without enforcement does not guarantee every user avoids HTTP.
Incorrect Answers
A:A higher hosting tier does not automatically redirect HTTP traffic to HTTPS. Enable the site's HTTPS Only control to meet this transport security requirement.
B:Access restrictions evaluate inbound request sources at the App Service boundary. TLS certificates protect transport, not source eligibility. This matters here because a security team wants all HTTP requests to an App Service site redirected to HTTPS. Which setting should be enabled.
C:A slot swap changes production-visible content under specified configuration rules. Testing prevents silent database or routing mismatches. This matters here because a security team wants all HTTP requests to an App Service site redirected to HTTPS. Which setting should be enabled.
Question 462
An app accepts TLS 1.0 connections though HTTPS Only is enabled. What separate control is required?
- Verify the custom domain's DNS records and bind the hostname to the App Service app.
- Configure private inbound access or appropriate App Service access restrictions separately.
- Verify App Service OS, language stack and runtime version compatibility.
- Increase the App Service minimum inbound TLS version to the approved level.
Explanation
Correct Answer
D:HTTPS Only requires encrypted transport but does not, by itself, set the minimum accepted TLS protocol version. This matters here because an app accepts TLS 1.0 connections though HTTPS Only is enabled. What separate control is required.
Incorrect Answers
A:DNS and App Service hostname mapping work together. A DNS record alone does not authorize the platform to serve the hostname. This matters here because an app accepts TLS 1.0 connections though HTTPS Only is enabled. What separate control is required.
B:Outbound VNet integration does not inherently make an App Service web endpoint private. Inbound restrictions are a different feature. This matters here because an app accepts TLS 1.0 connections though HTTPS Only is enabled. What separate control is required.
C:App Service offerings vary by operating system and runtime. A build that runs locally may need a compatible hosting configuration. This matters here because an app accepts TLS 1.0 connections though HTTPS Only is enabled. What separate control is required.
Question 463
A web app must reach a private SQL endpoint inside a VNet without changing its public ingress. Which network feature enables outbound access?
- Create and approve an App Service private endpoint for inbound client traffic.
- Configure App Service regional VNet integration with a supported delegated subnet.
- Tune threshold separation, aggregation windows and cooldown to prevent oscillation.
- Create an Azure App Service web app using a supported Python runtime.
Explanation
Correct Answer
B:VNet integration routes supported App Service outbound traffic into the VNet. It does not expose the app itself through a private IP.
Incorrect Answers
A:Private endpoints provide private network ingress to supported App Service apps. Regional VNet integration is for outbound app calls. This matters here because a web app must reach a private SQL endpoint inside a VNet without changing its public ingress. Which network feature….
C:Scale-in and scale-out should not react to the same short-lived noise. Cooldowns and hysteresis reduce resource churn. This matters here because a web app must reach a private SQL endpoint inside a VNet without changing its public ingress. Which network feature….
D:App Service manages supported application hosting and scaling features. A VM-hosted web server adds guest patching responsibilities. This matters here because a web app must reach a private SQL endpoint inside a VNet without changing its public ingress. Which network feature….
Question 464
A team uses App Service VNet integration and assumes Internet clients cannot reach the app. What additional control is needed?
- Configure App Service Health Check with an accurate application readiness path.
- Increase the App Service minimum inbound TLS version to the approved level.
- Configure private inbound access or appropriate App Service access restrictions separately.
- Create and approve an App Service private endpoint for inbound client traffic.
Explanation
Correct Answer
C:Outbound VNet integration does not inherently make an App Service web endpoint private. Inbound restrictions are a different feature. This matters here because a team uses App Service VNet integration and assumes Internet clients cannot reach the app. What additional control….
Incorrect Answers
A:Health Check probes a configured endpoint and can mark unhealthy worker instances for exclusion in supported plans.
B:HTTPS Only requires encrypted transport but does not, by itself, set the minimum accepted TLS protocol version. This matters here because a team uses App Service VNet integration and assumes Internet clients cannot reach the app. What additional control….
D:Private endpoints provide private network ingress to supported App Service apps. Regional VNet integration is for outbound app calls. This matters here because a team uses App Service VNet integration and assumes Internet clients cannot reach the app. What additional control….
Question 465
Employees need to reach an App Service site by private IP without exposing it through the ordinary public ingress. Which resource helps?
- Set up custom App Service backup over a storage account and assume it creates private inbound client connectivity.
- Create and approve an App Service private endpoint for inbound client traffic.
- Configure private inbound access or appropriate App Service access restrictions separately.
- Configure App Service regional VNet integration with a supported delegated subnet.
Explanation
Correct Answer
B:Private endpoints provide private network ingress to supported App Service apps. Regional VNet integration is for outbound app calls. This matters here because employees need to reach an App Service site by private IP without exposing it through the ordinary public ingress.….
Incorrect Answers
A:Backup destination networking controls where backup data can travel, not the site's public or private ingress. Configure an App Service private endpoint and DNS where supported.
C:Outbound VNet integration does not inherently make an App Service web endpoint private. Inbound restrictions are a different feature. This matters here because employees need to reach an App Service site by private IP without exposing it through the ordinary public ingress.….
D:VNet integration routes supported App Service outbound traffic into the VNet. It does not expose the app itself through a private IP. This matters here because employees need to reach an App Service site by private IP without exposing it through the ordinary public ingress.….
Question 466
A private endpoint is connected but employee DNS resolves the app hostname publicly. What should be configured?
- Configure App Service Health Check with an accurate application readiness path.
- Verify the custom domain's DNS records and bind the hostname to the App Service app.
- Bind a valid TLS certificate to the custom hostname using a supported App Service method.
- Link the appropriate privatelink.azurewebsites.net private DNS records to client VNets.
Explanation
Correct Answer
D:Private routing requires the standard hostname to resolve to the private endpoint address. Endpoint connection without DNS integration is insufficient. This matters here because a private endpoint is connected but employee DNS resolves the app hostname publicly.
Incorrect Answers
A:Health Check probes a configured endpoint and can mark unhealthy worker instances for exclusion in supported plans. This matters here because a private endpoint is connected but employee DNS resolves the app hostname publicly.
B:DNS and App Service hostname mapping work together. A DNS record alone does not authorize the platform to serve the hostname. This matters here because a private endpoint is connected but employee DNS resolves the app hostname publicly.
C:TLS bindings present the domain's certificate to clients and authenticate the endpoint. HTTPS-only settings alone cannot supply a trusted certificate. This matters here because a private endpoint is connected but employee DNS resolves the app hostname publicly.
Question 467
A workload needs outbound Internet without assigning a public IP to each VM. Which Azure networking service can supply scalable SNAT?
- Attach an Azure NAT Gateway to the workload subnet for supported outbound connectivity.
- Verify effective default routes and an explicit supported outbound Internet method.
- Enable IP forwarding on every workload NIC and assume those VMs obtain Internet SNAT automatically.
- Associate a Standard SKU static public IP address with the supported endpoint.
Explanation
Correct Answer
A:NAT Gateway provides outbound SNAT using allocated public addresses while VMs remain privately addressed. This matters here because a workload needs outbound Internet without assigning a public IP to each VM. Which Azure networking service can….
Incorrect Answers
B:Removing a public IP can eliminate an implicit egress path. VNet connectivity alone does not guarantee outbound Internet reachability. This matters here because a workload needs outbound Internet without assigning a public IP to each VM. Which Azure networking service can….
C:Packet forwarding makes a VM eligible to relay transit traffic but does not translate private source addresses to a shared public egress IP. A NAT Gateway associated with the subnet supplies managed outbound SNAT for eligible flows.
D:A static Standard public IP can provide an allocated endpoint address under supported attachment and availability constraints. This matters here because a workload needs outbound Internet without assigning a public IP to each VM. Which Azure networking service can….
Question 468
Several VMs without public IPs have intermittent outbound exhaustion during high connection counts. What should be inspected?
- Use nonoverlapping VNet address prefixes and check peering conflicts.
- Review the source NIC's effective routes and the matching user-defined route.
- Use Azure Bastion over the VNet private address for supported VM management.
- Review NAT Gateway SNAT port capacity, assigned public IPs and connection patterns.
Explanation
Correct Answer
D:NAT Gateway capacity is finite and depends on allocated IP resources. Excessive concurrent connections can exhaust port availability.
Incorrect Answers
A:A VNet cannot contain conflicting address spaces in ways that undermine subnet allocation and routing. Peering also requires unique address planning. This matters here because several VMs without public IPs have intermittent outbound exhaustion during high connection counts.
B:Effective routes show which prefix and next hop govern a destination. A VM's subnet attachment does not reveal overrides by itself. This matters here because several VMs without public IPs have intermittent outbound exhaustion during high connection counts.
C:Bastion brokers approved RDP or SSH connections to VMs without public IPs on each guest.
Question 469
A company needs a private VM to contact an external update repository through a controlled outbound egress path. Which design fits?
- Set the NIC IP configuration's private IP allocation method to Static with an available subnet address.
- Use Azure DNS Private Resolver with an outbound endpoint and forwarding rule set.
- Configure supported hub routing through an NVA or gateway with allow-forwarded-traffic and UDRs as appropriate.
- Provide a subnet NAT Gateway or another approved outbound path with suitable NSG rules.
Explanation
Correct Answer
D:A private VM can reach public services through a managed outbound translation path without a directly attached public IP.
Incorrect Answers
A:Static private IP allocation makes the address stable across supported VM lifecycle events. DNS records must agree with the NIC configuration. This matters here because a company needs a private VM to contact an external update repository through a controlled outbound egress path.….
B:Private Resolver can forward selected domain queries to reachable DNS servers without self-managed DNS VMs.
C:Spoke-to-hub peering does not automatically create spoke-to-spoke transitive routing. A routing service or topology change is needed. This matters here because a company needs a private VM to contact an external update repository through a controlled outbound egress path.….
Question 470
A VM can reach peers but cannot download OS updates after public IP removal. What should be checked?
- Bind the application listener and guest network interface to the secondary private IP as required.
- Inspect hub Allow gateway transit and spoke Use remote gateways settings plus effective routes.
- Verify effective default routes and an explicit supported outbound Internet method.
- Attach an Azure NAT Gateway to the workload subnet for supported outbound connectivity.
Explanation
Correct Answer
C:Removing a public IP can eliminate an implicit egress path. VNet connectivity alone does not guarantee outbound Internet reachability. This matters here because a VM can reach peers but cannot download OS updates after public IP removal.
Incorrect Answers
A:Azure IP configuration and guest OS listener binding are separate. The guest must accept traffic for the assigned address. This matters here because a VM can reach peers but cannot download OS updates after public IP removal.
B:A spoke must opt into supported remote gateway use. Gateway advertisements and route tables also determine reachability. This matters here because a VM can reach peers but cannot download OS updates after public IP removal.
D:NAT Gateway provides outbound SNAT using allocated public addresses while VMs remain privately addressed. This matters here because a VM can reach peers but cannot download OS updates after public IP removal.