100% Latest & Updated Microsoft AZ-801 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 530
A PaaS-migrated IIS app fails when a native Windows COM component is missing on the managed App Service environment. What change should be prioritized to restore the intended behavior?
- Identify and refactor the unsupported background-service dependency before choosing App Service.
- Inventory and replace the extension with a supported App Service dependency or select a compatible hosting model.
- Choose an appropriate supported Windows App Service runtime or refactor the application.
- Assess supported hosting alternatives or refactor the COM dependency rather than assuming arbitrary component registration.
Explanation
Correct Answer
D:Managed PaaS runtime restrictions limit installation of unmanaged server-level components. A suitable corrective action is to assess supported hosting alternatives or refactor the COM dependency rather than assuming arbitrary component registration.
Incorrect Answers
A:App Service hosts managed web applications rather than arbitrary machine-wide Windows services. However, managed PaaS runtime restrictions limit installation of unmanaged server-level components.
B:Automated assessment can miss undocumented in-process/server-level dependencies. Here, managed PaaS runtime restrictions limit installation of unmanaged server-level components.
C:Runtime and OS support vary by App Service hosting option. In this situation, managed PaaS runtime restrictions limit installation of unmanaged server-level components.
Question 531
A legacy ASP.NET Framework IIS app requires a Windows container, but the team builds a Linux image without compatible runtime support. Which supported action should be taken for this reported condition?
- Use an appropriate Windows container base image and compatible runtime for the application.
- Assess supported image capabilities and refactor or choose a compatible base image.
- Keep the Linux base image and select Hyper-V isolation, expecting the Windows-only .NET Framework and IIS services to run in the Linux guest.
- Rebuild and redeploy from a supported patched base image with dependency scanning.
Explanation
Correct Answer
A:Container OS base image and framework requirements must match the workload's platform dependencies. The targeted remedy is to use an appropriate Windows container base image and compatible runtime for the application.
Incorrect Answers
B:Windows container base images include different OS components and do not replicate every full server role. In this situation, container OS base image and framework requirements must match the workload's platform dependencies.
C:Hyper-V isolation changes a Windows container's isolation and compatibility boundary; it does not turn a Linux container into a Windows IIS/.NET Framework runtime. The application needs a supported Windows image and runtime.
D:Container base OS packages remain part of the deployment's vulnerability surface. Here, container OS base image and framework requirements must match the workload's platform dependencies.
Question 532
A containerized IIS app saves uploaded content inside its writable container layer and loses data when the image is replaced. Which response addresses the identified root cause without weakening other controls?
- Extract the scheduled work into a supported external job/worker architecture.
- Move persistent data to supported mounted or external storage before deployment.
- Use an appropriate Windows container base image and compatible runtime for the application.
- Rebuild and redeploy from a supported patched base image with dependency scanning.
Explanation
Correct Answer
B:Move persistent data to supported mounted or external storage before deployment. This addresses the condition because container lifecycle replacement can discard writable-layer changes, so state must live outside the disposable instance.
Incorrect Answers
A:Moving the HTTP endpoint to a container does not automatically migrate unrelated host scheduler tasks. In this situation, container lifecycle replacement can discard writable-layer changes, so state must live outside the disposable instance.
C:Container OS base image and framework requirements must match the workload's platform dependencies. Here, container lifecycle replacement can discard writable-layer changes, so state must live outside the disposable instance.
D:Container base OS packages remain part of the deployment's vulnerability surface. In this situation, container lifecycle replacement can discard writable-layer changes, so state must live outside the disposable instance.
Question 533
A Windows container image is built with credentials embedded in its Dockerfile ENV lines and pushed to a shared registry. What is the best targeted remediation for the behavior described?
- Use an appropriate Windows container base image and compatible runtime for the application.
- Assess supported image capabilities and refactor or choose a compatible base image.
- Remove secrets from image layers and inject scoped secrets through the target runtime.
- Validate the Windows container host and image build compatibility or use supported isolation.
Explanation
Correct Answer
C:Image history and registry access can expose embedded credentials even if containers do not print them. For that reason, remove secrets from image layers and inject scoped secrets through the target runtime.
Incorrect Answers
A:Container OS base image and framework requirements must match the workload's platform dependencies. However, image history and registry access can expose embedded credentials even if containers do not print them.
B:Windows container base images include different OS components and do not replicate every full server role. Here, image history and registry access can expose embedded credentials even if containers do not print them.
D:Windows containers have host/kernel compatibility requirements that differ from generic Linux image portability. However, image history and registry access can expose embedded credentials even if containers do not print them.
Question 534
An IIS app container exits immediately because the startup command runs configuration then terminates instead of keeping the web service active. What is the best targeted remediation for the behavior described?
- Use an appropriate Windows container base image and compatible runtime for the application.
- Validate the Windows container host and image build compatibility or use supported isolation.
- Move persistent data to supported mounted or external storage before deployment.
- Configure a valid container entrypoint that keeps the required IIS/application process running.
Explanation
Correct Answer
D:Configure a valid container entrypoint that keeps the required IIS/application process running. The underlying technical reason is that container lifetime follows its primary process; a completed configuration script stops the container.
Incorrect Answers
A:Container OS base image and framework requirements must match the workload's platform dependencies. Here, container lifetime follows its primary process; a completed configuration script stops the container.
B:Windows containers have host/kernel compatibility requirements that differ from generic Linux image portability. In this situation, container lifetime follows its primary process; a completed configuration script stops the container.
C:Container lifecycle replacement can discard writable-layer changes, so state must live outside the disposable instance. However, container lifetime follows its primary process; a completed configuration script stops the container.
Question 535
A web application container runs as an elevated identity although no privileged Windows operations are required. Which administrative change most directly resolves the documented failure?
- Use an appropriately least-privileged container identity and constrain writable filesystem areas.
- Use an appropriate Windows container base image and compatible runtime for the application.
- Configure a valid container entrypoint that keeps the required IIS/application process running.
- Validate the Windows container host and image build compatibility or use supported isolation.
Explanation
Correct Answer
A:Excessive container privileges increase impact if the application process is compromised. A suitable corrective action is to use an appropriately least-privileged container identity and constrain writable filesystem areas.
Incorrect Answers
B:Container OS base image and framework requirements must match the workload's platform dependencies. However, excessive container privileges increase impact if the application process is compromised.
C:Container lifetime follows its primary process; a completed configuration script stops the container. Here, excessive container privileges increase impact if the application process is compromised.
D:Windows containers have host/kernel compatibility requirements that differ from generic Linux image portability. In this situation, excessive container privileges increase impact if the application process is compromised.
Question 536
A team assumes a Windows Server Core container image includes the Desktop Experience GUI components needed by a legacy installer. Which supported action should be taken for this reported condition?
- Assume a Windows Server Core container image supports running the legacy Desktop Experience GUI installer without changing the image or application.
- Assess supported image capabilities and refactor or choose a compatible base image.
- Rebuild and redeploy from a supported patched base image with dependency scanning.
- Remove secrets from image layers and inject scoped secrets through the target runtime.
Explanation
Correct Answer
B:Windows container base images include different OS components and do not replicate every full server role. The targeted remedy is to assess supported image capabilities and refactor or choose a compatible base image.
Incorrect Answers
A:Windows Server Core containers omit the full Desktop Experience shell. A GUI-dependent installer is not made compatible just by invoking it in the same unsupported image.
C:Container base OS packages remain part of the deployment's vulnerability surface. In this situation, Windows container base images include different OS components and do not replicate every full server role.
D:Image history and registry access can expose embedded credentials even if containers do not print them. However, Windows container base images include different OS components and do not replicate every full server role.
Question 537
An IIS Windows container build passes locally but cannot start on a target host due to unsupported host/image version combinations. Which configuration or recovery action best matches this evidence?
- Rebuild on the newest available Windows Server 2025 base image while retaining process isolation on the Windows Server 2022 host.
- Change IIS application pool settings while leaving the unsupported Windows container host and image build combination unchanged.
- Validate the Windows container host and image build compatibility or use supported isolation.
- Remove secrets from image layers and inject scoped secrets through the target runtime.
Explanation
Correct Answer
C:Validate the Windows container host and image build compatibility or use supported isolation. This addresses the condition because windows containers have host/kernel compatibility requirements that differ from generic Linux image portability.
Incorrect Answers
A:A newer Windows base image can increase rather than solve host/image build mismatch. For process isolation, the host and image compatibility matrix matters; use a supported matching image or an appropriate isolation mode.
B:Application pool settings cannot make an incompatible Windows container kernel/build combination valid. Use a compatible base image/host or supported isolation mode.
D:Image history and registry access can expose embedded credentials even if containers do not print them. Here, Windows containers have host/kernel compatibility requirements that differ from generic Linux image portability.
Question 538
A containerized website relies on a scheduled task running in the old physical server rather than an application process. Which administrative change most directly resolves the documented failure?
- Move persistent data to supported mounted or external storage before deployment.
- Rebuild and redeploy from a supported patched base image with dependency scanning.
- Assess supported image capabilities and refactor or choose a compatible base image.
- Extract the scheduled work into a supported external job/worker architecture.
Explanation
Correct Answer
D:Moving the HTTP endpoint to a container does not automatically migrate unrelated host scheduler tasks. For that reason, extract the scheduled work into a supported external job/worker architecture.
Incorrect Answers
A:Container lifecycle replacement can discard writable-layer changes, so state must live outside the disposable instance. In this situation, moving the HTTP endpoint to a container does not automatically migrate unrelated host scheduler tasks.
B:Container base OS packages remain part of the deployment's vulnerability surface. However, moving the HTTP endpoint to a container does not automatically migrate unrelated host scheduler tasks.
C:Windows container base images include different OS components and do not replicate every full server role. Here, moving the HTTP endpoint to a container does not automatically migrate unrelated host scheduler tasks.
Question 539
A Windows IIS image contains an outdated vulnerable base layer even though application binaries were recently patched. Which supported action should be taken for this reported condition?
- Rebuild and redeploy from a supported patched base image with dependency scanning.
- Assess supported image capabilities and refactor or choose a compatible base image.
- Use an appropriate Windows container base image and compatible runtime for the application.
- Validate the Windows container host and image build compatibility or use supported isolation.
Explanation
Correct Answer
A:Rebuild and redeploy from a supported patched base image with dependency scanning. The underlying technical reason is that container base OS packages remain part of the deployment's vulnerability surface.
Incorrect Answers
B:Windows container base images include different OS components and do not replicate every full server role. Here, container base OS packages remain part of the deployment's vulnerability surface.
C:Container OS base image and framework requirements must match the workload's platform dependencies. In this situation, container base OS packages remain part of the deployment's vulnerability surface.
D:Windows containers have host/kernel compatibility requirements that differ from generic Linux image portability. However, container base OS packages remain part of the deployment's vulnerability surface.
Question 540
An application stores its session state in local process memory and users lose sessions when the IIS container scales to multiple replicas. Which response addresses the identified root cause without weakening other controls?
- Use an appropriate Windows container base image and compatible runtime for the application.
- Move session state to a supported distributed store or adopt stateless application design.
- Configure a valid container entrypoint that keeps the required IIS/application process running.
- Move persistent data to supported mounted or external storage before deployment.
Explanation
Correct Answer
B:Multiple container instances do not automatically share in-memory user sessions. A suitable corrective action is to move session state to a supported distributed store or adopt stateless application design.
Incorrect Answers
A:Container OS base image and framework requirements must match the workload's platform dependencies. Here, multiple container instances do not automatically share in-memory user sessions.
C:Container lifetime follows its primary process; a completed configuration script stops the container. However, multiple container instances do not automatically share in-memory user sessions.
D:Container lifecycle replacement can discard writable-layer changes, so state must live outside the disposable instance. Here, multiple container instances do not automatically share in-memory user sessions.
Configuring Windows Server Hybrid Advanced Services (AZ-801) Practice Tests