You save $69.98
An Azure administrator describes a solution for: route a controlled percentage of inbound traffic to the newly deployed revision. What remaining limitation must not be misrepresented?
Traffic weighting is approximate over samples and does not substitute for readiness and integration checks. That remains a practical service boundary even after the recommended change (configure multiple active revisions and explicit traffic weights for the Container App) is implemented; retest it when identities, policies, service capacity or network paths change.
The incident (all requests shift to the new revision despite a planned small canary rollout) could recur if a related Azure dependency changes. The design still faces the limitation: Traffic weighting is approximate over samples and does not substitute for readiness and integration checks.
The successful check 'Send representative requests and inspect routing distribution by revision' proves only the tested behavior and cannot eliminate every dependent failure. The specific remaining limitation is: Traffic weighting is approximate over samples and does not substitute for readiness and integration checks.
The two checks cover separate behavior: 'Send representative requests and inspect routing distribution by revision' and 'Shift weights back to the stable revision and confirm the rollback path'. Neither check removes the remaining operational limitation: Traffic weighting is approximate over samples and does not substitute for readiness and integration checks.
A production subscription has this use case: A .NET web application requires a managed App Service host with Linux runtime, regional placement and appropriate pricing. The owner specifies: select an App Service plan that defines the compute SKU and operating system for the hosted web app. What is the best administrative approach?
The plan determines hosting resources and OS characteristics for its apps, independent of a mere app name. This achieves select an App Service plan that defines the compute SKU and operating system for the hosted web app through create a compatible Linux App Service plan in the intended region and deploy the web app to that plan instead of relying on merely similar resource settings.
Reader cannot provision a web app or App Service plan; that would not meet select an App Service plan that defines the compute SKU and operating system for the hosted web app, for which the relevant Azure action is create a compatible Linux App Service plan in the intended region and deploy the web app to that plan.
An incompatible OS plan cannot host the intended Linux runtime; that would not meet select an App Service plan that defines the compute SKU and operating system for the hosted web app, for which the relevant Azure action is create a compatible Linux App Service plan in the intended region and deploy the web app to that plan.
Blob lifecycle settings do not determine App Service hosting SKU; that would not meet select an App Service plan that defines the compute SKU and operating system for the hosted web app, for which the relevant Azure action is create a compatible Linux App Service plan in the intended region and deploy the web app to that plan.
An Azure administrator is investigating this symptom: The web app deployment rejects its target because the plan's OS type differs from the runtime requirement. Which root cause best matches the underlying requirement: select an App Service plan that defines the compute SKU and operating system for the hosted web app?
The trace reports: The web app deployment rejects its target because the plan's OS type differs from the runtime requirement. The causal misconfiguration is: The selected App Service plan is not compatible with the application's operating system or runtime. The targeted action is to select or create a plan with the required OS, region and pricing tier before publishing.
The external DNS record or App Service custom-domain binding is missing or incorrect; that mechanism would be more consistent with an observation such as the default Azure hostname works but the custom domain shows host-not-found or an unrecognized-host response, rather than this case's the web app deployment rejects its target because the plan's OS type differs from the runtime requirement.
The TLS binding or certificate subject/SAN does not cover the configured hostname. That mechanism would be more consistent with an observation such as the web app resolves under the custom domain but browsers warn that the certificate does not match the name, rather than this case's the web app deployment rejects its target because the plan's OS type differs from the runtime requirement.
Autoscale is disabled, mis-scoped or capped at one instance under the plan; that mechanism would be more consistent with an observation such as hTTP latency rises while the app remains at one instance despite steady demand above the chosen threshold, rather than this case's the web app deployment rejects its target because the plan's OS type differs from the runtime requirement.
An Azure rollout fails because: The web app deployment rejects its target because the plan's OS type differs from the runtime requirement. Which change most directly restores the intended control?
Select or create a plan with the required OS, region and pricing tier before publishing. This addresses the documented failure condition: the selected App Service plan is not compatible with the application's operating system or runtime. Retest the affected operation and retain the original least-privilege boundaries.
An incompatible OS plan cannot host the intended Linux runtime. In the reported incident (the web app deployment rejects its target because the plan's OS type differs from the runtime requirement), that change would not correct the cause: the selected App Service plan is not compatible with the application's operating system or runtime.
Blob lifecycle settings do not determine App Service hosting SKU. In the reported incident (the web app deployment rejects its target because the plan's OS type differs from the runtime requirement), that change would not correct the cause: the selected App Service plan is not compatible with the application's operating system or runtime.
Reader cannot provision a web app or App Service plan. In the reported incident (the web app deployment rejects its target because the plan's OS type differs from the runtime requirement), that change would not correct the cause: the selected App Service plan is not compatible with the application's operating system or runtime.
For the configuration goal, select an App Service plan that defines the compute SKU and operating system for the hosted web app. The Azure context is: A .NET web application requires a managed App Service host with Linux runtime, regional placement and appropriate pricing. Which TWO observations provide useful assurance? Select TWO answers.
Verify the live app endpoint responds and reports expected runtime configuration. This supplies observed evidence for select an App Service plan that defines the compute SKU and operating system for the hosted web app. It is not interchangeable with the second required check, check the plan OS and hosting SKU and deploy a basic Linux test app, because that checks a separate success or failure boundary.
Check the plan OS and hosting SKU and deploy a basic Linux test app. This supplies observed evidence for select an App Service plan that defines the compute SKU and operating system for the hosted web app. It is not interchangeable with the second required check, verify the live app endpoint responds and reports expected runtime configuration, because that checks a separate success or failure boundary.
A configured resource is not proof of live behavior. The relevant result must be observed by verifying the live app endpoint responds and reports expected runtime configuration on the affected Azure deployment.
A privileged administrator in a different subscription may succeed at 'Verify the live app endpoint responds and reports expected runtime configuration' even though the intended caller fails. This does not prove the required behavior for verify the live app endpoint responds and reports expected runtime configuration.
A release checklist recording 'Check the plan OS and hosting SKU and deploy a basic Linux test app' is not evidence that the required operation actually succeeded or failed. To establish the correct result, the team must check the plan OS and hosting SKU and deploy a basic Linux test app on the actual workload to prove its independent boundary.
A stakeholder asks whether the proposed configuration guarantees: select an App Service plan that defines the compute SKU and operating system for the hosted web app. What qualification is technically accurate?
An App Service plan controls hosting capacity but does not automatically grant all required network, storage or database permissions. That remains a practical service boundary even after the recommended change (create a compatible Linux App Service plan in the intended region and deploy the web app to that plan) is implemented; retest it when identities, policies, service capacity or network paths change.
The successful check 'Verify the live app endpoint responds and reports expected runtime configuration' proves only the tested behavior and cannot eliminate every dependent failure. The specific remaining limitation is: An App Service plan controls hosting capacity but does not automatically grant all required network, storage or database permissions.
The two checks cover separate behavior: 'Verify the live app endpoint responds and reports expected runtime configuration' and 'Check the plan OS and hosting SKU and deploy a basic Linux test app'. Neither check removes the remaining operational limitation: An App Service plan controls hosting capacity but does not automatically grant all required network, storage or database permissions.
The incident (the web app deployment rejects its target because the plan's OS type differs from the runtime requirement) could recur if a related Azure dependency changes. The design still faces the limitation: An App Service plan controls hosting capacity but does not automatically grant all required network, storage or database permissions.
An Azure administrator must resolve a specific request: A business website must answer at portal.example.com instead of the default azurewebsites.net address. The expected outcome is: bind a controlled custom hostname and prove the domain points to the correct App Service. Which option is appropriate?
A DNS mapping plus a verified hostname binding makes the app respond under the controlled domain. This achieves bind a controlled custom hostname and prove the domain points to the correct App Service through create the appropriate DNS record, verify domain ownership when required, and add the custom domain binding to App Service instead of relying on merely similar resource settings.
Governance exemptions do not create hostname records; that would not meet bind a controlled custom hostname and prove the domain points to the correct App Service, for which the relevant Azure action is create the appropriate DNS record, verify domain ownership when required, and add the custom domain binding to App Service.
Disk snapshots do not configure App Service custom domains; that would not meet bind a controlled custom hostname and prove the domain points to the correct App Service, for which the relevant Azure action is create the appropriate DNS record, verify domain ownership when required, and add the custom domain binding to App Service.
A resource name alone is not an external DNS record; that would not meet bind a controlled custom hostname and prove the domain points to the correct App Service, for which the relevant Azure action is create the appropriate DNS record, verify domain ownership when required, and add the custom domain binding to App Service.
Operations sees an unexpected outcome: The default Azure hostname works but the custom domain shows host-not-found or an unrecognized-host response. The original demand was: bind a controlled custom hostname and prove the domain points to the correct App Service. Which cause is most consistent with the evidence?
The trace reports: The default Azure hostname works but the custom domain shows host-not-found or an unrecognized-host response. The causal misconfiguration is: The external DNS record or App Service custom-domain binding is missing or incorrect. The targeted action is to correct the DNS mapping and complete the App Service domain binding verification.
The proposed mechanism concerns the custom hostname resolves to the intended App Service and the application accepts that host header successfully, which is not established by the observed the default Azure hostname works but the custom domain shows host-not-found or an unrecognized-host response. Test the more directly supported condition: The external DNS record or App Service custom-domain binding is missing or incorrect.
Autoscale is disabled, mis-scoped or capped at one instance under the plan; that mechanism would be more consistent with an observation such as hTTP latency rises while the app remains at one instance despite steady demand above the chosen threshold, rather than this case's the default Azure hostname works but the custom domain shows host-not-found or an unrecognized-host response.
The selected App Service plan is not compatible with the application's operating system or runtime; that mechanism would be more consistent with an observation such as the web app deployment rejects its target because the plan's OS type differs from the runtime requirement, rather than this case's the default Azure hostname works but the custom domain shows host-not-found or an unrecognized-host response.
A service owner needs a practical fix after this failure: The default Azure hostname works but the custom domain shows host-not-found or an unrecognized-host response. What is the best remediation?
Correct the DNS mapping and complete the App Service domain binding verification. This addresses the documented failure condition: the external DNS record or App Service custom-domain binding is missing or incorrect. Retest the affected operation and retain the original least-privilege boundaries.
Governance exemptions do not create hostname records. In the reported incident (the default Azure hostname works but the custom domain shows host-not-found or an unrecognized-host response), that change would not correct the cause: the external DNS record or App Service custom-domain binding is missing or incorrect.
A resource name alone is not an external DNS record. In the reported incident (the default Azure hostname works but the custom domain shows host-not-found or an unrecognized-host response), that change would not correct the cause: the external DNS record or App Service custom-domain binding is missing or incorrect.
Disk snapshots do not configure App Service custom domains. In the reported incident (the default Azure hostname works but the custom domain shows host-not-found or an unrecognized-host response), that change would not correct the cause: the external DNS record or App Service custom-domain binding is missing or incorrect.
A deployment claims to meet: bind a controlled custom hostname and prove the domain points to the correct App Service. The environment is: A business website must answer at portal.example.com instead of the default azurewebsites.net address. Which TWO test results would substantiate that claim? Select TWO answers.
Resolve the custom hostname and inspect its expected DNS target. This supplies observed evidence for bind a controlled custom hostname and prove the domain points to the correct App Service. It is not interchangeable with the second required check, send HTTPS requests with the custom host header after adding a valid certificate, because that checks a separate success or failure boundary.
Send HTTPS requests with the custom host header after adding a valid certificate. This supplies observed evidence for bind a controlled custom hostname and prove the domain points to the correct App Service. It is not interchangeable with the second required check, resolve the custom hostname and inspect its expected DNS target, because that checks a separate success or failure boundary.
A privileged administrator in a different subscription may succeed at 'Resolve the custom hostname and inspect its expected DNS target' even though the intended caller fails. This does not prove the required behavior for resolve the custom hostname and inspect its expected dns target.
A release checklist recording 'Send HTTPS requests with the custom host header after adding a valid certificate' is not evidence that the required operation actually succeeded or failed. To establish the correct result, the team must send HTTPS requests with the custom host header after adding a valid certificate on the actual workload to prove its independent boundary.
A configured resource is not proof of live behavior. The required check must exercise resolve the custom hostname and inspect its expected DNS target on the affected Azure deployment.
An infrastructure design was selected to meet: bind a controlled custom hostname and prove the domain points to the correct App Service. What caveat remains relevant during operation?
DNS mapping and domain binding do not automatically install a trusted TLS certificate for the hostname. That remains a practical service boundary even after the recommended change (create the appropriate DNS record, verify domain ownership when required, and add the custom domain binding to App Service) is implemented; retest it when identities, policies, service capacity or network paths change.
The two checks cover separate behavior: 'Resolve the custom hostname and inspect its expected DNS target' and 'Send HTTPS requests with the custom host header after adding a valid certificate'. Neither check removes the remaining operational limitation: DNS mapping and domain binding do not automatically install a trusted TLS certificate for the hostname.
The incident (the default Azure hostname works but the custom domain shows host-not-found or an unrecognized-host response) could recur if a related Azure dependency changes. The design still faces the limitation: DNS mapping and domain binding do not automatically install a trusted TLS certificate for the hostname.
The successful check 'Resolve the custom hostname and inspect its expected DNS target' proves only the tested behavior and cannot eliminate every dependent failure. The specific remaining limitation is: DNS mapping and domain binding do not automatically install a trusted TLS certificate for the hostname.
or Guarantee your success by buying the full version which covers the full latest pool of questions. (606 Questions, Last Updated on Oct 25, 2026)
Please check your mailbox for a message from support@examlabs.com and follow the directions.
