AZ-802 Practice Exam 1 — 50 Explained Questions
50 questions
Open this course’s practice exams →Windows Server · Public course · v1.1.1
Study Windows Server identity, virtual machines, networking, storage, security and hybrid management with flashcards, explained questions and four practice exams.
1051 flashcards · 506 practice questions
Choose topics, then use Flashcards, Learn, Write, Match, Practice Questions or Mock Exam when the course has suitable content.
Unofficial study material, independently written and not affiliated with or endorsed by Microsoft. These are original learning questions, not actual exam questions. Product support and exam scope can change; a practice percentage is not a Microsoft exam scaled score.
Fixed question sets within this course. Open study modes to take an exam and save results in your browser.
50 questions
Open this course’s practice exams →50 questions
Open this course’s practice exams →50 questions
Open this course’s practice exams →50 questions
Open this course’s practice exams →AD DS · AD DS | Deploy and manage AD DS domain controllers
Role installation adds AD DS binaries. Promotion creates or joins the directory as a domain controller and requires a restart.
AD DS · AD DS | Deploy and manage AD DS domain controllers
Install-ADDSForest creates a new forest. Install-ADDSDomain creates a domain; Install-ADDSDomainController adds a DC to an existing domain.
AD DS · AD DS | Deploy and manage AD DS domain controllers
It checks prerequisites for an additional DC installation without promoting the server. A successful test does not replace post-promotion health checks.
AD DS · AD DS | Deploy and manage AD DS domain controllers
It provides a local recovery credential for Directory Services Restore Mode when normal domain authentication is unavailable. Protect it independently for each DC.
AD DS · AD DS | Deploy and manage AD DS domain controllers
A Domain Admin or an account with equivalent delegated permissions can perform the installation. Forest/schema preparation can require additional forest-level privileges.
AD DS · AD DS | Deploy and manage AD DS domain controllers
Use reachable DNS capable of resolving the existing AD domain and its service records. Public DNS alone cannot locate private domain services.
AD DS · AD DS | Deploy and manage AD DS domain controllers
Verify AD/DNS health, SYSVOL and NETLOGON shares, replication, and relevant event logs. dcdiag and repadmin help assess these layers.
AD DS · AD DS | Deploy and manage AD DS domain controllers
IFM reduces initial replication traffic by supplying directory data locally. It still requires a live DC for remaining changes and does not create an isolated independent replica.
AD DS · AD DS | Deploy and manage AD DS domain controllers
Normal demotion updates directory topology and removes its DC role cleanly. Check FSMO roles and surviving DNS/DC capacity before retirement.
AD DS · AD DS | Deploy and manage AD DS domain controllers
No. DC operating-system version and functional level are separate choices; validate all DC version requirements before raising levels.
AD DS · AD DS | Deploy and manage AD DS domain controllers
Set the Azure NIC's private IP allocation to static. Normally leave DHCP enabled inside the Windows guest so Azure supplies the reserved address.
AD DS · AD DS | Deploy and manage AD DS domain controllers
Configure the workload VNet/client DNS to reachable AD DNS private addresses. Azure-provided DNS alone does not publish the existing domain's AD service records.
AD DS · AD DS | Deploy and manage AD DS domain controllers
Use persistent managed data disks with host caching set to None for the AD database, logs, and SYSVOL. Do not place these on the temporary/resource disk.
AD DS · AD DS | Deploy and manage AD DS domain controllers
Deploy at least two DC VMs in separate availability zones where available, or an availability set where zones are unsuitable. Maintain AD-aware backups as well as VM availability.
AD DS · AD DS | Deploy and manage AD DS domain controllers
A site-to-site VPN or ExpressRoute can connect the on-premises network and Azure VNet. Allow required DNS, authentication, replication, and management traffic across the path.
AD DS · AD DS | Deploy and manage AD DS domain controllers
They map Azure network prefixes to an AD site, guiding nearby DC selection and replication topology. Connectivity alone does not create this directory mapping.
AD DS · AD DS | Deploy and manage AD DS domain controllers
DC management and directory traffic should use restricted private paths. Bastion or private management access avoids exposing administrative endpoints directly to the internet.
AD DS · AD DS | Deploy and manage AD DS domain controllers
Refresh the guest's DHCP-derived configuration or restart as appropriate so the new DNS servers take effect. A portal change alone may not immediately update an existing guest.
AD DS · AD DS | Deploy and manage AD DS domain controllers
No. Configure appropriate custom DNS on each connected workload network and verify DNS reachability.
AD DS · AD DS | Deploy and manage AD DS domain controllers
An arbitrary disk copy is not an AD-aware consistent backup with a tested restore procedure. Virtualization safeguards do not replace directory backup and recovery planning.
AD DS · AD DS | Deploy and manage AD DS domain controllers
A branch with weak physical security can use an RODC to provide local directory services while limiting writable-directory and credential exposure. Its WAN dependencies still require planning.
AD DS · AD DS | Deploy and manage AD DS domain controllers
No. It receives directory changes from writable DCs; directory writes require a writable DC.
AD DS · AD DS | Deploy and manage AD DS domain controllers
Yes, it can host read-only AD-integrated DNS and act as a global catalog. These roles do not make its directory writable.
AD DS · AD DS | Deploy and manage AD DS domain controllers
An administrator precreates an RODC account, selects its delegated administrator and policies, and a branch operator attaches the matching server to that account.
AD DS · AD DS | Deploy and manage AD DS domain controllers
Install-ADDSDomainController uses -UseExistingAccount in the staged installation workflow. The server must match the prepared account.
AD DS · AD DS | Deploy and manage AD DS domain controllers
It allows administration of the RODC server without granting broad domain administration. It does not authorize arbitrary AD directory changes.
AD DS · AD DS | Deploy and manage AD DS domain controllers
It needs a reachable writable DC to validate the account. Password Replication Policy then governs whether the credential may be cached.
AD DS · AD DS | Deploy and manage AD DS domain controllers
Workstation/domain authentication can depend on both identities. Caching a permitted user alone does not ensure the computer's domain authentication succeeds offline.
AD DS · AD DS | Deploy and manage AD DS domain controllers
Deny takes precedence over allow. Evaluate nested group membership as well as direct entries.
AD DS · AD DS | Deploy and manage AD DS domain controllers
No. Allowed means eligible for replication; the revealed/cached list shows secrets actually stored on the RODC.
AD DS · AD DS | Deploy and manage AD DS domain controllers
Authenticated accounts can include authentication forwarded to a writable DC. Revealed accounts indicate credentials actually cached on the RODC.
AD DS · AD DS | Deploy and manage AD DS domain controllers
It is empty by default. Populate carefully scoped branch groups instead of broadly allowing privileged identities.
AD DS · AD DS | Deploy and manage AD DS domain controllers
A stolen or compromised branch DC could expose its cached secrets. Excluding valuable administrative credentials reduces the resulting compromise.
AD DS · AD DS | Deploy and manage AD DS domain controllers
It displays accounts whose passwords have been revealed to that RODC. This checks actual exposure rather than only PRP eligibility.
AD DS · AD DS | Deploy and manage AD DS domain controllers
Identify actually exposed accounts and reset their relevant user/computer credentials through a controlled incident response. Changing PRP alone does not invalidate stolen secrets.
AD DS · AD DS | Deploy and manage AD DS domain controllers
Improperly granting Replicating Directory Changes All to RODC-related principals can bypass the intended credential restriction. Investigate sensitive replication permissions.
AD DS · AD DS | Deploy and manage AD DS domain controllers
Check nested membership, PRP attributes and group membership consistency across DCs, and replication permissions. Different DC views can reflect replication faults.
AD DS · AD DS | Deploy and manage AD DS domain controllers
Schema master and domain naming master are forest-wide. RID master, PDC emulator, and infrastructure master exist once per domain.
AD DS · AD DS | Deploy and manage AD DS domain controllers
It authorizes updates to the forest schema. Ordinary user authentication can continue when this role is temporarily unavailable.
AD DS · AD DS | Deploy and manage AD DS domain controllers
It authorizes adding or removing domains and application partitions in the forest. It is not the DNS server for every domain.
AD DS · AD DS | Deploy and manage AD DS domain controllers
It allocates RID pools to domain DCs so they can create unique security principal SIDs. Existing local pools can let object creation continue temporarily during an outage.
AD DS · AD DS | Deploy and manage AD DS domain controllers
It receives preferential password updates and can be consulted after another DC rejects a recently changed password. It also supports account lockout coordination and time hierarchy.
AD DS · AD DS | Deploy and manage AD DS domain controllers
It maintains references to objects in other domains. GC placement constraints have exceptions when all DCs are GCs or the forest uses AD Recycle Bin.
AD DS · AD DS | Deploy and manage AD DS domain controllers
Transfer when the current holder is reachable and functioning, such as during planned retirement. Seize only when transfer is impossible and the holder cannot return as a valid role owner.
AD DS · AD DS | Deploy and manage AD DS domain controllers
It attempts transfer and can seize when transfer fails. It should not be used as a routine synonym for a normal planned move.
AD DS · AD DS | Deploy and manage AD DS domain controllers
Use Get-ADForest for schema/domain-naming owners and Get-ADDomain for domain role owners, or netdom query fsmo. Verify replication after any move.
AD DS · AD DS | Deploy and manage AD DS domain controllers
Retire or properly rebuild/demote the former owner before reintroduction. Reconnecting a stale DC unchanged risks conflicting directory state.
AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
Users in AccountDomain are trusted by ResourceDomain. The resource domain is the trusting side; resource permissions must still grant access.
AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
No. A trust enables authentication routing; resource ACLs and any selective-authentication gate separately control access.
AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
They are created automatically as two-way transitive trusts within the forest. They do not create an independent forest security boundary.
AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
An external trust is a nontransitive relationship between specific domains. A forest trust routes authentication among domains of two participating forests.
AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
No. Forest-trust transitivity covers domains inside its two participating forests, not an unlimited chain of other forest trusts.
AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
It requires explicit Allowed to authenticate permission on target computers before authentication to those resources. Resource ACL permissions remain necessary.
AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
It limits acceptance of inappropriate SIDs presented across the trust. Disabling it to accommodate SIDHistory requires a deliberate security-reviewed migration design.
AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
Verify reciprocal DNS resolution, routed service connectivity, compatible functional levels, and suitable authority on the participating sides.
AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
It shortens an authentication path between domains in the same forest. It changes routing efficiency without replacing resource authorization.
AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
A site represents network locality based on IP subnets. It can contain DCs from multiple domains, and one domain can span several sites.
AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
Its IP address is matched to an AD subnet object associated with a site. Correct subnet mappings support nearby DC discovery.
AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
nltest /dsgetsite reports the discovered site. Use it with subnet and DC-placement checks when clients select distant DCs.
AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
It influences replication path preference, generally favoring the lower total cost. It does not define the replication interval.
AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
The schedule defines when intersite replication is permitted. The interval defines how often it is attempted inside those permitted windows.
AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
The default interval is 180 minutes, and the minimum is 15 minutes. A closed schedule still prevents replication outside its allowed window.
AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
No. It models a logical replication path; the IP network must independently allow the necessary traffic.
AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
Default transitive bridging assumes suitable network reachability. A partially routed topology may require bridges that reflect actual connectivity.
AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
It can reduce dependency on a local global catalog for subsequent membership lookup. Initial retrieval and cache freshness still require appropriate connectivity.
AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
The Knowledge Consistency Checker creates replication connections. Intersite topology generation coordinates connections between sites.
AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
It represents inbound replication to that DC from its named source partner. Its location identifies the destination.
AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
The schema and configuration partitions replicate throughout the forest. A DC's domain partition replicates within its own domain.
AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
It holds a partial read-only replica of objects in other forest domains using selected attributes. It does not hold every attribute or password from every domain.
AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
The GPO container replicates in AD, while its template and scripts replicate through SYSVOL. Modern SYSVOL uses DFS Replication, which must be checked separately.
AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
repadmin /replsummary summarizes replication health; repadmin /showrepl DC02 shows that DC's inbound partner status.
AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
Replication partners must resolve and contact the correct DC endpoints. An RPC error can reflect name resolution or service connectivity rather than directory corruption.
AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
Synchronization requests do not repair DNS, routing, RPC access, or a failed source. Correct the underlying cause and then verify replication.
AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
Isolation beyond applicable deletion-retention limits can leave lingering objects. Controlled recovery must assess their directory state before replication resumes.
AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
It can prevent alternate suitable DCs from handling intersite replication after failure. Allow automatic partner selection unless network requirements justify constraints.
AD DS · AD DS | Create and manage AD DS security principals
Permissions refer to the account's SID, which remains the same when renamed. The display or logon name is not the security identity.
AD DS · AD DS | Create and manage AD DS security principals
The replacement receives a new SID. Name reuse alone does not restore permissions granted to the deleted identity.
AD DS · AD DS | Create and manage AD DS security principals
A security group can receive permissions. A distribution group is intended for messaging and is not a DACL authorization principal.
AD DS · AD DS | Create and manage AD DS security principals
Accounts and global groups from its own domain. A trust does not allow a global group to contain arbitrary external-domain users.
AD DS · AD DS | Create and manage AD DS security principals
It grants permissions on resources in its own domain. Its membership can include eligible principals from trusted domains.
AD DS · AD DS | Create and manage AD DS security principals
Accounts join Global role groups, which join Domain Local resource groups, which receive Permissions. This separates business membership from resource rights.
AD DS · AD DS | Create and manage AD DS security principals
OU placement determines delegation and applicable policies. Creating an account in an unintended container can change who manages it and which policies apply.
AD DS · AD DS | Create and manage AD DS security principals
Check replication, nested membership, the user's actual fresh logon token, and resource ACLs. Existing tokens may not reflect new membership.
AD DS · AD DS | Create and manage AD DS security principals
Disabling blocks new account authentication but does not automatically remove ownership, every application grant, or all existing sessions. Complete the intended access and retention workflow.
AD DS · AD DS | Create and manage AD DS security principals
It adds a Universal group between domain-specific Global role groups and Domain Local resource groups. This aggregates a stable role across domains within one forest.
AD DS · AD DS | Create and manage AD DS security principals
Universal groups can aggregate eligible users/global/universal groups from their own forest. They are not general cross-forest containers.
AD DS · AD DS | Create and manage AD DS security principals
Nest an appropriate external global group or eligible principal into a resource-domain domain-local group, then grant that group resource permissions.
AD DS · AD DS | Create and manage AD DS security principals
It represents an external security principal's SID in the local directory. It is not a copied user account with a local password database.
AD DS · AD DS | Create and manage AD DS security principals
It limits forest-wide universal membership churn as individual users change within domain-specific global groups. GC replication and tokens still need consideration.
AD DS · AD DS | Create and manage AD DS security principals
Commands/consoles can default to an unintended DC or domain. Use the appropriate -Server or connection context to manage the correct directory object.
AD DS · AD DS | Create and manage AD DS security principals
No. Global membership is limited to accounts/global groups from its own domain. Use eligible universal/domain-local nesting for broader designs.
AD DS · AD DS | Create and manage AD DS security principals
Existing members and parent-group memberships can violate the target scope's constraints. Conversion must fit the intended membership and authorization model.
AD DS · AD DS | Create and manage AD DS security principals
Membership changes still require replication and suitable token renewal, and resource ACLs/selective authentication remain separate checks.
AD DS · AD DS | Create and manage AD DS security principals
Use it for a supported service running on approved domain hosts, especially a server farm. AD manages its password rather than administrators sharing or rotating it manually.
AD DS · AD DS | Create and manage AD DS security principals
An sMSA provides managed service credentials for one host. A gMSA can be used by multiple authorized hosts.
AD DS · AD DS | Create and manage AD DS security principals
A local virtual account such as NT SERVICE\ServiceName uses the host computer's identity for network access. It is not a shared domain account for a server farm.
AD DS · AD DS | Create and manage AD DS security principals
It normally authenticates as the computer account while having fewer local privileges than LocalSystem.
AD DS · AD DS | Create and manage AD DS security principals
LocalService generally presents anonymous network credentials. NetworkService normally uses the domain computer identity.
AD DS · AD DS | Create and manage AD DS security principals
A KDS root key must be available to the relevant DCs. Confirm an existing key before creating another.
AD DS · AD DS | Create and manage AD DS security principals
It allows replication convergence before hosts depend on generated passwords. Immediate/backdated lab shortcuts do not repair production replication problems.
AD DS · AD DS | Create and manage AD DS security principals
PrincipalsAllowedToRetrieveManagedPassword identifies the eligible principals, commonly a security group of approved computer accounts.
AD DS · AD DS | Create and manage AD DS security principals
Install-ADServiceAccount installs it locally; Test-ADServiceAccount checks whether the host can use it. Run them on the authorized service host.
AD DS · AD DS | Create and manage AD DS security principals
Use its domain identity with a trailing dollar sign, such as CORP\gmsaWeb$. Do not manually type the generated managed password.
AD DS · AD DS | Create and manage AD DS security principals
The host's group membership token may be stale. Refresh its machine authentication state, such as through a controlled reboot, after verifying replication.
AD DS · AD DS | Create and manage AD DS security principals
It does not prove application compatibility, grant all resource permissions, or make Kerberos delegation safe. Check SPNs, required logon rights, and service-specific support.
AD DS · AD DS | Manage Windows Server by using domain-based Group Policies
The Group Policy Container is stored in AD; the Group Policy Template is stored in SYSVOL. Both must be available and consistent.
AD DS · AD DS | Manage Windows Server by using domain-based Group Policies
It can be linked to a site, domain, or OU. Groups and individual users are filtering targets rather than direct link containers.
AD DS · AD DS | Manage Windows Server by using domain-based Group Policies
Local, Site, Domain, then parent-to-child OUs. Later applicable settings normally win conflicts.
AD DS · AD DS | Manage Windows Server by using domain-based Group Policies
Link order 1 has the highest precedence among applicable links at that container. Settings in different areas still accumulate.
AD DS · AD DS | Manage Windows Server by using domain-based Group Policies
That GPO does not manage the setting. It is not an explicit instruction to disable the feature.
AD DS · AD DS | Manage Windows Server by using domain-based Group Policies
Block inheritance is a container setting that stops ordinary inherited links. Enforced is a link setting that survives inheritance blocking and resists lower-level overrides.
AD DS · AD DS | Manage Windows Server by using domain-based Group Policies
The target needs Read and Apply Group Policy, subject to deny entries. Enforcing a link does not bypass these permissions.
AD DS · AD DS | Manage Windows Server by using domain-based Group Policies
It evaluates a computer condition to filter the entire GPO. It differs from per-item preference targeting.
AD DS · AD DS | Manage Windows Server by using domain-based Group Policies
It processes the user's normal user GPO list, then the user settings selected from the computer's location. The computer-based list wins conflicts.
AD DS · AD DS | Manage Windows Server by using domain-based Group Policies
It uses only the user GPO list selected from the computer's location. This suits controlled session hosts or kiosks.
AD DS · AD DS | Manage Windows Server by using domain-based Group Policies
Normally 90 minutes plus up to 30 minutes of random offset. Some settings still require foreground processing, logoff, or restart.
AD DS · AD DS | Manage Windows Server by using domain-based Group Policies
Use gpresult, RSoP, or GPMC Group Policy Results with effective local state. Check denied GPO reasons, AD/SYSVOL, and GroupPolicy events.
AD DS · AD DS | Manage Windows Server by using domain-based Group Policies
Preferences generally configure settings that users may change, though refresh can reapply them. Enforced policy settings take precedence in a conflict.
AD DS · AD DS | Manage Windows Server by using domain-based Group Policies
It creates the item if absent and leaves an existing item unchanged. Confirm the preference extension's supported behavior.
AD DS · AD DS | Manage Windows Server by using domain-based Group Policies
It changes specified properties while preserving unspecified ones, and commonly creates the item if absent. It avoids unnecessary deletion and recreation.
AD DS · AD DS | Manage Windows Server by using domain-based Group Policies
It deletes and recreates the item. Repeated replacement can interrupt resources such as active drive mappings.
AD DS · AD DS | Manage Windows Server by using domain-based Group Policies
It evaluates conditions for an individual preference item. Other items in the same GPO can use different conditions.
AD DS · AD DS | Manage Windows Server by using domain-based Group Policies
It supplies an initial preference without resetting later user changes during normal reapplication.
AD DS · AD DS | Manage Windows Server by using domain-based Group Policies
Preferences often persist unless removal behavior is configured. Where supported, Remove this item when it is no longer applied supplies cleanup and automatically sets the action to Replace; test the resulting refresh behavior.
AD DS · AD DS | Manage Windows Server by using domain-based Group Policies
Historical cpassword secrets in SYSVOL are recoverable. Use Windows LAPS or managed service accounts for the appropriate password-management requirement.
AD DS · AD DS | Manage Windows Server by using domain-based Group Policies
Replacing membership or deleting existing members can remove necessary administrators or add unintended access. Choose explicit add/remove semantics and test effective membership.
Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
It accepts the administrator’s browser connection and performs management operations against the selected servers using Windows management interfaces. The gateway and the managed target can be different machines.
Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
A shared gateway provides one browser-accessible management endpoint for several administrators. A local desktop installation is suitable for individual administration or evaluation.
Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
The certificate must identify the gateway name used by clients and chain to a CA those clients trust. A certificate installed on the gateway alone does not establish client trust.
Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
Access to the gateway and permission to administer the target server are separate. A user who can open the gateway still needs a suitable identity and rights for the target operation.
Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
Onboard the supported server to Azure Arc, then deploy the Windows Admin Center extension to its Arc resource. The portal connection uses the configured Arc service path.
Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
Reader and Windows Admin Center Administrator Login at an applicable scope covering the Arc resource. Installing the extension and registering providers involve separate permissions.
The login role contains dataActions and cannot be assigned at management-group scope.
Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
No. The portal experience uses the server’s outbound service connectivity; its required outbound HTTPS endpoints still must be reachable.
Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
The portal experience supports a defined per-server tool set. A third-party tool available on a local gateway is not automatically supported by the Azure-hosted access experience.
Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
TCP 5985 for HTTP and TCP 5986 for HTTPS. A listener, firewall path and valid authentication are still required.
Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
It tests whether the target’s WSMan endpoint responds. It does not prove that the current user has authorization for every PowerShell endpoint or resource operation.
Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
Use New-PSSession when you need a reusable remote session and its session state across commands. Invoke-Command can execute a one-off block without retaining that persistent state.
Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
It refers to the remote machine executing that script block. Local and remote filesystem paths, modules and service names belong to their respective execution contexts.
Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
Returned objects are commonly serialized copies. Perform operations requiring the live object inside the remote script block instead of assuming all methods survive serialization.
Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
Credentials used for a session from workstation A to server B are not automatically delegated when B accesses a resource on server C as that user. Successful authentication to B is insufficient evidence of identity delegation to C.
Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
No. Microsoft’s second-hop guidance excludes WinRM for this method. A supported SMB or other service delegation scenario must not be generalized to a second WinRM session.
Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
CredSSP delegates and caches the user’s credentials on that server. It requires a trusted intermediate server and an intentional decision about that exposure.
Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
The cmdlets, functions, external commands and parameter constraints exposed to a role. It defines what the operator is permitted to do through the endpoint.
Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
It maps identities to role capabilities and configures endpoint behavior such as run-as identity and transcripts. Role definitions must be exposed through a registered session endpoint.
Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
A gMSA supplies a controlled domain service identity to which you can grant the required network permissions. A local virtual account’s network identity differs and commonly uses the computer account.
Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
Test an intended allowed action and a forbidden command or parameter value. Verify that the endpoint rejects operations outside the designed role, not merely that a session can connect.
Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
It allows the client to verify the server’s identity. User authentication then proves who is requesting access; the host key does not grant the user administrative rights.
Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
It is installed by default. Administrators still need to enable and configure the sshd service and confirm the required firewall access.
Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
Check the sshd service and TCP 22, including the OpenSSH-Server-In-TCP firewall rule and the permitted source scope.
Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
PowerShell remoting requires a configured SSH subsystem that launches the PowerShell remoting host. An ordinary interactive shell can work without that subsystem.
Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
HostName selects the SSH connection path in commands such as Enter-PSSession and New-PSSession. ComputerName normally selects the WSMan remoting path.
Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
No. Current PowerShell SSH-remoting documentation does not support the WinRM endpoint-configuration and JEA hosting model. Choose a supported transport for the required endpoint behavior.
Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
The key file must be stored in the correct location and protected with appropriate ACLs for the account and sshd configuration. A matching public key in an inaccessible or improperly protected file can still fail authentication.
Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
Verify the server’s identity and the reason for the change before trusting the new key. A planned rebuild is possible, but the warning can also indicate the wrong endpoint or interception.
Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
It requires authentication before the full remote session is established. This reduces the exposure of the remote session to unauthenticated clients.
Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
TCP 3389. The listener, network rules, Windows Firewall and user logon authorization must all permit the connection.
Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
Effective policy can remove the required logon right or assign a deny right. Membership alone does not override the effective user-rights policy.
Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
The Deny log on through Remote Desktop Services right takes precedence. Investigate effective group memberships and applied policy.
Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
No. Those connections support administration. Serving multiple application users requires the appropriate RDS deployment and licensing.
Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
Ping tests ICMP reachability, not the RDP listener, TCP 3389 path, NLA authentication or remote logon rights. Test those layers separately.
Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
A Resultant Set of Policy or gpresult report shows the effective policies. Review the applied Allow and Deny remote-logon rights instead of editing only the local setting.
Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
Check client compatibility, valid credentials, account state and effective logon rights. Retain NLA when possible rather than treating a weaker authentication setting as the default repair.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
It creates an Azure management resource and connects the existing server to supported Azure management services. The workload continues to run on its original physical server or hypervisor.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
The Hybrid Instance Metadata Service, HIMDS, manages the connection and the machine identity used for Azure authentication. It is distinct from the telemetry agent.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
GCArcService handles the Arc machine-configuration service. ExtensionService handles VM extensions, and himds handles hybrid metadata and identity.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
It displays Connected Machine agent configuration and connection information for the local Arc server. A connected status is a control-path check, not proof that every extension or workload is healthy.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
The agent initiates outbound connections to the required Azure service endpoints. Permit the documented HTTPS/DNS path and configure a proxy when the environment requires one.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
It locates the Azure management resource metadata. It does not move the server’s operating system or business data to that region.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
Arc registration and identity must be unique to the server. Use the documented preparation and registration workflow instead of copying the enrolled identity to unrelated machines.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
No. Azure resource permissions and guest Windows permissions are separate. The chosen access tool and operation determine which identity and authorization layer are required.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
It audits or configures operating-system settings inside the guest. Azure resource compliance alone does not establish the actual guest setting.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
It reports the observed configuration without applying the requested setting. An audit failure is a finding, not evidence that a repair has run.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
Apply and Monitor applies the configuration and reports later drift. Apply and Autocorrect also brings drifted settings back into conformance.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
The supported machine-configuration extension and a system-assigned managed identity are required. The service uses that identity and extension to obtain and evaluate assignments.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
The Connected Machine agent includes the relevant machine-configuration capability. Do not apply Azure-VM extension prerequisites indiscriminately to an Arc server.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
Microsoft.GuestConfiguration. Required resource providers and permissions must be available in the target subscription.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
A guest assignment identifies the configuration to evaluate or apply on that machine. The package contains the settings and dependencies needed by the guest configuration engine.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
If they demand different values for the same setting, each controller can undo the other’s change. Define a consistent desired state and management authority before enabling correction.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
The extension publisher, type and handler version identify the component to install. Select a supported Arc extension for the server’s OS and cloud.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
The Arc catalog and prerequisites can differ from the Azure VM catalog. An extension supported on an Azure VM is not automatically supported on every Arc server.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
The extension manager, represented by ExtensionService on Windows, manages extension installation, removal and upgrade. HIMDS has a separate metadata and identity role.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
Use protected settings where the extension supports them. Ordinary settings should not contain credentials or secrets visible through normal resource configuration.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
The control connection can work while the extension has a separate problem, such as blocked download endpoints, an unsupported handler or local installation failure. Inspect extension provisioning state and local logs.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
It updates supported extension handler versions according to the publisher’s rollout. It does not replace Windows operating-system patching.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
Check the Azure extension provisioning result and the extension’s local handler logs. The Azure error and local execution failure often describe different parts of the same deployment.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
Extensions can install agents or run tasks inside the server with high local privileges. Scope and audit Azure extension-management permissions accordingly.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
It uses the guest’s configured update source, such as Microsoft Update or WSUS. It does not replace that source with a universal Azure patch repository.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
No. Azure Update Manager is a separate service for assessment and patching of Azure VMs and Arc-connected servers. Do not use old MMA/workspace requirements as its current architecture.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
Assessment discovers applicable updates and reports the state. Installation attempts to apply the selected updates; a successful assessment does not prove patch installation will succeed.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
It defines a maintenance window and patch settings such as update selection and reboot behavior. Machines must be associated with the configuration or selected through its supported dynamic scope.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
Customer Managed Schedules. Configure the supported scheduling prerequisites rather than assuming every guest-patching mode has identical behavior.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
The window must accommodate installation and required reboot behavior. A window that is too short can leave selected updates unapplied or only partially completed.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
Tags and other selection criteria determine which machines are included at run time. A scope or tag mismatch can omit a server even when it is visible in Azure inventory.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
Separating waves preserves a functioning authentication or application path while a peer is updating or restarting. Validate health before progressing to the next wave.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
Check the configured update source, guest servicing state, patch extension, selected orchestration mode, machine power state, maintenance duration and reboot requirements. Use the installation result rather than assuming assessment certified each prerequisite.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
No. Updating an extension handler and installing Windows OS updates are separate maintenance tasks. Plan and verify each through the appropriate service.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
A runbook is the stored automation definition. A job is one execution of that runbook, with its own input, output streams and result state.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
Choose a worker when execution needs the worker’s local network path, installed modules or on-premises resources. The cloud sandbox does not automatically acquire a branch server’s private route.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
No. Deploy and configure the supported extension-based worker and associate it with the intended worker group. Arc registration is a management prerequisite, not the full worker configuration.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
The System account runs Windows hybrid jobs by default. A configured Hybrid Worker credential or explicit resource credentials can change how local resources are accessed.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
No. Azure authentication and Windows share/filesystem authorization are separate. Grant the actual Windows execution identity the required local or domain resource access.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
The Automation account’s system-assigned managed identity is used for the documented hybrid-job Azure authentication path. The Arc worker identity cannot be substituted for it in that configuration.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
The supported runtime and compatible modules must exist on the worker, with the relevant extension/runtime configuration. Selecting a runtime in the runbook does not install every dependency on the worker.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
No. Test the draft, then publish the intended version. Configure the schedule or job against the published version and chosen execution environment.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
Nonterminating errors may not stop the script or fail the job. Review output/error streams and use intentional error handling to reflect the required business outcome.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
It helps prevent reuse of an unintended persisted Azure context. Authenticate deliberately and set the subscription/context for the job’s required operations.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
It checks existing state and brings it to the desired result without blindly recreating resources or duplicating actions. Verify each effect and handle failures deliberately.
Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
It supplies a configured credential asset for hybrid jobs in that group to use instead of the default System context. It does not itself grant an Azure RBAC role.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Remote Desktop Protocol is carried through the Hyper-V connection, allowing redirection and a richer display without a working guest IP network.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
In Hyper-V Settings, select Enhanced Session Mode Policy and enable Allow enhanced session mode.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Enable Use enhanced session mode under the user's Enhanced Session Mode settings. The host policy must also permit the feature.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
The guest must have Remote Desktop Services enabled and run at least Windows 10 or Windows Server 2016 in the documented Windows workflow.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Open the enhanced connection's Show options and choose the required local resources before connecting. Redirect only resources needed for the task.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Basic session mode provides console display and keyboard/mouse access. Enhanced mode adds RDP-based capabilities once its prerequisites are met.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Set-VMHost -EnableEnhancedSessionMode $true permits enhanced sessions. Get-VMHost can display the EnableEnhancedSessionMode property for verification.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Check the user's Use enhanced session mode setting, guest OS support, guest startup state, and Remote Desktop Services configuration. Host permission alone does not prepare the guest.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
It queries virtualization objects on the Hyper-V host HV01. It does not execute a command inside a guest merely because that guest is listed.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Network remoting targets a reachable computer and its remoting endpoint. PowerShell Direct executes inside a locally running supported Windows VM through the host-to-guest channel without depending on guest networking.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
The host and guest require supported Windows versions, including Windows Server 2016 or later or Windows 10 or later. Use the documented Windows PowerShell Direct cmdlets.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
The caller must have Hyper-V administrator rights on the host and supply valid credentials inside the guest. Host administration does not imply guest administrator access.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Use Invoke-Command -VMName 'APP01' -Credential $guestCredential -ScriptBlock { Get-NetIPConfiguration } on the Hyper-V host.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Create it with New-PSSession -VMName and guest credentials, reuse it with session-based cmdlets, then remove it with Remove-PSSession.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Inspect the Hyper-V PowerShell Direct Service, vmicvmsession, along with credentials and guest readiness. Guest firewall or DNS changes do not fix a missing Direct endpoint.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Hyper-V sockets use the host-to-guest VMBus path; Linux uses a compatible VSOCK endpoint. An SSH endpoint must be configured for that socket transport.
Socket support alone is not a complete SSH Direct distribution or host-version compatibility guarantee.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
No. TCP SSH proves an IP endpoint exists; a Direct workflow needs the compatible Hyper-V socket endpoint and host tooling. Authentication and host-key checks still apply.
Verify the specific host and Linux implementation rather than assume a universal compatibility matrix.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Disconnect the guest network and test the supported configured socket path. A successful connection with networking present can hide an implementation's IP fallback.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
It exposes CPU virtualization extensions so the VM can run its own hypervisor and inner VMs. The middle VM becomes a virtualization host.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Use Intel VT-x with EPT, Windows Server 2016 or later on the outer host, and VM configuration version 8.0 or later.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
AMD EPYC/Ryzen or later requires Windows Server 2022 or later on the outer host and VM configuration version 9.3 or later.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Run Set-VMProcessor -VMName 'NestedHost01' -ExposeVirtualizationExtensions $true on the outer host while the VM is off.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Install and configure Hyper-V in the middle VM. Exposing CPU extensions alone does not install the role or create inner guests.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Enable it when inner guest MAC addresses must pass through the outer switch. The surrounding network must permit that design.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Create an internal virtual switch and NAT inside the middle VM. Give inner guests suitable IP, gateway, and DNS settings; NAT alone does not provide DHCP.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Its memory cannot fluctuate with Dynamic Memory or be resized while running. Shut down that VM before changing its memory.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Use Standard security type with a VM size supporting nesting. Confirm current size and platform prerequisites before deployment.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
It is the RAM available during boot and installation. Meet the guest's startup requirements even when Maximum RAM is much higher.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
It sets the lower assigned-memory boundary after startup. An excessively low minimum can increase guest paging and latency.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
It defines the upper allocation limit, not a reservation or guarantee. Host available memory and guest support still limit actual allocation.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
It requests extra RAM above reported guest demand. Hyper-V attempts to provide it but cannot guarantee it during host pressure.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
It expresses relative preference when the host cannot satisfy every VM's memory request. A higher priority does not create additional physical RAM.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Inspect MemoryDemand, MemoryAssigned, and MemoryStatus on the VM, together with guest paging and host available memory.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Choose it when the application requires fixed RAM or a feature such as DDA or running nested Hyper-V requires a stable allocation.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
It temporarily bridges a VM restart when startup RAM exceeds assigned RAM, physical RAM is unavailable, and memory cannot be reclaimed. It is not used as general RAM overcommit or to solve insufficient failover capacity.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Use DynamicMemoryEnabled, StartupBytes, MinimumBytes, and MaximumBytes. Buffer and Priority tune extra allocation and relative preference.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
It reports guest OS responsiveness. The VM's Running state alone only shows that the host allocated resources and started it.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
The guest shutdown service delivers a cooperative shutdown request to the guest. A nonresponsive guest or missing service may prevent graceful completion.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Data exchange, also called key-value pair exchange or KVP, supplies guest metadata. Missing displayed IP information does not alone prove network failure.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
It works with VSS to support consistent backup and production checkpoints. Application writers and guest support must also be healthy.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Guest Service Interface enables host-to-guest file copying. Enable it for the VM and ensure the corresponding supported guest component is available.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
They are built into supported modern Windows and updated through normal Windows servicing. Guest updates and host-side feature enablement both matter.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Run Get-VMIntegrationService -VMName 'APP01' on the Hyper-V host and inspect service status and enabled state.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
The domain's intended Windows Time hierarchy and authoritative source must be preserved. A host time setting should not unintentionally replace the forest-root PDC emulator's planned source.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
No. Check the supported distribution/kernel integration feature matrix and required components; availability differs by release and service.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
DDA passes an entire compatible PCIe device into one VM, where a native vendor driver controls it. The host and other VMs cannot share that assigned device.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Graphics adapters and NVMe storage devices. For other device classes, obtain the hardware vendor's support statement rather than assume universal support.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Server-class hardware must provide native PCIe control, ACS, and the required IOMMU isolation. Assess the specific server and device rather than infer support from the PCIe slot alone.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
It checks assignability and reports the device location path and MMIO requirements. It can explain why a device or platform is unsuitable.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Use static memory and set AutomaticStopAction to TurnOff. DDA does not support Dynamic Memory or saved-state operation.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Prepare the stopped VM, disable the device in the host, dismount it from the host partition, and then assign its PCIe location path to the VM. Install the appropriate native driver in the guest.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Assigned devices map registers and device memory into the VM address space. Allocate enough low/high MMIO for the specific devices plus appropriate overhead.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
The mitigation driver addresses assignment security on the host. The guest driver operates the assigned device; installing one does not substitute for the other.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
It bypasses the security warning about the absent mitigation driver. Assess that security decision for the device and trust boundary; it is not a performance option.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
No. Its supported Datacenter GPU-pool design can restart a VM where an available device exists after failure, but DDA live migration remains unsupported.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
It assigns hardware-isolated fractions of a supported GPU to different VMs through SR-IOV. Each VM accesses its allocated GPU resources.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Windows Server 2025 introduced it on qualifying hardware and drivers. Earlier support for some GPU functions does not imply this migration capability.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
The documented clustered design requires Windows Server 2025 Datacenter. Standalone-node planned live migration and cluster recovery are different requirements.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
IOMMU DMA bit tracking is required. Examples include AMD EPYC 7003 or later and fourth-generation Intel Xeon Scalable processors.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
EPYC 7002 supports GPU partitioning but not its live migration. EPYC 7003 or later is an example of migration-capable DMA bit-tracking hardware.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Use the driver supplied with NVIDIA vGPU Software v18.x or later, along with supported GPU hardware and required licensing.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
The partition-capable driver exists, but server SR-IOV is not enabled. Complete firmware configuration before proceeding with partition assignment.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Inspect ValidPartitionCounts with Get-VMHostPartitionableGpu and choose one of the OEM-supported values. Arbitrary partition counts are not supported.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Use compatible matching GPU make/model, capacity, and partition count across hosts. Heterogeneous GPU configurations are unsupported for this design.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Hyper-V falls back to TCP/IP with compression for migration with a GPU partition. Budget CPU and network headroom and allow for longer migrations.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
No. Choose either complete-device assignment or partitioning for that GPU; their host ownership models differ.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
It captures VM memory and device state along with disk/configuration state. Restoring it can resume old in-memory application state.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
They use supported guest VSS coordination rather than capturing live memory. Guest writers and backup integration must work.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
A production checkpoint restores consistent disk state and the VM starts from off. A standard checkpoint can resume saved memory/device state.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Production may fall back to a standard checkpoint if the production mechanism fails. ProductionOnly fails instead of taking a standard checkpoint.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
They go into a differencing child, commonly an AVHDX file, preserving the earlier parent state. The child and parent remain part of one dependency chain.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Hyper-V merges required disk changes and removes the checkpoint safely. Do not manually delete AVHDX files from the disk chain.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
It depends on the VM's storage and disk chain. Loss of that storage can remove both the current VM and all checkpoints.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Use Set-VM -Name 'APP01' -CheckpointType ProductionOnly. Verify the setting before creating the required checkpoint.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Differencing files consume storage and complicate chain/merge management. Monitor capacity, verify recovery, and remove checkpoints when their short-term purpose ends.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
The failover cluster can restart the VM on another node with accessible storage and sufficient resources. An unplanned restart does not preserve the failed host's live memory.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Place its files on supported resilient storage and add it to the prepared cluster, for example with Add-ClusterVirtualMachineRole -VMName 'APP01'.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Use supported resilient storage accessible by the eligible nodes, such as Cluster Shared Volumes or appropriate SMB 3 storage. Storage Spaces Direct can supply clustered storage in a supported design.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
The VM must find the intended compatible network attachment after migration or failover. Matching names alone still requires matching uplink, VLAN, and network design.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
It moves a running VM to another prepared host with a brief final handoff. It cannot transfer live state from a host that has already failed.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Enough CPU, startup RAM, storage access, and network capacity for the planned failure tolerance. Idle Dynamic Memory minimums do not establish failover capacity.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
It participates in quorum decisions so the cluster can maintain a valid majority. It does not store the VMs or add compute capacity.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Guest clustering protects an application through nodes inside VMs. Host clustering manages VM availability and placement at the virtualization layer.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Validation tests the intended hardware, storage, networking, and cluster configuration for compatibility. Resolve relevant failures before relying on automatic recovery.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
A fixed disk allocates its configured space up front; a dynamic disk grows its file as data is written toward its maximum. Both present a configured virtual capacity to the guest.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
It stores changes relative to a parent disk and needs that parent to interpret unchanged blocks. Protect the chain and avoid modifying its parent outside the supported workflow.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
It changes the virtual disk's capacity. Expanding the disk does not automatically extend the guest's partition or filesystem.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
It can expand VHD and VHDX, but shrink only VHDX. A shrink cannot go below the VHDX MinimumSize.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Use a supported VHDX attached to the VM's SCSI chain. An IDE-attached disk requires the VM to be offline.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Rescan if necessary and extend the partition into suitable adjacent unallocated space. The guest volume is a separate layer from VHDX capacity.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Compacting reclaims eligible unused space in the disk file. Resizing changes the virtual capacity visible to the guest; these are different operations.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Get-VHD returns properties such as virtual Size, FileSize, and MinimumSize. Use the correct property for capacity, physical file usage, or shrink limits.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
The file may consume additional real storage as the guest writes data. A large virtual maximum does not reserve or guarantee enough host disk space.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Identify the attached differencing chain and supported management operation. Manipulating a base disk alone can omit current changes or break checkpoint dependencies.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
It attaches a VM's virtual NIC to the named Hyper-V virtual switch. Guest IP configuration is a separate task.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
It associates the adapter with one VLAN. The virtual and physical switch configuration must agree with the intended network.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Use it for a suitable guest or appliance that handles multiple VLAN tags. Configure the allowed VLAN list and native VLAN deliberately.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
It blocks DHCP-server traffic from that guest. Do not enable it on an authorized VM that must serve DHCP clients.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Router Guard restricts router advertisement and redirect messages sent by the VM. It is distinct from DHCP Guard, which filters DHCP-server traffic.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
A justified appliance or nested-guest design may need traffic with source MAC addresses different from the assigned VM NIC MAC. Enable it only for the intended requirement.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Port mirroring copies traffic from configured source ports to a designated destination port. Configure the capture guest and switch relationships appropriately.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Check physical NIC, firmware, switch configuration, and guest driver support. Enabling a virtual setting cannot add missing hardware capability.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Inspect Get-VMNetworkAdapter and Get-VMNetworkAdapterVlan for the VM, then compare its intended guest IP network and physical path.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
SET integrates supported physical-NIC teaming with the Hyper-V virtual switch, providing uplink resilience and aggregate traffic distribution.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
SET operates switch-independently. It does not use LACP port-channel negotiation; configure physical switch ports for the selected design.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Use matched adapters with compatible manufacturer/model, speed, firmware, driver, and configuration. Do not build the supported design from arbitrary dissimilar uplinks.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Use New-VMSwitch -Name 'Production' -NetAdapterName 'NIC1','NIC2' -EnableEmbeddedTeaming $true. Include the appropriate management-OS sharing choice.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Get-VMSwitchTeam -Name 'Production' displays the embedded team's configuration and member information.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
No. It improves aggregate capacity and failover, but distribution algorithms and flow placement limit an individual flow's throughput.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Set-VMNetworkAdapter -VMName 'APP01' -AllowTeaming On permits the guest teaming behavior. Create the actual supported team inside Windows separately.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Two adapters sharing the same failed uplink, switch, or host have that common failure boundary. Teaming does not remove shared dependencies or survive host loss by itself.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
SET is embedded in the vSwitch and is the modern host design; LBFO is the separate older teaming mechanism. Continued LBFO cmdlet availability does not establish that an LBFO-backed vSwitch is the preferred current configuration.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
An external switch uses a physical Ethernet adapter. The uplink, VLAN, and surrounding network determine actual connectivity.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
An internal switch connects the VMs and the host's virtual adapter. It does not automatically provide routing or NAT to external networks.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
A private switch connects attached VMs to each other only. It does not create a host virtual adapter for that network.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
It allows the host management OS to share the physical uplink through a virtual adapter. It does not automatically configure every guest's addressing.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Configure the appropriate management vEthernet adapter. The physical adapter is now bound into the virtual-switch uplink design.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
No. Configure a host virtual-adapter address, a NAT object, and suitable guest addresses and gateway separately.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
It is a software Layer 2 Ethernet switch with extensible security and traffic policies. A switch alone does not supply Layer 3 routing services.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Maintain console access or another management path because uplink binding and host network changes can interrupt the current session.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
It keeps an asynchronous VM copy on another host or cluster for disaster recovery. It does not require the source and replica to share storage.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
The documented choices are 30 seconds, 5 minutes, or 15 minutes. Actual recovery-point age can worsen when replication backlog accumulates.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Kerberos uses HTTP, normally port 80, without transport encryption. Certificate-based HTTPS, normally port 443, provides encrypted transport and needs appropriate certificate trust.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
It supplies a cluster endpoint and directs replication toward the node owning the VM. The VM may change owners without requiring a fixed individual-node endpoint.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Use immediate or scheduled network transfer, external media, or a suitable existing restored initial copy. Choose based on dataset size and available bandwidth.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
It creates a temporary isolated test copy at the replica site. The primary continues operating and replication continues while recovery is validated.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Stop the primary, transfer remaining changes, and complete the coordinated role switch. A successful planned failover can avoid data loss.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
Changes not sent to the replica can be lost. Select the recovery point and prevent the old primary from becoming a competing active copy.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
The primary replicates to a replica, which replicates onward to a third host. It is not two independent direct replication targets from the primary.
Virtual machines · Virtual machines | Manage Hyper-V and guest VM
A healthy disk-replication status does not prove the recovered service can be reached or authenticated. Validate recovery-site addressing and dependency startup as well.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
Use suitable persistent managed data disks or another durable service. A size-provided temporary/resource disk is scratch storage and can lose its contents.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
An ephemeral OS disk uses local VM storage for replaceable instances. A persistent managed OS disk retains OS data independently of the host-local lifecycle.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
Ultra Disk and Premium SSD v2 are data-only choices. Check size, region, redundancy, and other compatibility requirements before selecting them.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
Bring the disk online, initialize it appropriately, create a volume, and format it inside Windows. Azure attachment alone does not make a usable filesystem.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
Increase the Azure disk capacity, then extend the guest partition/filesystem into the additional space. Follow attachment and online-expansion support for the chosen disk.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
No. To reduce required capacity, provision a suitable smaller disk and migrate data using a supported process.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
Compare the individual disk's IOPS/throughput limits with the VM's aggregate disk limits and guest workload behavior. A faster disk cannot bypass the VM ceiling.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
They do not support host caching. For other supported disk types, select cache mode according to application guidance.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
Separate snapshots do not automatically coordinate all database disks and transactions. Use an application-consistent recovery process for that requirement.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
Supported ZRS disks replicate across availability zones for disk resilience. ZRS does not automatically start another VM or create an application replica.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
It changes VM size and associated CPU, RAM, and supported resource limits. A resize normally restarts the VM and must satisfy compatibility and capacity constraints.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
Check target SKU availability, regional/family quota, placement capacity, attached disk/NIC limits, and feature compatibility. Plan restart or required deallocation.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
The target size may be unavailable on the current hardware cluster. Deallocation permits placement elsewhere and can affect temporary data and allocation-dependent resources.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
Stopped can retain host allocation and incur compute charges. Deallocated releases compute allocation; persistent disks and other resources may still incur charges.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
It adds or removes instances instead of changing one VM's size. The application must handle multiple instances and use an appropriate load-balancing/state design.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
It provides instance orchestration, scaling, health, and upgrade controls. Configure image/model, networking, initialization, and scaling behavior for the workload.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
Uniform manages scale-set-specific instances from a common VM profile. Flexible orchestrates standard Azure IaaS VMs that support standard VM management APIs.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
Define metrics or schedules, minimum and maximum capacity, scale actions, and suitable timing/cooldown behavior. Verify the workload metric and instance initialization.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
No. Design data, sessions, and consistency separately using suitable shared or replicated services; creating more instances does not copy all application state.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
It groups VMs sharing infrastructure such as a power source and network switch. Spreading instances reduces correlated infrastructure failure.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
It groups VMs and underlying hardware that can restart together during planned platform maintenance. Azure schedules maintenance across update domains rather than all at once.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
An availability set can have up to three fault domains and twenty update domains, subject to regional/platform support. Plan the counts when creating the set.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
The documented fault/update domain settings cannot be changed after the set is created. Treat them as deployment design choices.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
It is a physically separate datacenter group within a supported Azure region with distinct power, network, and cooling infrastructure.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
No. A zonal VM occupies its chosen zone. Deploy multiple workload instances across zones and provide suitable application/data failover.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
Provide load balancing or application failover, health checks, and suitable data/state handling. Placement isolation alone does not make requests switch to a healthy replica.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
Zones isolate failures within one region. A regional disaster requires a separately designed recovery path in another region.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
Availability-set VMs are closer together and can have lower inter-VM latency. Zones provide broader isolation, so assess latency alongside resilience requirements.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
JIT restricts selected management ports and temporarily permits approved source addresses for a requested window through supported NSG/firewall controls.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
Defender for Servers Plan 2 provides the feature. Confirm the supported machine and network-control prerequisites as well.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
Select management ports, permitted source addresses, and maximum access duration. Authorized requests open a time-limited network window.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
It does not create a route, VPN, guest logon account, or guest OS permission. Azure authorization to request access and guest authentication remain separate.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
Existing higher-priority broad allows can take precedence over JIT restrictions. Review effective NSG and supported firewall behavior.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
The time window closes the allowed network access configuration, but established connections are not forcibly disconnected merely by expiry.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
It connects to the VM's private IP using RDP or SSH. The target VM does not need its own public management IP.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
Standard and Premium support native SSH/RDP client connections. Verify the chosen feature and connection prerequisites rather than assume all tiers are identical.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
Premium provides these capabilities. Dedicated Basic, Standard, and Premium designs have requirements different from Developer's shared model.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
The guest must allow the relevant RDP/SSH listener and firewall traffic from the Bastion path, with valid guest authentication. Bastion does not repair a stopped guest service.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
Set static private allocation on the Azure NIC/IP configuration, then keep Windows aligned with platform provisioning. Do not only hard-code an arbitrary guest address.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
Azure reserves the first four addresses and the final address. For 10.20.0.0/24, these are .0 through .3 and .255.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
The NICs must meet the common-VNet constraints and the VM size's NIC-count limit. Use suitable subnets within that supported VNet design.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
Lower numeric priorities are evaluated first, and the first matching rule determines the decision within that NSG. Rules match source/destination, ports, and protocol.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
Both applicable NSGs must allow it, followed by guest firewall and listener requirements. An allow in one does not override a deny in the other.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
Allowed flows are tracked; response traffic does not need a separately mirrored rule for every established connection. New flows still undergo applicable rule evaluation.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
Enable IP forwarding on its Azure NIC and configure forwarding in the guest OS. Provide appropriate routes, reachable next hops, and return paths.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
No. Design explicit supported transit using appropriate gateways, routing, or appliances; two peering relationships alone are not a transit configuration.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
VMs need an explicit outbound method for public endpoints, such as a NAT Gateway or supported firewall/load-balancer/public-IP design. Existing VNets are not automatically changed by this new default.
Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
Inspect effective security rules, effective routes, Network Watcher connection diagnostics, and the guest firewall/listener. Separate route reachability from security and application acceptance.
Networking · Networking | Implement on-premises and hybrid name resolution
It is stored in AD DS, normally in a DNS application directory partition. AD replication carries its records rather than a separate zone-transfer topology between those replicas.
Networking · Networking | Implement on-premises and hybrid name resolution
Eligible domain controllers running DNS and holding the relevant directory partition can host its writable replicas. A standalone member server does not obtain that directory-backed writable role.
Networking · Networking | Implement on-premises and hybrid name resolution
An eligible writable DNS/DC replica containing the zone can accept updates. A standard file-backed primary/secondary design instead has one writable primary.
Networking · Networking | Implement on-premises and hybrid name resolution
They define domain-wide versus forest-wide DNS application-partition replication scope. Select the scope appropriate to which DNS/DC replicas should receive the data.
Networking · Networking | Implement on-premises and hybrid name resolution
AD-integrated zones support secure dynamic updates using directory security and record permissions. Ordinary nonsecure updates do not provide the same authenticated ownership control.
Networking · Networking | Implement on-premises and hybrid name resolution
The authenticating identity may lack permission or ownership of that record. Inspect the record ACL and the identity performing the update.
Networking · Networking | Implement on-premises and hybrid name resolution
A consistent authorized identity can create and maintain DHCP-managed records, including across failover partners. Mismatched identities can prevent one partner updating another's records.
Networking · Networking | Implement on-premises and hybrid name resolution
SRV records advertise services such as LDAP and Kerberos, supported by correct host records. Point domain clients to DNS resolvers that can resolve the AD namespace.
Networking · Networking | Implement on-premises and hybrid name resolution
Check zone partition/replication scope, server enrollment, and AD replication health, then distinguish replicated zone data from client/server caches.
Networking · Networking | Implement on-premises and hybrid name resolution
A primary is the writable authority for its stored zone. A secondary holds a read-only copy obtained through zone transfer from a master.
Networking · Networking | Implement on-premises and hybrid name resolution
It retains records needed to locate the zone's authority, such as SOA, NS, and necessary glue. It is not a full secondary copy of all host records.
Networking · Networking | Implement on-premises and hybrid name resolution
It supports resolving an IP address to a name, commonly using PTR records. A forward A record alone does not guarantee the corresponding reverse record exists.
Networking · Networking | Implement on-premises and hybrid name resolution
It maps a DNS name to an IPv4 address. Use AAAA for IPv6.
Networking · Networking | Implement on-premises and hybrid name resolution
It makes an alias refer to another canonical DNS name. The target still needs appropriate address resolution.
Networking · Networking | Implement on-premises and hybrid name resolution
It identifies a service's target host, port, and selection information such as priority/weight. It supports service discovery rather than replacing the target's address record.
Networking · Networking | Implement on-premises and hybrid name resolution
It directs resolution for a child namespace to that child's authoritative servers. Add required glue where the referral needs it.
Networking · Networking | Implement on-premises and hybrid name resolution
Permit only intended secondary/master participants according to the chosen design. An unrestricted transfer can expose zone data to unnecessary recipients.
Networking · Networking | Implement on-premises and hybrid name resolution
It limits how long cached answers may remain usable. Adjusting an authoritative record does not immediately purge every existing resolver cache.
Networking · Networking | Implement on-premises and hybrid name resolution
Check master addresses, zone-transfer permissions, transport/reachability, and zone serial/transfer status. Editing a read-only secondary is not the primary update workflow.
Networking · Networking | Implement on-premises and hybrid name resolution
It provides an upstream path for general recursive queries not answered locally or controlled by a more specific applicable path.
Networking · Networking | Implement on-premises and hybrid name resolution
It sends queries for a specific DNS suffix to configured target DNS servers. Other namespaces can use the normal resolver path.
Networking · Networking | Implement on-premises and hybrid name resolution
A conditional forwarder has configured query targets for a suffix. A stub holds authority-locator records learned from the zone's masters.
Networking · Networking | Implement on-premises and hybrid name resolution
No. Choose the namespace's hosted-zone or conditional-forwarder role rather than create both for the identical name.
Networking · Networking | Implement on-premises and hybrid name resolution
No. NXDOMAIN is a terminal negative answer from the applicable authority. It differs from a target timeout or retryable failure.
Networking · Networking | Implement on-premises and hybrid name resolution
They identify starting points for iterative resolution. They can be used when the resolver configuration and time budget permit that path.
Networking · Networking | Implement on-premises and hybrid name resolution
Recursion and root-hint fallback must be enabled, applicable forwarders must be exhausted, and the overall recursion timeout must not already have expired.
Networking · Networking | Implement on-premises and hybrid name resolution
Queries can circulate or time out when each target sends the same suffix back. Ensure each forwarding path terminates at the appropriate authority or resolver.
Networking · Networking | Implement on-premises and hybrid name resolution
Set-DnsServerForwarder -IPAddress '10.10.0.10','10.10.0.11' sets upstream servers. Inspect Get-DnsServerForwarder to verify the intended configuration.
Networking · Networking | Implement on-premises and hybrid name resolution
Allow the required UDP and TCP port 53 paths. TCP can be needed for large or truncated DNS responses and other DNS operations.
Networking · Networking | Implement on-premises and hybrid name resolution
It receives DNS queries at a private IP in Azure, allowing on-premises resolvers to forward Azure-private namespaces through private connectivity.
Networking · Networking | Implement on-premises and hybrid name resolution
It forwards matching queries toward target DNS servers through a configured forwarding ruleset. Ruleset links determine which VNets use that path.
Networking · Networking | Implement on-premises and hybrid name resolution
Create the appropriate virtual-network link to the private zone. Peering alone does not automatically link every private zone.
Networking · Networking | Implement on-premises and hybrid name resolution
Use dedicated endpoint subnets delegated to Microsoft.Network/dnsResolvers and meeting current endpoint requirements. Do not treat them as general VM subnets.
Networking · Networking | Implement on-premises and hybrid name resolution
Provide a routed VPN or ExpressRoute path with return routes and DNS transport permitted. Private Resolver does not create that network connection.
Networking · Networking | Implement on-premises and hybrid name resolution
Configure a conditional forwarder for the appropriate suffix pointing to the inbound endpoint's private IP. Link the authoritative Azure private zone to the resolver VNet.
Networking · Networking | Implement on-premises and hybrid name resolution
Create a forwarding rule targeting the on-premises DNS servers, associate the outbound endpoint, and link the ruleset to the intended client VNets.
Networking · Networking | Implement on-premises and hybrid name resolution
Clients query their configured custom DNS servers. Those servers must implement the required forwarding path; a linked ruleset does not silently replace the custom server configuration.
Networking · Networking | Implement on-premises and hybrid name resolution
No. Azure's special resolver address is used within its supported Azure context. Use an inbound resolver endpoint or a suitable Azure DNS-forwarding VM for on-premises queries.
Networking · Networking | Implement on-premises and hybrid name resolution
Check the service's correct Private Link DNS suffix, private records and VNet links, on-premises conditional forwarding, and the actual resolver the client uses.
Networking · Networking | Implement on-premises and hybrid name resolution
Routing, security rules, guest/application listening, and authorization still require verification. A DNS answer alone does not prove service connectivity.
Networking · Networking | Implement on-premises and hybrid name resolution
It is a distinct record set within one zone. The same name can have different addresses in different scopes.
Networking · Networking | Implement on-premises and hybrid name resolution
It contains recursion behavior and forwarder settings. Policies can select it for queries that require recursive resolution.
Networking · Networking | Implement on-premises and hybrid name resolution
It names an IPv4/IPv6 subnet criterion that policies can match. The authoritative server must see source information that matches the intended criterion.
Networking · Networking | Implement on-premises and hybrid name resolution
Create different scoped records for the same name and select the appropriate scope using criteria such as client subnet or server interface.
Networking · Networking | Implement on-premises and hybrid name resolution
They can match client subnet, queried name/type, server interface, transport or IP protocol, and time-of-day conditions. Configure applicable policy scope and order deliberately.
Networking · Networking | Implement on-premises and hybrid name resolution
DENY rejects the matching query, while IGNORE drops it without a normal answer. IGNORE can therefore appear to a client as a timeout.
Networking · Networking | Implement on-premises and hybrid name resolution
No. Scoped zone data can replicate, but policy definitions are local to each DNS server. Configure policies on every server that must apply them.
Networking · Networking | Implement on-premises and hybrid name resolution
The default scope supports these functions. Nondefault scopes require their own record-management plan.
Networking · Networking | Implement on-premises and hybrid name resolution
DNS replies are cached and policy weights distribute answers rather than probe each application instance. Cached clients may continue using a failed target.
Networking · Networking | Implement on-premises and hybrid name resolution
Create the scope and its required resource records, plus any named client-subnet criteria. Then configure the policy and test matching and default behavior.
Networking · Networking | Implement on-premises and hybrid name resolution
It provides authenticated origin, data integrity, and authenticated denial of existence for DNS data. It does not encrypt DNS queries or application traffic.
Networking · Networking | Implement on-premises and hybrid name resolution
DNSSEC validates signed answers. Secure dynamic updates authorize changes to zone records; the two protect different stages of DNS operation.
Networking · Networking | Implement on-premises and hybrid name resolution
It contains a digital signature for a DNS resource-record set. A validator checks it against the appropriate public key and trust chain.
Networking · Networking | Implement on-premises and hybrid name resolution
It publishes a zone's public signing key. Possessing a key alone is not enough unless the validator trusts it through an anchor or authenticated chain.
Networking · Networking | Implement on-premises and hybrid name resolution
A parent-zone DS links the child to the authenticated delegation chain. Signing a child does not automatically install the needed DS in its parent.
Networking · Networking | Implement on-premises and hybrid name resolution
The zone-signing key signs ordinary record sets; the key-signing key signs the DNSKEY set. Plan rollover and signature validity for each.
Networking · Networking | Implement on-premises and hybrid name resolution
They support authenticated denial of existence. NSEC3 uses hashed names but is not general encryption or complete confidentiality.
Networking · Networking | Implement on-premises and hybrid name resolution
It needs a configured trust anchor or an authenticated chain from a trusted parent. Unsigned or broken delegation data can prevent required validation.
Networking · Networking | Implement on-premises and hybrid name resolution
Configure a suitable NRPT rule, commonly through Group Policy, with DNSSEC enabled and validation required. Check the effective client policy.
Networking · Networking | Implement on-premises and hybrid name resolution
No. It requests DNSSEC data; receiving signatures is different from validating them through a trusted chain and enforcing the required policy.
Networking · Networking | Implement on-premises and hybrid name resolution
Check trust anchors, DS/DNSKEY chain, signature validity and rollover, system time, effective NRPT, and DNS transport handling.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
Discover, Offer, Request, Acknowledge, commonly called DORA. The exchange obtains an address lease and configuration.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
Clients use UDP 68 and servers use UDP 67. Permit the required client, relay, and server paths.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
Configure a suitable static IPv4 address for the server before deploying the role. It needs a stable reachable endpoint.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
Install-WindowsFeature -Name DHCP -IncludeManagementTools installs the role/tools. Authorization and usable scopes are configured separately.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
Authorization registers the permitted DHCP server in AD for the Windows DHCP service's domain checks. It is not a physical network block against every rogue device.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
Add-DhcpServerInDC registers the server's DNS name and address. Get-DhcpServerInDC lists authorized servers.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
Initial client broadcasts normally do not cross routers. The relay forwards requests and supplies subnet context so the server can select the correct scope.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
The service must be ready and authorized where required, bound to the intended interface, and have an active scope with free addresses and correct options.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
No. Azure's platform supplies supported primary NIC addressing; configure Azure NIC allocation appropriately. On-premises broadcast/relay behavior is a separate design.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
Inspect address, subnet mask, gateway, DNS servers, DHCP server, and lease details. Compare them with the intended network before changing configuration.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
The client did not obtain a usable DHCP lease and selected link-local addressing. The address alone does not identify whether the server, relay, path, or client failed.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
The client may consider a remote destination local and ARP for it instead of using the gateway. Verify prefix/mask as well as the IP address.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
Same-subnet communication works but remote destinations fail by IP. Verify gateway, routes, firewall behavior, and return paths before focusing on DNS.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
The required destination succeeds by IP but fails by its expected name. Verify the actual resolver and record path, then test the application with its required hostname.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
Overlapping prefixes create ambiguous or unsupported routing relationships in the intended VPN/peering design. Plan distinct prefixes and valid return routes.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
It evaluates specified TCP/UDP traffic against applicable NSG and security-admin rules, returning allowed/denied and the matching rule. It does not prove the guest application is listening.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
ICMP may be blocked while the application's TCP port works. Test the required destination and port and inspect the applicable security path.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
The remote network may lack a return route, or a stateful firewall/appliance path may be asymmetric. Check both directions rather than only the outbound route.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
It defines a subnet lease range, mask, exclusions, lease duration, and options. The range must fit the intended subnet and available addressing plan.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
It prevents listed pool addresses from being offered dynamically, commonly protecting infrastructure addresses assigned statically.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
Activate the scope and verify service/authorization, reachability, and free-address capacity. A saved inactive scope does not offer normal leases.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
It supplies the client's router/default gateway. Set it to the appropriate gateway for that scope's subnet.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
It supplies DNS server addresses. Domain clients should receive resolvers able to locate the AD namespace.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
It supplies the DNS domain/suffix used by clients. It does not replace DNS server addresses or a default gateway.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
It groups scopes for a multinet arrangement on one physical network. It does not create VLANs, routing, or new physical broadcast domains.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
Shorter leases can free unused addresses sooner but cause more renewal traffic. Choose duration from client turnover, capacity, and operational needs.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
More specific scope, policy, or reservation settings may override inherited values. Verify what the affected client actually receives.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
It associates a selected scope address with a particular client identifier, commonly the NIC's MAC address. The server leases that address to the matching client.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
A reserved device remains a DHCP client and obtains a lease and options from DHCP. A manual static address is configured locally without that lease-selection process.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
It must use DHCP and send the matching identifier. A device configured only with a manual static IP does not request the reserved lease.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
Add-DhcpServerv4Reservation uses ScopeId, IPAddress, and ClientId to reserve an address. Use the identifier actually presented by the client.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
Inspect the actual client/lease identifier rather than guess from a label or another adapter. The request must match the configured identifier.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
The client may present a different MAC/client identifier. Update the reservation deliberately after verifying the new identifier.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
A changing client identifier may no longer match the intended reservation. Use a supported stable identifier/configuration for clients needing predictable leased addresses.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
No. The reserved device still depends on DHCP for lease acquisition and renewal; an already valid lease can remain usable until its limits require renewal.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
Replicate the changed scope configuration from the intended source to the partner. Lease synchronization alone does not guarantee the partner received a new reservation setting.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
Two DHCP servers participate in that scope's failover relationship. A server can have other relationships, but one scope cannot have three failover partners.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
The described failover protocol supports DHCPv4 scopes. DHCPv6 availability requires a different supported design.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
Both partners normally serve clients according to the configured distribution ratio, commonly 50:50. They synchronize lease information.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
One partner normally serves the scope; the other is standby with a reserve for the appropriate failure behavior. It suits local service backed by another site.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
MCLT limits lease extension beyond information known to the partner and supports safe takeover timing. It helps prevent duplicate address assignment during disrupted communication.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
The server-to-server connection failed, but the partner may still serve clients. Follow safe lease-ownership rules and verify failure before forcing Partner Down.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
The appropriate Partner Down state and required MCLT waiting behavior permit safe use of the full pool. A lost link alone does not authorize immediate unsafe reuse.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
TCP 647 carries failover messages. DHCP client/relay UDP paths must also remain available to both partners.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
The configured source scopes are created on the partner as part of relationship setup. Start from the intended source rather than conflicting independently configured full scopes.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
No. Replicate configuration changes explicitly from the intended source to the partner, for example using Invoke-DhcpServerv4FailoverReplication.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
Clients must reach the surviving server as well as the normal one. Healthy partner synchronization cannot compensate for a relay pointing only to a failed endpoint.
Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
Keep partner clocks synchronized and use matching authorized DNS-update credentials when they update secure DNS. Otherwise setup/state or record updates can fail.
Storage and file services · Storage and file services | Configure and manage Azure Files
SMB and NFS. Select a supported protocol, media tier, billing model, region and redundancy for the workload; one share is not simultaneously an SMB and NFS share.
Storage and file services · Storage and file services | Configure and manage Azure Files
Direct clients mount a cloud file share. File Sync synchronizes that share with Windows Server endpoints that provide local access and optional caching.
Storage and file services · Storage and file services | Configure and manage Azure Files
TCP 445. A private endpoint or VPN changes the network path but does not change the SMB port.
Storage and file services · Storage and file services | Configure and manage Azure Files
The storage account file endpoint name must resolve through the private-link DNS design to the intended private IP. Correct routing and storage firewall access are also required.
Storage and file services · Storage and file services | Configure and manage Azure Files
An availability-zone failure within the primary region. Geo-redundancy additionally replicates asynchronously to another region and can lose recent writes during failover.
Storage and file services · Storage and file services | Configure and manage Azure Files
No. Create a supported SSD share and migrate the data; changing access tier within an eligible HDD billing model is a different operation.
Storage and file services · Storage and file services | Configure and manage Azure Files
A point-in-time read-only view useful for recovery. It does not replace a planned retention, backup and disaster-recovery strategy.
Storage and file services · Storage and file services | Configure and manage Azure Files
No. Azure Files does not expose read access to the secondary; RA-GRS file shares are treated and billed as geo-redundant shares.
Storage and file services · Storage and file services | Configure and manage Azure Files
AD DS, Microsoft Entra Domain Services, or Microsoft Entra Kerberos. Only one user identity source can be enabled per storage account.
Storage and file services · Storage and file services | Configure and manage Azure Files
Share-level permission and directory/file Windows ACLs. A grant at one layer does not normally remove restrictions at the other.
Storage and file services · Storage and file services | Configure and manage Azure Files
No. Management-plane resource rights differ from data-plane share roles and file ACLs. Assign appropriate data access explicitly.
Storage and file services · Storage and file services | Configure and manage Azure Files
Read access at the share gate, further limited by file and directory ACLs. It cannot grant writes even if a file ACL allows them.
Storage and file services · Storage and file services | Configure and manage Azure Files
It adds permission modification to normal read/write/delete capabilities at the share gate. Appropriate file ACL authority remains required; it is not the privileged ACL-bypass role.
Storage and file services · Storage and file services | Configure and manage Azure Files
All authenticated users of the configured identity source and all shares in the storage account. It is broad and must be combined with carefully scoped file ACLs.
Storage and file services · Storage and file services | Configure and manage Azure Files
No. Entra issues Kerberos tickets; hybrid identities still need AD DS connectivity for Windows ACL administration. Current support includes eligible updated cloud-only Windows clients.
Storage and file services · Storage and file services | Configure and manage Azure Files
Use supported cloud-only ACL management such as the Azure portal or RestSetAcls. Do not assume ordinary on-premises AD SID lookup supplies cloud-only identities.
Storage and file services · Storage and file services | Configure and manage Azure Files
Keys provide broad shared access rather than individual identity-based permissions. Kerberos and scoped data roles/ACLs provide more suitable user access controls.
Storage and file services · Storage and file services | Configure and manage Azure Files
One Azure Files cloud endpoint and one or more Windows Server endpoints sharing a synchronized namespace.
Storage and file services · Storage and file services | Configure and manage Azure Files
A path on a registered supported Windows Server NTFS volume. It is not simply an arbitrary network SMB share.
Storage and file services · Storage and file services | Configure and manage Azure Files
HTTPS over TCP 443. Local clients can still access the server endpoint using SMB; those are separate connections.
Storage and file services · Storage and file services | Configure and manage Azure Files
Cold content can be replaced locally by placeholders while the full dataset remains in Azure Files. Reading tiered data triggers recall.
Storage and file services · Storage and file services | Configure and manage Azure Files
The service aims to keep 20 percent of the volume free. It does not mean retain 20 percent of the dataset locally.
Storage and file services · Storage and file services | Configure and manage Azure Files
The volume free-space policy takes precedence over the optional date policy. Policy evaluation is periodic.
Storage and file services · Storage and file services | Configure and manage Azure Files
Fully cached local content remains readable. Tiered content requiring recall needs Azure connectivity.
Storage and file services · Storage and file services | Configure and manage Azure Files
Back up the Azure file share, or a fully hydrated supported endpoint without tiered files. Ordinary placeholder backups can skip content or cause mass recall.
Storage and file services · Storage and file services | Configure and manage Azure Files
Cloud changes first require change detection; the documented regular cloud change-detection job runs once every 24 hours.
Storage and file services · Storage and file services | Configure and manage Azure Files
It communicates with the service. It does not prove every endpoint or file has synchronized successfully.
Storage and file services · Storage and file services | Configure and manage Azure Files
Telemetry event 9102 records completed sessions. Correlate endpoint, timestamps, result and persistent per-file errors.
Storage and file services · Storage and file services | Configure and manage Azure Files
Event 9302 shows active-session progress. Compare applied-item counts over time rather than treating a long session as automatically stuck.
Storage and file services · Storage and file services | Configure and manage Azure Files
Event 9121. Use its filename and error details to investigate individual files that failed while other files synchronized.
Storage and file services · Storage and file services | Configure and manage Azure Files
Event Viewer under Applications and Services Logs, Microsoft, FileSync, Agent. Use the telemetry channels relevant to the symptom.
Storage and file services · Storage and file services | Configure and manage Azure Files
AFS Bytes Transferred and AFS Sync Operations in Performance Monitor. Compare them with session events and workload demand.
Storage and file services · Storage and file services | Configure and manage Azure Files
A scanner, indexer, backup, or changed working set may be recalling cold files. Correlate the timing with local processes and cache policy.
Storage and file services · Storage and file services | Configure and manage Azure Files
Offline registered servers, files not syncing, unsuccessful sessions, low disk-space mode, agent expiry and abnormal recalls. Configure endpoint dimensions and action groups.
Storage and file services · Storage and file services | Configure and manage Azure Files
DFS Namespaces can retain the stable user path. File Sync replaces replication; it does not replace namespace referrals.
Storage and file services · Storage and file services | Configure and manage Azure Files
Confirm that it has the complete, healthy intended dataset, appropriate ACLs, and supported local storage.
Storage and file services · Storage and file services | Configure and manage Azure Files
Start with tiering disabled and let the complete cloud upload finish before later tiering enablement.
Storage and file services · Storage and file services | Configure and manage Azure Files
After the first dataset upload and server registration, disable DFS-R as prescribed, then create the remaining endpoints with tiering disabled.
Storage and file services · Storage and file services | Configure and manage Azure Files
Two replication systems acting on the same tree can conflict. Follow the documented transition instead of leaving multiple active overlapped locations.
Storage and file services · Storage and file services | Configure and manage Azure Files
No. Do not use the read-only DFS-R folder as an Azure File Sync endpoint.
Storage and file services · Storage and file services | Configure and manage Azure Files
DFS namespace targets, SMB share permissions, user mappings and backup policies need explicit validation or update.
Storage and file services · Storage and file services | Configure and manage Azure Files
The retired source no longer contains those writes. Switching referrals back without copying accepted changes can lose user work.
Storage and file services · Storage and file services | Configure and manage Azure Files
Measure capacity, file count, churn, paths, ACLs, unsupported metadata, open-file behavior and performance requirements.
Storage and file services · Storage and file services | Configure and manage Azure Files
Use direct migration when users will access Azure Files without retaining a Windows Server cache. File Sync fits retained local SMB/cache needs.
Storage and file services · Storage and file services | Configure and manage Azure Files
No. Recreate or redirect share access, namespace targets, mapped drives and backup policies separately.
Storage and file services · Storage and file services | Configure and manage Azure Files
/COPYALL requests data, attributes, timestamps, security ACLs, ownership and auditing (/COPY:DATSOU). For Azure Files, the documented migration command uses /COPY:DATSO; do not assume auditing information or every NTFS feature is preserved.
Storage and file services · Storage and file services | Configure and manage Azure Files
It mirrors and deletes target entries missing from the source. Review target ownership and deletion impact before using it.
Storage and file services · Storage and file services | Configure and manage Azure Files
They are bitmasks. Values below 8 can indicate successful copying with differences; 8 or higher indicates at least one failure to investigate.
Storage and file services · Storage and file services | Configure and manage Azure Files
Perform an initial copy and incremental passes, freeze source writes, finish the final delta, validate and redirect clients.
Storage and file services · Storage and file services | Configure and manage Azure Files
Sample contents, supported metadata, effective ordinary-user access, application workflows, performance and recovery configuration.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
Both the SMB share permissions and filesystem ACLs. Local file access does not traverse the share permission gate.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
It hides entries users cannot enumerate. It does not replace the underlying file permissions or grant access.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
New-SmbShare exposes an existing directory and can configure share permissions and properties. Set the directory ACL separately.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
Get-SmbShareAccess. Compare its results with the directory ACL when diagnosing effective access.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
It requires encryption for access to that share. Confirm the client supports the necessary SMB encryption capability.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
No. It hides the share from normal browsing, while explicit UNC access still depends on authentication and permissions.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
Get-SmbOpenFile identifies open handles and their clients. Use it to distinguish locks from permission denial.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
Disk redundancy does not recover the file server service or host. Use a supported clustered file-server architecture for service availability.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
NTFS. FSRM does not support ReFS volumes.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
FSRM limits the folder tree regardless of file owner. NTFS disk quotas measure usage by user on a volume.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
It blocks growth beyond its configured limit. Threshold notifications can warn before enforcement occurs.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
It measures and can notify when thresholds are reached but does not block writes beyond the limit.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
It automatically creates template-based quotas on existing and newly created subfolders, such as home directories.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
Active screening blocks configured file-name patterns. Passive screening records/notifies without preventing the write.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
It matches filename patterns rather than proving file content or safety. Renaming a file can bypass simple extension matching.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
They classify files using configured properties/rules and perform conditional actions such as an approved expiration workflow. They do not replace access ACLs.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
A stable logical UNC path and referrals to underlying SMB folder targets. It does not itself copy the targets files.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
In AD DS. Multiple namespace servers can improve root availability; the data targets need their own availability design.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
An underlying UNC share location that can serve a namespace folder. Validate direct share access and content before adding interchangeable targets.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
DFS referrals are cached. Check the client referral cache and refresh behavior as well as the namespace configuration.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
DFS-R asynchronously synchronizes replicated folders; DFS-N routes users to folder targets. Either role can exist without the other.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
It identifies changed portions of files to reduce transfer. It is not distributed file locking or a mechanism that merges conflicting edits.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
Its content seeds initial replication. It is not a permanent single writer after initialization.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
DFS-R cannot replicate a file while it remains open and does not provide application-level transactional consistency.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
NTFS. It relies on NTFS capabilities such as the change journal and does not support ReFS replicated folders.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
A TLS 1.3 encrypted QUIC tunnel over UDP 443. SMB authorization still applies inside the tunnel.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
Server 2022 requires Datacenter: Azure Edition. Server 2025 or later supports any edition; Windows 11 is the standard client.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
No. An administrator must opt in and configure a suitable server certificate mapping.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
DNS subject alternative names must match the names clients use. The trusted server certificate also requires a private key and Server Authentication usage.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
Use New-SmbMapping -TransportType QUIC or NET USE /TRANSPORT:QUIC. Otherwise clients normally attempt TCP before QUIC.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
Use PowerShell server certificate mapping cmdlets. The documented Windows Admin Center configuration method is not currently supported for Server 2025.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
Renewal changes the certificate thumbprint. Update the server certificate mapping to the new valid certificate.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
Device admission based on trusted client certificates and allow/deny rules. Passing admission does not grant the user share or file access.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
Any deny for a checked certificate in the client chain takes priority over an allow. Access entries identify certificate hashes with SHA-256.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
Signing protects message integrity and authenticity. Encryption additionally protects data confidentiality in transit; signing alone does not hide file content.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
EncryptData. Server/client-wide encryption policies are a separate scope and must be supported by the peers.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
The highest mutually supported allowed dialect. Policy restrictions and peer capabilities determine whether a connection can be established.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
Get-SmbClientConfiguration and Get-SmbServerConfiguration. Get-SmbConnection displays negotiated active client connections.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
SMB Multichannel. Disabling it prevents SMB Direct even when RDMA adapters are installed.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
It protects the negotiation and session-setup exchange against tampering. It does not replace later content encryption.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
Outbound SMB signing is required by default. Inspect effective settings and distinguish it from Windows 11 24H2 client-edition defaults.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
The normal Kerberos service-name path may not be used. Correct DNS/SPN naming rather than treating IP connectivity as authentication proof.
Storage and file services · Storage and file services | Configure and manage Windows Server file shares
For sufficiently compressible data and a suitable CPU/network tradeoff. Already compressed content can offer little benefit.
Storage and file services · Storage and file services | Configure Windows Server storage
Identify the disk, bring it online as appropriate, initialize, partition, format and assign a drive letter or mount point. A share is optional and separate.
Storage and file services · Storage and file services | Configure Windows Server storage
GPT supports large disks and many partitions. MBR has a roughly 2-TiB addressability limit with conventional sector sizes.
Storage and file services · Storage and file services | Configure Windows Server storage
Check disk number together with unique ID or serial number, capacity and existing partition state. Disk numbering alone can change.
Storage and file services · Storage and file services | Configure Windows Server storage
A volume attached under an empty NTFS directory instead of a drive letter. It helps organize many volumes without consuming letters.
Storage and file services · Storage and file services | Configure Windows Server storage
The underlying physical/virtual disk or LUN must expose additional capacity. Then extend the supported partition/filesystem into usable free space.
Storage and file services · Storage and file services | Configure Windows Server storage
Its backing pool may have exhausted physical capacity. Monitor pool free space separately from filesystem free space.
Storage and file services · Storage and file services | Configure Windows Server storage
Ownership or SAN policy may intentionally keep it offline. Verify cluster ownership and disk identity before changing state.
Storage and file services · Storage and file services | Configure Windows Server storage
ReFS cannot be shrunk. NTFS supports shrinking subject to supported layout and immovable-data constraints.
Storage and file services · Storage and file services | Configure Windows Server storage
A pool groups eligible physical capacity. A virtual disk consumes that capacity with a chosen layout; Windows then partitions and formats it.
Storage and file services · Storage and file services | Configure Windows Server storage
Simple layout stripes data without protection. It is suitable only when loss is acceptable or the data is reproducible.
Storage and file services · Storage and file services | Configure Windows Server storage
It stores two copies, so usable capacity is roughly half raw capacity before metadata and repair headroom. Placement must support the intended failure tolerance.
Storage and file services · Storage and file services | Configure Windows Server storage
Capacity-sensitive, predominantly read or archive workloads. Parity generally has greater write overhead than mirroring.
Storage and file services · Storage and file services | Configure Windows Server storage
Fixed provisioning allocates backing capacity up front. Thin provisioning allocates as data grows and requires independent monitoring of real pool capacity.
Storage and file services · Storage and file services | Configure Windows Server storage
Get-PhysicalDisk, Get-StoragePool and Get-VirtualDisk show device, pool and virtual-disk state. Get-StorageJob shows repairs.
Storage and file services · Storage and file services | Configure Windows Server storage
Columns, resiliency and placement requirements determine usable allocation. Total raw free capacity alone does not prove a supported expansion is possible.
Storage and file services · Storage and file services | Configure Windows Server storage
Confirm repair-job completion and restored virtual-disk resiliency, not merely that the filesystem is mounted. Retain independent backups.
Storage and file services · Storage and file services | Configure Windows Server storage
Eligible directly attached drives across failover-cluster nodes, using a software storage bus. It differs from a conventional shared SAN.
Storage and file services · Storage and file services | Configure Windows Server storage
Windows Server Datacenter. Azure Local is a separately managed related solution, not simply the same licensing and deployment model.
Storage and file services · Storage and file services | Configure Windows Server storage
Hyperconverged nodes run Hyper-V and storage together. Disaggregated storage nodes provide Scale-Out File Server shares to separate compute hosts.
Storage and file services · Storage and file services | Configure Windows Server storage
High-bandwidth, low-latency networking with at least 10-GbE. RDMA is recommended and needs compatible adapters, drivers and network configuration.
Storage and file services · Storage and file services | Configure Windows Server storage
It checks hardware, storage, network and system suitability, including S2D tests. A successful role installation does not establish a supported cluster.
Storage and file services · Storage and file services | Configure Windows Server storage
It enables the clustered storage system, discovers eligible drives and configures the pool/cache and storage tiers.
Storage and file services · Storage and file services | Configure Windows Server storage
They give clustered Hyper-V hosts supported access to shared storage volumes for VM files, coordinated by the cluster.
Storage and file services · Storage and file services | Configure Windows Server storage
Data resiliency and cluster voting are different. Enough data copies do not ensure the cluster can remain operational after node failures.
Storage and file services · Storage and file services | Configure Windows Server storage
Current faults, repair jobs, fault-domain protection, capacity and quorum. Drain workloads and follow supported storage maintenance procedures.
Storage and file services · Storage and file services | Configure Windows Server storage
Volume blocks, below the file layer. It can replicate open-file changes but provides crash consistency rather than automatic application-transaction consistency.
Storage and file services · Storage and file services | Configure Windows Server storage
After the remote replication log durably records it. This protects acknowledged writes when the remote destination survives but adds round-trip latency.
Storage and file services · Storage and file services | Configure Windows Server storage
It acknowledges locally before remote confirmation, allowing higher latency/distance while recent unreplicated writes can be lost.
Storage and file services · Storage and file services | Configure Windows Server storage
Server-to-server, cluster-to-cluster and stretched cluster. Application failover design is separate from the replication partnership.
Storage and file services · Storage and file services | Configure Windows Server storage
The replication logs are part of the write path and require suitable performance and capacity. They should not host unrelated workloads.
Storage and file services · Storage and file services | Configure Windows Server storage
The proposed workload, storage, bandwidth and latency for replication. Use its report before committing to a partnership.
Storage and file services · Storage and file services | Configure Windows Server storage
One replicated volume up to 2 TB. Datacenter removes those edition limits.
Storage and file services · Storage and file services | Configure Windows Server storage
No. Direct ordinary access would conflict with incoming block changes; supported test-failover snapshots are a separate capability.
Storage and file services · Storage and file services | Configure Windows Server storage
Replication also copies deletions, corruptions and malicious writes. Retained recovery points protect against those changes.
Storage and file services · Storage and file services | Configure Windows Server storage
It stores repeated data chunks once and replaces duplicate ranges with references, while applications normally see their original logical files.
Storage and file services · Storage and file services | Configure Windows Server storage
The volume becomes eligible for scheduled/background optimization. Existing files are not instantly all optimized.
Storage and file services · Storage and file services | Configure Windows Server storage
Workload-specific defaults for optimization behavior. Select a supported workload and evaluate suitability rather than assuming all VM/database files qualify.
Storage and file services · Storage and file services | Configure Windows Server storage
Chunks no longer referenced by optimized files. It differs from optimization, which finds and consolidates repeated content.
Storage and file services · Storage and file services | Configure Windows Server storage
It checks chunk-store integrity and attempts supported repair. Monitor its results rather than equating savings with integrity.
Storage and file services · Storage and file services | Configure Windows Server storage
No. Use a supported unoptimization workflow with adequate free capacity to expand optimized data.
Storage and file services · Storage and file services | Configure Windows Server storage
Windows Server 2019, in supported configurations. FSRM and DFS-R still independently require NTFS.
Storage and file services · Storage and file services | Configure Windows Server storage
No. Optimization changes physical representation rather than logical file content; DFS-R uses its own RDC transfer mechanism.
Storage and file services · Storage and file services | Configure Windows Server storage
File age, exclusions, job completion, resource limits and data characteristics. Already compressed or encrypted content often yields low savings.
Storage and file services · Storage and file services | Configure Windows Server storage
Remote Direct Memory Access on suitable network adapters, providing high throughput with low latency and reduced CPU overhead.
Storage and file services · Storage and file services | Configure Windows Server storage
SMB Multichannel. Without it, SMB uses TCP even if the adapters support RDMA.
Storage and file services · Storage and file services | Configure Windows Server storage
Both client and server need compatible enabled RDMA adapters, drivers and network paths.
Storage and file services · Storage and file services | Configure Windows Server storage
No. Ordinary guest virtual adapters do not automatically expose the host adapter RDMA capability.
Storage and file services · Storage and file services | Configure Windows Server storage
Get-NetAdapterRdma. Combine it with SMB interface and multichannel connection checks while traffic is active.
Storage and file services · Storage and file services | Configure Windows Server storage
SMB Direct Connection Bytes RDMA Read/sec and Bytes RDMA Written/sec. Adapter capability alone does not prove traffic uses RDMA.
Storage and file services · Storage and file services | Configure Windows Server storage
Encryption supports direct data placement with modest performance overhead. Earlier encryption performance limitations must not be applied universally.
Storage and file services · Storage and file services | Configure Windows Server storage
Multichannel, enabled RDMA, adapter/driver support, selected interfaces, routing and RDMA-type-specific network configuration.
Storage and file services · Storage and file services | Configure Windows Server storage
Storage performance goals and limits for VM VHD/VHDX flows on supported Hyper-V CSV or Scale-Out File Server storage.
Storage and file services · Storage and file services | Configure Windows Server storage
A ceiling on normalized IOPS for the assigned policy scope. It can constrain a noisy workload.
Storage and file services · Storage and file services | Configure Windows Server storage
Actual workload demand and available storage capacity. A reservation cannot create physical throughput that the storage system lacks.
Storage and file services · Storage and file services | Configure Windows Server storage
One allocation of IOPS and bandwidth among all assigned flows. It is useful for a tenant or multi-VM application budget.
Storage and file services · Storage and file services | Configure Windows Server storage
Independent allocations for assigned VM/disk groupings rather than one cross-tenant shared allocation. Multiple disks with the same policy on one VM can share its allocation.
Storage and file services · Storage and file services | Configure Windows Server storage
32 normalized operations. Normalized IOPS therefore differs from raw request count for large I/O.
Storage and file services · Storage and file services | Configure Windows Server storage
Set the disk QoSPolicyID using the storage cluster policy GUID, such as with Set-VMHardDiskDrive.
Storage and file services · Storage and file services | Configure Windows Server storage
A flow demands its assigned minimum but storage cannot satisfy it. Investigate contention and physical limits rather than increasing the minimum blindly.
Storage and file services · Storage and file services | Configure Windows Server storage
The referenced policy GUID may not exist on the destination storage cluster. Recreate or reassign a suitable destination policy.
Storage and file services · Storage and file services | Configure Windows Server storage
NTFS. ReFS is not supported as a bootable Windows filesystem.
Storage and file services · Storage and file services | Configure Windows Server storage
It checksums metadata and can use optional integrity streams for file data. File-data checksumming is not automatically implied for every file.
Storage and file services · Storage and file services | Configure Windows Server storage
A healthy alternate copy in a supported resilient storage configuration, such as mirrored or parity Storage Spaces. Detection alone cannot recreate missing data.
Storage and file services · Storage and file services | Configure Windows Server storage
Supported file-range copy operations by sharing existing blocks instead of duplicating all data immediately; virtualization and backup tools can benefit.
Storage and file services · Storage and file services | Configure Windows Server storage
NTFS. Those services have their own filesystem requirements; ReFS integrity features do not remove them.
Storage and file services · Storage and file services | Configure Windows Server storage
NTFS. Current ReFS does not support built-in disk quotas or shrinking.
Storage and file services · Storage and file services | Configure Windows Server storage
Yes. Volume encryption is distinct from the filesystem feature differences.
Storage and file services · Storage and file services | Configure Windows Server storage
Current documentation adds ReFS EFS support on Windows Server 2025. Do not assume that support applies to older Server releases.
Storage and file services · Storage and file services | Configure Windows Server storage
The host must support the volume ReFS format version and workload. Newer format features are not automatically readable on older releases.
Storage and file services · Storage and file services | Configure Windows Server storage
Block storage using SCSI commands over TCP, normally port 3260. The resulting LUN appears as a disk rather than an SMB directory.
Storage and file services · Storage and file services | Configure Windows Server storage
The initiator consumes storage; the target presents LUNs/virtual disks and authorizes intended initiators.
Storage and file services · Storage and file services | Configure Windows Server storage
It identifies an initiator or target for discovery/authorization. The identifier itself is not a secret credential.
Storage and file services · Storage and file services | Configure Windows Server storage
No. CHAP authenticates peers; protected networks or supported IPsec designs provide transport confidentiality.
Storage and file services · Storage and file services | Configure Windows Server storage
Reconnect to the target after restart. Confirm the initiator service and saved session settings before relying on boot-time storage.
Storage and file services · Storage and file services | Configure Windows Server storage
Coordinated multiple independent paths to the same storage device. Additional uncoordinated sessions are not equivalent to a configured multipath design.
Storage and file services · Storage and file services | Configure Windows Server storage
Not without a supported clustering/application ownership design. Concurrent uncoordinated filesystem ownership risks corruption.
Storage and file services · Storage and file services | Configure Windows Server storage
TCP reachability, target mapping, initiator authorization, MPIO paths, driver/firmware health and iScsiPrt/Disk/StorPort events on host and array.
Storage and file services · Storage and file services | Configure Windows Server storage
A volume data at rest. It does not replace file ACLs or SMB encryption after the volume is unlocked.
Storage and file services · Storage and file services | Configure Windows Server storage
Expected boot integrity measurements. Firmware, Secure Boot or boot-configuration changes can cause recovery.
Storage and file services · Storage and file services | Configure Windows Server storage
A lost protector or changed boot state can otherwise make data inaccessible. Verify authorized retrieval, not only successful encryption.
Storage and file services · Storage and file services | Configure Windows Server storage
A new sanitized volume, because it encrypts allocated data as it is written. A reused volume can contain recoverable old plaintext in unused sectors.
Storage and file services · Storage and file services | Configure Windows Server storage
Suspension temporarily changes protector enforcement while data remains encrypted. Decryption converts the volume back to plaintext.
Storage and file services · Storage and file services | Configure Windows Server storage
Get-BitLockerVolume. Distinguish conversion status, protection status and protector identifiers.
Storage and file services · Storage and file services | Configure Windows Server storage
Backup-BitLockerKeyProtector with the mount point and KeyProtectorId. Confirm the correct protector and actual escrow policy.
Storage and file services · Storage and file services | Configure Windows Server storage
Resume protection and verify normal unlocking and protection status. Confirm any revised recovery information is securely stored.
Storage and file services · Storage and file services | Configure Windows Server storage
Match the displayed recovery key ID to the corresponding escrow record. A computer can have several historical recovery protectors.
Storage and file services · Storage and file services | Configure Windows Server storage
Unlock-BitLocker -MountPoint D: -RecoveryPassword <48-digit-password>. Obtain the matching password through an authorized secure process.
Storage and file services · Storage and file services | Configure Windows Server storage
Identify firmware/TPM/boot/policy changes or storage problems that triggered it, then verify protection and rotate used recovery credentials as required.
Storage and file services · Storage and file services | Configure Windows Server storage
Salvage decryptable data to a separate output volume/image using valid key material. It is not a way to bypass missing encryption keys.
Storage and file services · Storage and file services | Configure Windows Server storage
A matching key package in addition to the recovery password or key. The package is bound to the corresponding volume.
Storage and file services · Storage and file services | Configure Windows Server storage
Its contents are overwritten by recovered decrypted data. Use a reviewed separate target and preserve any existing target data first.
Storage and file services · Storage and file services | Configure Windows Server storage
It cannot repair a drive that failed during encryption or decryption and assumes the source was fully encrypted.
Storage and file services · Storage and file services | Configure Windows Server storage
The user EFS certificate/private key or a valid Data Recovery Agent private key. Taking ownership does not supply decryption material.
Security · Security | Secure Windows Server operating system
It applies process mitigations that make exploitation of vulnerable software harder. It complements malware detection and software execution controls.
Security · Security | Secure Windows Server operating system
DEP prevents execution from memory marked for data. It does not decide which publishers are allowed to install software.
Security · Security | Secure Windows Server operating system
ASLR changes memory layout so useful addresses are harder for an exploit to predict. Application/platform support influences its effectiveness.
Security · Security | Secure Windows Server operating system
CFG restricts indirect control-flow transfers to valid targets. It addresses exploit behavior rather than general file reputation.
Security · Security | Secure Windows Server operating system
System settings provide defaults, and a program-specific configuration can override them. Inspect the targeted executable's effective settings.
Security · Security | Secure Windows Server operating system
A path narrows the configuration to the intended program location. Name-only targeting can affect other executables with the same name.
Security · Security | Secure Windows Server operating system
No. Only supported mitigations offer audit behavior; confirm the selected mitigation before planning a nonblocking pilot.
Security · Security | Secure Windows Server operating system
Export a tested configuration as XML and deploy it with Use a common set of exploit protection settings. Targets must be able to read the XML.
Security · Security | Secure Windows Server operating system
Identify the failing mitigation and use a narrow tested exception if necessary. Validate full workflows and process/restart requirements rather than disabling all protections.
Security · Security | Secure Windows Server operating system
Code-integrity policy defines which software/code is trusted to run. It can cover kernel/user-mode code and other supported script/installer paths.
Security · Security | Secure Windows Server operating system
Audit permits untrusted code while recording events. Enforcement blocks disallowed code and records relevant events.
Security · Security | Secure Windows Server operating system
It requires production-signed Windows Server 2025 and the OSConfig module. This specific workflow is not a generic deployment method for earlier Server releases.
Security · Security | Secure Windows Server operating system
No. Administrators must configure the desired policies; installation alone does not enable the documented audit scenarios.
Security · Security | Secure Windows Server operating system
The file's hash changes with new content. Properly scoped publisher rules can accommodate signed updates, but must avoid excessive trust.
Security · Security | Secure Windows Server operating system
They reveal legitimate applications, agents, scripts, and update workflows that the policy would block. Use the evidence to refine narrow allow or supplemental rules.
Security · Security | Secure Windows Server operating system
It lists code-integrity policies present on the device. Check expected policy names and mode alongside actual execution/events.
Security · Security | Secure Windows Server operating system
Use the corresponding Remove-OSConfigDesiredConfiguration scenario. Manual removal can be reversed by OSConfig drift control.
Security · Security | Secure Windows Server operating system
No. AppLocker and App Control have different policy models. Validate the effective App Control policy for the program.
Security · Security | Secure Windows Server operating system
It uses virtualization-based security to protect supported NTLM hashes, Kerberos TGTs, and domain credentials from access by normal OS processes.
Security · Security | Secure Windows Server operating system
Eligible domain-joined, non-DC servers meeting platform requirements qualify unless explicitly disabled. Installation on every server does not guarantee it is running.
Security · Security | Secure Windows Server operating system
No. Default enablement is without UEFI lock, permitting administrative remote disablement.
Security · Security | Secure Windows Server operating system
It strengthens resistance to remote disablement and requires a physical-presence recovery process to remove the lock. Plan this tradeoff before enabling it.
Security · Security | Secure Windows Server operating system
Turn On Virtualization Based Security under Computer Configuration, Administrative Templates, System, Device Guard includes Credential Guard configuration.
Security · Security | Secure Windows Server operating system
Win32_DeviceGuard.SecurityServicesRunning containing 1 identifies Credential Guard. Check actual running state after the required restart.
Security · Security | Secure Windows Server operating system
No. It does not protect those databases or every voluntarily supplied application credential. DC and local-account protection remain necessary.
Security · Security | Secure Windows Server operating system
Microsoft says it provides no additional protection for the DC's directory secrets and can introduce compatibility problems. The member-server default excludes DCs.
Security · Security | Secure Windows Server operating system
Enabling it on Exchange Server is unsupported. Validate application-specific compatibility before rollout.
Security · Security | Secure Windows Server operating system
No. An explicit disable configured before an update is preserved rather than overwritten by default enablement.
Security · Security | Secure Windows Server operating system
It evaluates downloaded applications/files and can warn or block suspicious or unrecognized content. It complements antivirus and application execution policy.
Security · Security | Secure Windows Server operating system
It turns on application reputation and prevents users from turning it off. The chosen warning/bypass behavior determines whether users can proceed.
Security · Security | Secure Windows Server operating system
It prevents users from ignoring the SmartScreen warning. A warning alone can leave an override path.
Security · Security | Secure Windows Server operating system
No. Edge has separate SmartScreen browser policies. Verify each required protection surface.
Security · Security | Secure Windows Server operating system
Prevent bypassing Windows Defender SmartScreen prompts for sites prevents the relevant site-warning override when enabled.
Security · Security | Secure Windows Server operating system
Prevent bypassing of Microsoft Defender SmartScreen warnings about downloads controls the download-warning override.
Security · Security | Secure Windows Server operating system
Check the deployed OS/browser's supported templates and interactive workflow. Client-only MDM settings should not be assumed supported by every Server release.
Security · Security | Secure Windows Server operating system
Reputation decisions and warnings differ from explicit code-integrity execution rules. Unknown reputation does not necessarily prove malware.
Security · Security | Secure Windows Server operating system
Link it to the intended computer OU or another appropriate computer scope. Verify the actual server computer objects are in scope.
Security · Security | Secure Windows Server operating system
DC roles have distinct services, privileges, and dependencies. A member-server configuration should not be assumed suitable for directory servers.
Security · Security | Secure Windows Server operating system
It can manage supported security options, user rights, advanced auditing, firewall, Defender, and administrative template settings. Scope and platform support still apply.
Security · Security | Secure Windows Server operating system
Changes to local/RDP/service logon can interrupt administration or service operation. Test intended users and recovery access with the effective rights.
Security · Security | Secure Windows Server operating system
Give them narrow, reviewable scope and rationale, and verify the effective winning values. Competing settings should not silently broaden access.
Security · Security | Secure Windows Server operating system
Check effective local security state and actual administrative/application workflows. A report alone does not establish every control's behavior.
Security · Security | Secure Windows Server operating system
No. Use domain account policy or fine-grained password policies for domain users; member-server OU policy can affect local accounts.
Security · Security | Secure Windows Server operating system
The AD GPO container and SYSVOL template are separate replicated components. A mismatch can leave clients without the intended security settings.
Security · Security | Secure Windows Server operating system
Competing authorities can repeatedly overwrite each other and cause drift/conflict. Establish a consistent desired value and authority.
Security · Security | Secure Windows Server operating system
Windows Server 2025 is supported. OSConfig does not support earlier Windows Server versions.
Security · Security | Secure Windows Server operating system
No. Install the module, then set the desired scenario for the server's role and verify the result.
Security · Security | Secure Windows Server operating system
SecurityBaseline/WindowsServer/2025/DomainController is the documented role scenario. Select MemberServer or WorkgroupMember for their respective roles.
Security · Security | Secure Windows Server operating system
It applies the scenario's default desired configuration. It is a configuration operation rather than merely a compliance query.
Security · Security | Secure Windows Server operating system
It reports the desired scenario settings and compliance details, including noncompliance reasons. Check per-setting status after any required restart.
Security · Security | Secure Windows Server operating system
It maintains managed settings against deviation from the desired configuration. Manual changes can be reapplied to the managed value.
Security · Security | Secure Windows Server operating system
Use the documented scenario-specific setting override, such as -Setting <name> -Value <value>. Verify the installed module's supported parameter syntax.
Security · Security | Secure Windows Server operating system
Use Remove-OSConfigDesiredConfiguration for that scenario, then verify the resulting state. Do not assume removal restores every historical local choice.
Security · Security | Secure Windows Server operating system
If an Arc-connected server changes role, such as becoming a domain controller, delete and reapply the machine-configuration assignment so the platform detects the new role. This concerns the Windows server role, not an Azure RBAC role.
Security · Security | Secure Windows Server operating system
Baseline restrictions can affect RDP redirection, protocols, authentication, and administration. Compliance should be checked alongside supported operational requirements.
Security · Security | Secure Windows Server operating system
It manages unique rotated passwords for designated local administrator accounts, reducing lateral movement from shared local secrets. It can also manage supported DC DSRM passwords.
Security · Security | Secure Windows Server operating system
It extends the forest schema with Windows LAPS attributes. Run it with appropriate schema authority before AD-backed password management.
Security · Security | Secure Windows Server operating system
It grants computers permission to update LAPS attributes on their own AD objects at the selected scope. This differs from granting helpdesk password-reading rights.
Security · Security | Secure Windows Server operating system
Set BackupDirectory to 2 for Windows Server Active Directory backup.
Security · Security | Secure Windows Server operating system
DFL 2016 or later permits encryption. Earlier DFL can support clear-text AD storage but not this encryption feature.
Security · Security | Secure Windows Server operating system
No. The DFL permits encryption, but Server 2016 DCs do not support their own Windows LAPS DSRM management. Supported Server 2019-or-later DCs can use that feature.
Security · Security | Secure Windows Server operating system
No. ADPasswordEncryptionPrincipal controls the authorized decryptor when the password is stored. Read rights and encryption authorization are separate.
Security · Security | Secure Windows Server operating system
Domain Admins is the default authorized decryptor unless another supported principal is configured.
Security · Security | Secure Windows Server operating system
It uses the account's well-known RID rather than relying solely on its visible name. A specifically named custom account needs suitable account provisioning.
Security · Security | Secure Windows Server operating system
Reset-LapsPassword requests immediate local rotation. Changing expiration in AD takes effect when the device next processes the relevant policy/state.
Security · Security | Secure Windows Server operating system
Event 10018 in the LAPS Operational log reports successful AD password update. Check backup/decryption status rather than merely policy presence.
Security · Security | Secure Windows Server operating system
The documented improved recovery starts with Insider build 27695 and later. Verify the recovery host actually supports the parameter before relying on offline recovery.
Security · Security | Secure Windows Server operating system
Defender Antivirus provides local malware protection. Defender for Servers is a Defender for Cloud plan integrating server security capabilities such as endpoint detection and posture.
Security · Security | Secure Windows Server operating system
It focuses on EDR capabilities through Defender for Endpoint integration. Select Plan 2 when its additional supported capabilities are needed.
Security · Security | Secure Windows Server operating system
It adds agentless vulnerability, malware, and secrets scanning for supported Azure/AWS/GCP cloud workloads. It does not automatically scan physical on-premises disks without agents.
Security · Security | Secure Windows Server operating system
No. Check the selected Defender plan, supported onboarding/provisioning, connectivity, and actual endpoint protection state.
Security · Security | Secure Windows Server operating system
Most use Defender for Endpoint integration and/or agentless scanning. Log Analytics agent or AMA is not a universal prerequisite for current plan features.
Security · Security | Secure Windows Server operating system
Plan 1 can be enabled at individual server resource scope; Plan 2 cannot. Both can be disabled at resource scope, with normal enablement planned at subscription level.
Security · Security | Secure Windows Server operating system
No. It supports all Plan 1 capabilities and applicable additional capabilities; some Plan 2 features require Arc or particular cloud environments.
Security · Security | Secure Windows Server operating system
No. It requires configuration after enabling Plan 2, subject to supported environment and onboarding requirements.
Security · Security | Secure Windows Server operating system
The machine must have the Azure Machine Configuration extension for that assessment capability. This is separate from EDR onboarding.
Security · Security | Secure Windows Server operating system
Check plan scope, supported OS, MDE onboarding/health, outbound connectivity, provisioning, and actual inventory. A running antivirus service alone does not prove EDR integration.
Security · Security | Secure Windows Server operating system
Domain, Private, and Public profiles govern traffic according to network identification. Domain membership alone does not prove every interface has the Domain profile.
Security · Security | Secure Windows Server operating system
The explicit block rule takes precedence. Adding another overlapping normal allow does not neutralize it.
Security · Security | Secure Windows Server operating system
No. Effective behavior follows its rule precedence and matching conditions. Do not use a supposed rule-order number to resolve a block.
Security · Security | Secure Windows Server operating system
Match the required application or listener, protocol, local port, remote scope, and active profile. Keep permissions as narrow as operational requirements allow.
Security · Security | Secure Windows Server operating system
No. A listener must exist independently. Check the listener and routing as well as effective firewall policy when access fails.
Security · Security | Secure Windows Server operating system
It uses IPsec to require or request endpoint authentication and traffic protection. It does not alone grant application traffic permission through the firewall.
Security · Security | Secure Windows Server operating system
Request attempts security but permits unsecured fallback. Require demands matching IPsec security for covered traffic.
Security · Security | Secure Windows Server operating system
Transport protects endpoint traffic; tunnel mode protects traffic between tunnel endpoints. Choose the mode and selectors for the actual topology.
Security · Security | Secure Windows Server operating system
Get-NetIPsecMainModeSA and Get-NetIPsecQuickModeSA inspect active associations. Use them with authentication and crypto proposal checks.
Security · Security | Secure Windows Server operating system
The effective policy can exclude local-rule merging or include another matching block. Inspect ActiveStore and applicable profile/filter conditions.
Security · Security | Secure AD DS
Use fine-grained password policies represented by Password Settings Objects. Assign them to user objects or global security groups.
Security · Security | Secure AD DS
No. Use a global security group representing the population or assign a user directly. OU-linked account policy does not create an FGPP.
Security · Security | Secure AD DS
Domain-level account policy, usually in the selected domain-root GPO, controls the domain default. Member-server OU account policy can affect local accounts.
Security · Security | Secure AD DS
The directly assigned PSO takes precedence over group-associated PSOs. Verify the user's resultant policy.
Security · Security | Secure AD DS
A lower msDS-PasswordSettingsPrecedence number has higher priority. Do not assume the longest minimum length wins.
Security · Security | Secure AD DS
Get-ADUserResultantPasswordPolicy returns the user's resultant PSO. Inspect the domain default separately when no applicable PSO is returned.
Security · Security | Secure AD DS
History prevents reuse of remembered passwords, while minimum age can prevent immediate cycling through replacements. Select settings with the organization's reset workflow in mind.
Security · Security | Secure AD DS
It stores password material in a recoverable form and substantially weakens protection. Enable only for a specific unavoidable compatible requirement.
Security · Security | Secure AD DS
They can limit repeated attempts but can also be abused to deny service. Diagnose stored old credentials and account usage before treating every lockout as an attack.
Security · Security | Secure AD DS
Its documented workflow specifies Windows Server 2012 or later domain functional level. This is distinct from the feature's historical introduction.
Security · Security | Secure AD DS
It adds global and tenant-custom banned-password validation to password changes/resets. Normal domain and FGPP validation still applies.
Security · Security | Secure AD DS
The DC agent evaluates it locally using cached policy. The user's password is not sent to Entra ID for live cloud validation.
Security · Security | Secure AD DS
It relays policy retrieval between DC agents and Entra ID. It is not the component that evaluates each user password.
Security · Security | Secure AD DS
They provide policy-download redundancy. Agents can keep enforcing cached policy during a temporary proxy outage.
Security · Security | Secure AD DS
The domain must use DFS Replication. An installer succeeding in an FRS domain does not mean the product works correctly.
Security · Security | Secure AD DS
Deploy agents to writable DCs that process password changes/resets. An unprotected writable DC can allow a request to bypass the component.
Security · Security | Secure AD DS
Audit logs would-reject passwords while allowing the change. Enforced rejects failures of banned-password validation.
Security · Security | Secure AD DS
No. They retrieve policy through registered proxies; allow required DC-to-proxy RPC and proxy outbound TLS service connectivity.
Security · Security | Secure AD DS
It continues evaluating password changes against the cached policy. Lack of live cloud access does not immediately disable local evaluation.
Security · Security | Secure AD DS
This component accepts the password and logs a warning, while normal AD password rules still apply. Monitor policy freshness and initial deployment.
Security · Security | Secure AD DS
Register the forest and its proxies to the same Entra tenant. Each proxy supports DCs from the forest it belongs to.
Security · Security | Secure AD DS
The documented agent-updater versions are incompatible side by side. Use separate hosts rather than assuming the similarly named proxy products can be coinstalled.
Security · Security | Secure AD DS
Selected human accounts needing stronger credential restrictions, after compatibility testing. Do not use it as a blanket service/computer-account protection group.
Security · Security | Secure AD DS
Client protections require Windows 8.1 or Windows Server 2012 R2 or later. Older clients do not gain the same local protections merely from group membership.
Security · Security | Secure AD DS
Windows Server 2012 R2 or later DFL enables the documented authentication restrictions.
Security · Security | Secure AD DS
No. DC-side restrictions prohibit NTLM for these users, which can break legacy applications that require it.
Security · Security | Secure AD DS
Ensure the account can use AES keys, commonly by a suitable password change on a compatible DC. DES/RC4 preauthentication is restricted.
Security · Security | Secure AD DS
Members cannot use constrained or unconstrained Kerberos delegation under the documented DC protections. Group membership can explain failures even without the sensitive-account flag.
Security · Security | Secure AD DS
The documented restriction limits TGT lifetime and renewal to an initial four hours. A longer domain default does not automatically remove it.
Security · Security | Secure AD DS
Supported clients do not create the usual cached-logon verifier for these users. Plan connectivity and privileged recovery access.
Security · Security | Secure AD DS
NTLM, encryption, offline-logon, and delegation dependencies can lock out the entire administrative population. Pilot accounts and preserve a tested access path.
Security · Security | Secure AD DS
They can apply configurable host/device restrictions or TGT constraints, including supported service/computer scenarios. Audit policy impact before enforcement.
Security · Security | Secure AD DS
They store and control the directory's identities and security data. Privileged compromise can undermine the domain and its managed systems.
Security · Security | Secure AD DS
It reduces installed components and interactive attack surface. Use secure remote administration with the tools needed for the role.
Security · Security | Secure AD DS
Browsers, email, utilities, and application workloads add attack paths to a highly privileged system. Use dedicated secured administration endpoints.
Security · Security | Secure AD DS
Control of the hypervisor or VM files can compromise the DC even without an initial Domain Admin password. Treat the supporting fabric as directory-sensitive.
Security · Security | Secure AD DS
It helps protect directory data when disks or the machine are stolen. Preserve recovery material and verify supported hardware/storage configuration.
Security · Security | Secure AD DS
When physical security is weaker and local writable AD data is unnecessary, it limits writable-directory and cached-password exposure. Keep caching narrowly scoped.
Security · Security | Secure AD DS
Backups can expose directory secrets and support privileged recovery. Restrict backup access and test independent AD recovery workflows.
Security · Security | Secure AD DS
Permit tightly controlled documented service endpoints, using supported proxy designs where applicable. General-purpose internet browsing should remain restricted.
Security · Security | Secure AD DS
No. Patch, configure supported role security settings, restrict access, protect credentials/fabric/backups, and verify operational state.
Security · Security | Secure AD DS
Use SecurityBaseline/WindowsServer/2025/DomainController for the documented role-aware baseline. Pilot required authentication and administrative workflows.
Security · Security | Secure AD DS
Allow only authorized identities from intended secured management systems. Combine user-right assignments with host/network firewall restrictions.
Security · Security | Secure AD DS
No. Delegated directory tasks can be performed from appropriate remote administration tools. Keep OS/DC interactive access separately restricted.
Security · Security | Secure AD DS
It limits administrative endpoint exposure and credential use on untrusted systems. Verify required directory services still remain reachable.
Security · Security | Secure AD DS
Deny rights can override allowed users and lock out intended administrators. Review nested membership and recovery paths before rollout.
Security · Security | Secure AD DS
No. Clients and replication partners need directory protocols. Restrict unnecessary exposure while preserving documented service dependencies.
Security · Security | Secure AD DS
A compromised workstation can expose privileged credentials or tokens. Use separate administration identities and secured administrative devices.
Security · Security | Secure AD DS
Local storage, boot, and console access can undermine OS or directory security. Remote restrictions alone do not protect a physically exposed DC.
Security · Security | Secure AD DS
Editing those policies can change security rights, network access, and execution controls on directory authorities. Protect GPO permissions and audit changes.
Security · Security | Secure AD DS
Test authorized management, denied ordinary-user access, and necessary client/replication flows. Check effective user rights and firewall policy rather than only edited settings.
Security · Security | Secure AD DS
It prevents delegation of that user's security context. Use it deliberately for identities that must not be forwarded to downstream services.
Security · Security | Secure AD DS
It permits unauthenticated requests for encrypted AS responses that can support offline password attacks. Leave preauthentication required unless an explicit compatible need is justified.
Security · Security | Secure AD DS
DES is obsolete and weak. Validate modern AES-compatible authentication instead of retaining a legacy-only encryption option.
Security · Security | Secure AD DS
It requires the smart-card authentication path for interactive logon. Provision compatible certificates, trust, readers, and recovery procedures.
Security · Security | Secure AD DS
It substantially weakens password secrecy by enabling recoverable storage. Use it only for an unavoidable documented protocol requirement.
Security · Security | Secure AD DS
A conventional account still needs protected credential lifecycle and least privilege. Use supported managed service accounts where appropriate.
Security · Security | Secure AD DS
It reduces exposure of administrative credentials during browsing, email, and lower-trust activity. Use the privileged identity only on approved administration paths.
Security · Security | Secure AD DS
It prevents new authentication using that account, but other grants, sessions, and retention responsibilities still need review.
Security · Security | Secure AD DS
They constrain intended account use but are not a complete application authorization model. Verify their effect on actual workflows and recovery access.
Security · Security | Secure AD DS
Domain Admins has broad authority within its domain. Enterprise Admins can affect the forest and should be tightly controlled.
Security · Security | Secure AD DS
An authorized schema modification requiring that privilege. Remove temporary membership after the task rather than using it for ordinary administration.
Security · Security | Secure AD DS
It has broad DC/domain administrative authority. Its name does not make it a low-risk local-only group on a DC.
Security · Security | Secure AD DS
Backup/restore privileges can bypass file ACLs and expose or alter sensitive data. It is not an ordinary password-reset delegation role.
Security · Security | Secure AD DS
Their operational privileges can affect critical server services and security. Assess actual rights rather than treating the group name as a harmless support role.
Security · Security | Secure AD DS
Its security descriptor supplies the permissions template for protected administrative accounts/groups in the domain.
Security · Security | Secure AD DS
It periodically compares and reapplies AdminSDHolder-derived protection on the PDC emulator. Protected objects' ACL inheritance can differ from ordinary OU objects.
Security · Security | Secure AD DS
AdminSDHolder/SDProp protection can disable normal inherited ACL behavior. Investigate the protected status rather than broadly increasing helpdesk rights.
Security · Security | Secure AD DS
These roles enable high-impact forest/schema changes. Use justified task-time membership, protect membership modification, and audit activity.
Security · Security | Secure AD DS
It grants selected directory operations to an identity/group at a chosen scope. It differs from assigning broad Domain Admin membership.
Security · Security | Secure AD DS
Group membership supplies a manageable role boundary for staffing changes and review. The delegated ACL can remain stable.
Security · Security | Secure AD DS
Choose the target OU/container, object types, operations, and inheritance that match the task. Test both allowed and excluded objects.
Security · Security | Secure AD DS
No. Directory rights are operation-specific. Grant only the separate operations actually required.
Security · Security | Secure AD DS
AdminSDHolder/SDProp can replace or protect ACLs outside normal OU inheritance. Do not broaden ordinary helpdesk delegation to bypass that protection.
Security · Security | Secure AD DS
Rights that permit replication of secrets can enable credential extraction. They should not be added casually as a fix for ordinary delegation or RODC issues.
Security · Security | Secure AD DS
Administrative delegation grants directory management rights. Kerberos delegation lets a service access another service in a user's security context.
Security · Security | Secure AD DS
Constrained delegation restricts permitted target services; unconstrained delegation allows broader credential forwarding exposure. Use a deliberate least-privilege design.
Security · Security | Secure AD DS
On the resource-side service/computer object, specifying allowed delegating principals. Protect write access to that object's delegation-related properties.
Security · Security | Secure AD DS
The Account is sensitive and cannot be delegated property prevents their context from being delegated. RBCD does not bypass that restriction.
Security · Security | Secure AD DS
No. Managed passwords do not determine safe targets or resource-side authorization. Review delegated identities, SPNs, and object write permissions.
Security · Security | Secure AD DS
The client obtains a TGT from the KDC, requests a service ticket for the service SPN, and presents that ticket to the service. Service identity and keys must match.
Security · Security | Secure AD DS
It identifies the service account for Kerberos ticket issuance and decryption. Missing or duplicate registration can cause authentication failure or unexpected fallback.
Security · Security | Secure AD DS
DNS locates domain/services and time participates in ticket validation. Resolve names and clock problems before weakening authentication.
Security · Security | Secure AD DS
The expected name/SPN mapping can be absent, preventing the normal Kerberos path and leading to another protocol. Verify actual tickets and service registration.
Security · Security | Secure AD DS
It provides message integrity and authenticity for non-TLS SASL LDAP sessions. It does not provide confidentiality by itself.
Security · Security | Secure AD DS
TLS through LDAPS or STARTTLS supplies confidentiality, integrity, and server identity. Plain simple binds expose credentials without appropriate transport protection.
Security · Security | Secure AD DS
It adds confidentiality along with integrity for supported non-TLS SASL sessions. Signing alone leaves message contents readable.
Security · Security | Secure AD DS
It binds SASL authentication to its specific TLS connection to resist relay over a different TLS session. It applies to TLS plus SASL, not simple binds.
Security · Security | Secure AD DS
New AD deployments require LDAP signing by default. Inspect effective policy in upgraded environments because existing settings can be preserved.
Security · Security | Secure AD DS
When supported requires valid CBT from supporting clients while allowing nonsupporting clients. Always rejects applicable TLS+SASL clients without a valid CBT.
Security · Security | Secure AD DS
When supported is the documented default for new deployments. It is distinct from enforcing Always for every applicable client.
Security · Security | Secure AD DS
Directory Service summary events such as 2887 and per-client 2889 with relevant diagnostic logging help identify clients before stricter enforcement.
Security · Security | Secure AD DS
No. Cloud authentication controls do not automatically retrofit every traditional AD protocol session. Design supported authentication methods for the workload.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
An object is a subsystem, a counter measures a property, and an instance identifies a particular process, disk, interface or similar component.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
It averages across processors. One saturated core can limit a serial workload while total utilization remains moderate.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
It records representative healthy workloads over relevant periods. Compare similar workload, hardware and sampling context when judging an incident.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
It includes paging activity that can be legitimate. Correlate available memory, commitment, hard paging and process Private Bytes growth.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
Latency, IOPS, throughput, queue and workload/storage limits. A queue value alone does not establish poor performance.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
Match the incident duration and logging budget. Long intervals can conceal brief spikes; very short intervals increase data volume and overhead.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
It takes 120 counter samples at five-second intervals, roughly a ten-minute capture. It records evidence rather than repairing the system.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
Counter names can be localized. An English path may not resolve even when the corresponding performance object exists.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
A reusable definition grouping performance counters, event traces or configuration collection with output, scheduling and run conditions.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
When an issue must be captured unattended, overnight or during a reproducible workload for later correlated analysis.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
Relevant counters, sample interval, output location, run-as permissions, schedule, stop conditions and log retention/size limits.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
It preserves binary performance-counter data efficiently for later Performance Monitor analysis. CSV is useful for external processing.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
It creates a named counter collector with specified counters, format, sample interval and output. Starting collection is a separate operation.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
logman start <name> and logman stop <name>. Verify output and stop/rotation behavior before leaving it unattended.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
Unbounded diagnostic logging can fill a disk and worsen an incident. Keep sufficient data with a bounded capture/retention design.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
Remote permissions, firewall, name resolution or management connectivity may be missing. Confirm the collection path independently.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
Performance, events, services, storage and cluster views support operational investigation. Correlate the relevant views with the failing workload.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
No. Gateway, remoting, credentials or management-network problems can block WAC while the application continues serving users.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
Persistent centralized telemetry, alert evaluation and notifications. WAC provides an administrative surface and links to the monitoring configuration.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
Use Azure Arc for the non-Azure server management path, Azure Monitor Agent and associated DCRs. Avoid deploying the retired legacy Log Analytics agent.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
Working collection of the appropriate server/volume metric or log, a valid rule condition and an action group. Verify actual telemetry first.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
One nearly full volume can be hidden by aggregation with healthy disks. Dimension-aware alerts point the operator to the affected resource.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
Confirm the condition generates the expected alert, notification and resolution, with a clear affected server and volume.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
Permission to manage the server or deploy a monitoring extension does not automatically grant permission to read every Azure log workspace.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
Local historical data to forecast CPU capacity, networking capacity, total storage consumption and per-volume consumption.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
No. Its predictive processing runs locally on supported Windows Server 2019 and later systems.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
A forecast estimates future exhaustion from historical trends. A static current threshold triggers only after measured utilization crosses it.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
Predicted demand exceeds available capacity within the next seven days. Inspect the status description and capability data.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
Predicted demand exceeds available capacity within the next 30 days, outside the more urgent critical window.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
The default model needs history; zero to five days of data produces no forecast. None is not automatically a failed feature.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
Get-InsightsCapability and Get-InsightsCapabilityResult. Examine the status, description and capability-specific result data.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
Models use previous behavior. A new retention policy, import or workload can make past growth less representative of future demand.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
IDs are scoped to providers. Correlate provider, message, timestamp, computer and event ID.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
Windows logs include System, Application and Security. Component-specific operational logs appear under Applications and Services.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
It exports the System event log as an EVTX file. It does not clear the original log or enable new auditing.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
It filters by properties such as log, level and time before returning records, avoiding a broad read of a busy log.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
It allows continued logging by replacing old records. Important evidence may be lost if collection/export occurs too late.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
The disk can fill or logging can stop under the configured full-log policy. Match size and retention to audit and workload needs.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
Subscribed event collection from source computers to a collector. Scope, permissions, transport and collector retention still require configuration.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
The relevant audit policy, log access or retention may be missing. Confirm event generation and collection before interpreting absence.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
Data sources, filters/counters, destinations and supported processing transformations for its collection scenario.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
It connects a rule to a monitored resource so the agent downloads that configuration and collects its specified data.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
No. A matching DCR association and enabled data source are required; agent installation alone does not specify all guest collection.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
Yes. Associations are many-to-many: one rule can serve multiple resources and a resource can use multiple rules.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
Event in Log Analytics. The Sentinel Windows Security Events via AMA connector can instead send security events to SecurityEvent.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
Critical and error events in the System log. It is a log-name plus XPath selector, not a performance-counter path.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
No, not through this event-subscription mechanism. Use supported standard/operational channels and validate the filter locally.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
Private Link and relevant shared AMPLS DNS contexts require a DCE, and certain data sources also require one. Public-endpoint AMA does not universally need a DCE; check the selected source and destination requirements.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
A logs-based counter DCR can write Perf to Log Analytics. The new OpenTelemetry metrics experience uses an Azure Monitor workspace.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
Resource scope, signal and condition, evaluation logic, severity and actions. Validate the signal exists before enabling the rule.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
For a numeric time-series condition such as sustained CPU utilization or a disk metric threshold.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
When a KQL query over collected logs identifies the condition, such as repeated specific Windows service failures.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
Azure management-plane operations or supported activity events. It does not collect all guest Windows event logs.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
A reusable notification or approved automation target set invoked by alert rules. It is separate from the detection condition.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
Average over a longer window detects sustained load. Maximum over a shorter window captures bursts and can produce more noise.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
To evaluate affected resources separately instead of averaging one full volume with healthy volumes.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
They can suppress or modify action handling for matching alerts without changing the underlying collection and detection rule.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
A lack of error rows can mean missing collection rather than health. Detect heartbeat/data absence according to the expected reporting pattern.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
Azure collects host metrics automatically. Guest memory, local performance details and Windows events require a configured guest collection path.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
Install Azure Monitor Agent, define suitable DCRs and associate them with the VM. The portal onboarding flow can configure these pieces.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
The OpenTelemetry metrics experience using an Azure Monitor workspace. Classic logs-based metrics remains available for existing compatible deployments.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
A Log Analytics workspace. The classic predefined guest metrics use InsightsMetrics; additional standard counter DCRs can use Perf.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
No. Current enablement guidance says not to modify that predefined logs-based DCR; use additional appropriate collection rules for other requirements.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
Azure Connected Machine agent onboarding to Azure Arc-enabled servers. It supplies the management path for deploying AMA.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
Deprecated, with retirement scheduled for 30 June 2028. Current guidance says not to initiate new Dependency Agent installations.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
A disk can hit provisioned IOPS/throughput limits, and the VM size can impose aggregate caps. Guest filesystem health alone does not rule out throttling.
Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
Activity Log shows management changes such as resizing or extension operations; boot diagnostics helps when the guest cannot start.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
ICMP reachability does not prove the service TCP port is reachable or the application authenticates. Test the actual protocol and operation.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
TCP connectivity to the SMB port, with optional DNS and route details. It does not prove SMB authentication or file permissions.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
IP address, prefix, gateway, DNS servers, interface state and selected routes. Compare with the intended subnet and a working peer.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
Service state, listening address/port and effective Windows Firewall rules/profile, then upstream network filtering.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
The return path may be missing, asymmetric or filtered. Validate routing and stateful security in both directions.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
NIC/subnet NSGs, user-defined/effective routes, NVAs, gateways and firewalls. Inspect the effective packet path.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
An MTU/fragmentation or loss problem may exist. Correlate packet sizes, retransmissions and captures rather than assuming credentials failed.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
QUIC normally uses UDP 443. Exercise an actual QUIC SMB connection to validate its transport and security layers.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
If the IP path works while the name fails, inspect DNS selection and returned addresses. Authentication can still require the correct name/SPN.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
The DNS server to query. It helps compare authoritative, internal and client-selected resolver responses.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
LLMNR and NetBIOS resolution. It isolates the DNS result rather than allowing alternate local-name mechanisms.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
Client DNS settings, split-horizon zones, conditional forwarding, cached records and the intended authoritative zone.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
A timeout suggests no usable response, such as reachability/server problems. NXDOMAIN is a negative answer that the queried name does not exist.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
Clients may keep an earlier negative answer until expiry or a controlled cache refresh. Validate the record at the intended resolver first.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
AD SRV records and valid DC host records. Point domain clients to DNS servers that resolve the AD namespace.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
The normal storage file endpoint name must resolve through the private-link design to the intended reachable private IP.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
Scan/detection, download, installation and post-install/restart. Different stages have different policy, network and servicing causes.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
Applications and Services Logs, Microsoft, Windows, WindowsUpdateClient, Operational. Correlate errors with the update attempt time.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
A readable static WindowsUpdate.log assembled from ETL traces. Run it again for a refreshed view; the output is not continuously updated.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
Component-based servicing and update installation. Scan/download errors may require Windows Update trace and network/policy evidence instead.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
Effective update-source policy, WSUS reachability, product/classification approval, applicability and detection timing. Missing approval is distinct from a failed installation.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
OS version, architecture, installed/superseding packages or prerequisites can differ from the package requirements. Check the exact update applicability.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
It checks component-store corruption in the running OS. It does not approve WSUS updates or automatically correct every network download failure.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
Rescan and complete the original update, confirm installation/restart state and validate workload health. A cleared error alone is not completion.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
NT5DS, which follows the AD domain time hierarchy. The forest-root PDC emulator normally uses a reliable external source.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
The PDC emulator in the forest-root domain. Configure its intended reliable source and inspect effective configuration.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
UDP 123. A successful TCP test does not validate the NTP exchange.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
The current selected synchronization source. Combine it with status and configuration to distinguish configured peers from the active source.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
Effective time-service settings, including policy influence. Local changes can be overridden by Group Policy.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
Offset relative to a peer over repeated samples. Its diagnostic source port differs from the built-in NTP client behavior.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
Kerberos requires time agreement within policy tolerance. Correct the time source/path instead of assuming every ticket failure is a password issue.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
Resynchronize as appropriate and verify selected source, recent successful sync, offset and downstream domain member behavior.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
Identify the affected workload, incident time, recent changes and bottleneck evidence. Added resources may hide a regression without fixing it.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
A serial process can be CPU-bound despite moderate total CPU. Examine per-core and process behavior before assuming spare CPUs solve it.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
Sustained Private Bytes growth across comparable demand, shrinking available memory and rising commitment. One paging spike is insufficient.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
The disk or VM can reach provisioned IOPS/throughput limits while otherwise healthy. Correlate guest latency with platform limits.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
CPU counts, storage parallelism and workload demand differ. A fixed queue threshold cannot diagnose every server or array.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
A working peer with similar workload, OS/configuration, resource allocation and recent changes. Avoid comparing incomparable demand periods.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
Aligned counters, events and application measurements show whether the suspected resource change correlates with the symptom and recovery.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
Repeat the original application operation and confirm latency/throughput plus resource health. A different counter becoming low is not sufficient.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
Extensions execute inside the guest through an agent and have separate handler provisioning and workload execution states.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
The Azure VM Agent. On Arc-enabled servers the Connected Machine/extension management components provide a different management path.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
Detailed provisioning status, substatus and errors. Correlate those details with the handler version and operation time.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
Under C:\WindowsAzure\Logs\Plugins. Inspect the extension-specific handler/output and guest-agent health.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
C:\ProgramData\GuestConfig\ext_mgr_logs\gc_ext.log. It includes extension download and package-verification issues.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
It tests communication with required network endpoints and reports endpoint, proxy, private-link, or Arc gateway paths. Use it to distinguish network reachability from extension handler/script health.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
Download/verification failures concern the handler/network path. A script can fail after installation due to arguments, permissions or workload prerequisites.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
Preserve logs, identify and fix the actual cause, use its supported rerun/update procedure and verify the intended guest state.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
Distinguish locked BitLocker, missing EFS key, Azure key dependency, and physical/filesystem damage. Similar symptoms need different recovery paths.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
Volume lock/conversion/protection status and protector IDs. Preserve recovery material and identify the actual affected volume.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
Boot integrity measurements changed or protection was not correctly resumed. Investigate the trigger and verify effective configuration.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
It does not recreate missing encryption key material and can remove usable TPM-backed secrets.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
The files may additionally use EFS or deny access through ACLs. Volume and per-file encryption/authorization are separate layers.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
It can indicate storage-path or filesystem damage, not necessarily a missing password. Preserve evidence and diagnose the lower layers.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
Key availability/version, authorized access and Key Vault/network configuration. Identify the actual encryption design instead of treating every failure as guest BitLocker.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
Confirm real file reads, normal protection state and the underlying cause; rotate used recovery credentials according to policy.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
Physical/path, disk, pool/virtual disk, partition, filesystem, then share/application. An inaccessible share does not identify the failed layer.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
Disk presentation/online state from partition/filesystem volume state. A present disk does not guarantee its volume is mounted or readable.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
Repair or allocation jobs in progress. Active repair can affect latency and remaining failure tolerance.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
Thin volumes can show logical free space while backing physical capacity is exhausted. Both layers can block writes.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
It may contain damaged existing data. Preserve the source/backups and identify storage-path or filesystem failures before destructive changes.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
iScsiPrt/Disk/StorPort events, MPIO path state, target mappings and array/network health, using the incident timestamps.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
No. Use the supported ReFS integrity/salvage workflow and underlying storage health checks rather than assuming NTFS chkdsk behavior.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
A real read/write workload succeeds and expected redundancy/path health is restored. Mounted state alone can conceal degradation.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
Windows Server 2008 R2 or later forest functional level. Enabling it is a forest-wide, irreversible change requiring appropriate forest administrative rights.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
Yes, for its full deleted-object restoration benefits. Enabling it later does not retroactively preserve all attributes of already tombstoned objects.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
It restores deleted objects with preserved attributes and links such as memberships, without a DC database restore or reboot.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
The specific deleted AD object when it remains restorable. Identify the exact GUID and intended parent instead of matching an ambiguous name.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
Restore missing parents before their child objects. A deleted child cannot simply return to a parent that does not exist.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
Configured deleted-object and tombstone lifetimes determine restorability. Do not assume every forest uses a 180-day period.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
No. The restorable deleted-object period has ended; an appropriate alternate recovery method is needed.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
Parent location, attributes, memberships and replication to relevant DCs, followed by the object real workload behavior.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
The AD DS database. ESE transaction logs and checkpoints support consistent database operations; an active-file copy is not a supported system-state backup.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
A DC recovery startup mode with its local AD database offline, used for the supported directory restoration workflow.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
The local Administrator account with the DSRM password. Do not assume the current domain administrator password is the DSRM credential.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
The restored DC receives newer directory changes from its replication partners and catches up.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
Healthy partners can replicate the deletion back. A restorable Recycle Bin object or targeted authoritative recovery may be needed.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
It raises attribute versions so selected restored data wins replication over partners existing versions. Use the required object/subtree scope.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
After restoring the supported directory backup in DSRM, before restarting normally and allowing AD replication.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
The directory database holds objects and GPO metadata; SYSVOL holds policy files/scripts with its own DFS-R recovery procedure.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
DNS, DC advertising, authentication, AD replication, SYSVOL/NETLOGON and appropriate FSMO/time configuration, not just a successful local login.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
Group Policy file content and scripts. Its DFS-R replication is distinct from AD database object replication.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
Identify a verified good content source, inspect DFS-R events and repair underlying AD/DNS/network problems. Preserve policies/scripts.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
When an affected DC should replace its local SYSVOL state by synchronizing from a verified healthy partner.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
msDFSR-Enabled is set FALSE, replicated/polled, then TRUE with another replicated/polled change, following the documented ordering.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
The subscription has stopped replicating after being disabled. It is an expected checkpoint before re-enabling synchronization.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
Events 4614 and 4604 appear in the documented initialization sequence. Verify the completed state and actual share/content health.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
msDFSR-options=1 on its SYSVOL Subscription, alongside the coordinated enable/disable and service ordering; event 4602 confirms authoritative initialization.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
No. They are FRS settings. DFS-R SYSVOL uses its documented AD subscription-attribute procedure.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
No. Recover both the directory metadata and corresponding policy files coherently, using appropriate GPO or system-state backups.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
A broad AD replication failure summary. Use it to identify affected sources/destinations and then inspect detailed partner/context failures.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
Inbound replication partners, naming contexts and last-success/error information for a DC. Different partitions can have different failures.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
DC discovery and partner identification depend on valid host, SRV and GUID-related records and the correct resolver path.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
Routing, firewall, endpoint mapper/dynamic-port or service availability problems. Test the path rather than repeatedly forcing synchronization.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
Authentication, authorization, machine-account or related security/time issues. A reachable network does not establish replication permission.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
Expected deployment outages can explain replication errors. Distinguish an intentional offline partner from an unexpected failure before remediation.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
It can retain obsolete objects and trigger replication safeguards. Use a supported lingering-object or rebuild strategy rather than bypassing protections.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
Check sustained clean reports and propagation of relevant changes across DCs, then independently verify DFS-R SYSVOL and real authentication behavior.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
Affected accounts, sites, clients and DCs, plus online domain authentication versus cached sign-in. The scope guides the next test.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
Whether the client can discover a suitable domain controller. Discovery still must be followed by service/authentication checks.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
Targeted DC health tests such as DNS, advertising and services. Interpret actual failures and test scope rather than assuming one pass proves all AD healthy.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
AD DS, DNS, Netlogon, KDC and DFS-R/SYSVOL, with network and disk health. AD Web Services also matters for many management tools.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
Branch DNS, routing, site/subnet mapping or DC selection may differ. Compare the affected site with a working one.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
Account state, password/expiry, lockout, logon restrictions and relevant failure events. A domain-wide rebuild is not implied.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
Identify the source host/service and stale stored credentials using failure timing and logs, then correct the actual recurring attempt.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
Authorization still requires the proper share and file permissions. Diagnose authentication and resource ACLs as separate checkpoints.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
Working DNS, reachable KDC/DC services, acceptable time agreement, valid account keys and correct service identity/SPNs.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
A TGT is used to request service tickets from the KDC. A service ticket targets the SPN of the resource the client accesses.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
klist. Use klist get <service-SPN> for a targeted ticket request when diagnosing a particular service.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
It queries registrations for that SPN. Verify the actual service account and expected hostname before changing ownership.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
The requested service principal cannot be found. Check the requested name, service class and relevant SPN registration.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
The service principal resolves ambiguously, commonly due to duplicate SPNs. Identify the correct service identity and remove the erroneous registration.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
The service may receive a ticket encrypted for another account key and fail to decrypt it. DNS misdirection or key mismatch can also contribute.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
-S verifies duplicate SPNs before adding. It does not remove the need to identify the correct account and service.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
The first service may not be allowed to delegate to the backend SPN, or the user may prohibit delegation. Valid first-hop credentials do not imply delegation rights.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
The member local machine-account secret and the corresponding AD computer account secret, maintained through Netlogon.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
Snapshot rollback, old machine restore, duplicated identities or inconsistent DC data. Check reachability and replication before resetting.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
True or False for its domain secure channel; -Verbose adds diagnostic detail and -Server selects a preferred DC.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
Test-ComputerSecureChannel -Repair with appropriate credentials and a reachable selected DC. Retest afterward.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
No. It is for domain members and can return false-positive errors on DCs; use documented netdom/nltest procedures for DCs.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
Failure to locate/reach an appropriate DC or authenticate due to skew can resemble trust failure without proving a lost machine secret.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
Investigate replication and computer-account consistency across those DCs before repeated resets.
Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
Rejoin can affect the computer identity and service dependencies. Prefer the appropriate supported targeted repair when its prerequisites hold.
These are original study questions. Multiple-response practice uses exact-set scoring in the app, with no partial credit.
AD DS · AD DS | Deploy and manage AD DS domain controllers
✓ Correct answer
Install-ADDSDomainController promotes an additional replica. Install-ADDSForest creates a forest, the Test cmdlet only checks prerequisites, and a domain join leaves a member server without the DC role.
Open this question’s page →AD DS · AD DS | Deploy and manage AD DS domain controllers
✓ Correct answer
Installation from media reduces initial replication but still requires a live DC for remaining updates. An arbitrary VM disk copy is not a supported independent promotion workflow; removing all live connectivity defeats IFM requirements. A second forest does not add a replica to the existing domain.
Open this question’s page →AD DS · AD DS | Deploy and manage AD DS domain controllers
✓ Correct answer
SYSVOL/NETLOGON and DFS Replication directly support policy-file availability. Refresh intervals do not restore missing server-side files. Schema-master transfer addresses another operation, and AD replication is separate from SYSVOL file replication.
Open this question’s page →AD DS · AD DS | Deploy and manage AD DS domain controllers
✓ Correct answers
AD-capable DNS and healthy reachable partners support discovery and replication. A public resolver lacks private AD service records; role installation adds binaries but does not promote the server.
Open this question’s page →AD DS · AD DS | Deploy and manage AD DS domain controllers
✓ Correct answer
AD DNS resolves the SRV records needed for domain discovery. A public IP does not fix private DNS, a load balancer is not the AD DC Locator mechanism, and moving the PDC role does not populate the client's DNS service records.
Open this question’s page →AD DS · AD DS | Deploy and manage AD DS domain controllers
✓ Correct answer
Persistent data storage with caching None follows the AD DS write-consistency guidance. The temporary disk and ephemeral OS storage are unsuitable for persistent directory state. ReadWrite host caching is not the prescribed NTDS data-disk setting.
Open this question’s page →AD DS · AD DS | Deploy and manage AD DS domain controllers
✓ Correct answer
Subnet/site mappings guide DC Locator locality. External forwarder preference and public DNS do not create the missing AD site mapping or private discovery data. LDAP load balancing does not replace correct AD site configuration.
Open this question’s page →AD DS · AD DS | Deploy and manage AD DS domain controllers
✓ Correct answers
Azure NIC reservations preserve DC addresses, and multiple zone-separated DCs reduce a shared availability failure. Guest-only unrelated static addressing conflicts with Azure network provisioning. Temporary disks do not provide durable directory storage.
Open this question’s page →AD DS · AD DS | Deploy and manage AD DS domain controllers
✓ Correct answer
An RODC limits writable-directory and cached-secret exposure while supporting branch services. Broad writable/password exposure fails the security requirement. A duplicate forest changes identity design, and installed binaries on a member server do not provide DC authentication.
Open this question’s page →AD DS · AD DS | Deploy and manage AD DS domain controllers
✓ Correct answer
Staged installation separates central directory preparation from delegated branch deployment. Schema Admins is unnecessary broad authority; binaries without promotion do not form a DC. A new forest would not attach the server to the prepared RODC account.
Open this question’s page →AD DS · AD DS | Deploy and manage AD DS domain controllers
✓ Correct answer
Uncached credentials require validation by a writable DC. PRP eligibility does not prove caching; global catalog membership data is not a cache of every domain password. Workstation cached sign-in is separate from validating new domain authentication at the RODC.
Open this question’s page →AD DS · AD DS | Deploy and manage AD DS domain controllers
✓ Correct answers
RODCs can host read-only AD DNS and a GC. Normal directory changes and authoritative password resets still need writable DC services; hosting DNS or GC does not remove that boundary.
Open this question’s page →AD DS · AD DS | Deploy and manage AD DS domain controllers
✓ Correct answer
PRP deny precedence blocks caching. Addition time does not override it, WAN failure does not change eligibility, and a GC role does not bypass PRP.
Open this question’s page →AD DS · AD DS | Deploy and manage AD DS domain controllers
✓ Correct answer
Prepopulation supplies permitted secrets before loss of connectivity and verification confirms them. Eligibility alone does not prove caching. Allowing Domain Admins or deleting deny controls unnecessarily exposes high-value credentials.
Open this question’s page →AD DS · AD DS | Deploy and manage AD DS domain controllers
✓ Correct answer
Incorrect replication privileges or inconsistent replicated PRP/group state can explain unexpected caching. FSMO placement, workstation cached-logon settings, and GPO refresh frequency do not govern the RODC password replication authorization.
Open this question’s page →AD DS · AD DS | Deploy and manage AD DS domain controllers
✓ Correct answers
The revealed list identifies actual cached-secret exposure, and resetting those secrets invalidates compromised credentials. PRP edits do not revoke a stolen password; focusing only on the installer ignores other exposed accounts.
Open this question’s page →AD DS · AD DS | Deploy and manage AD DS domain controllers
✓ Correct answer
Schema modifications require the schema master. RID allocation creates unique principal identifiers, the infrastructure master maintains cross-domain references, and the domain naming master manages domain/application-partition changes.
Open this question’s page →AD DS · AD DS | Deploy and manage AD DS domain controllers
✓ Correct answer
Planned retirement of a healthy owner calls for transfer and verification. Seizure is a recovery path when transfer cannot work; deleting the VM leaves unmanaged role ownership. Functional-level changes do not create multiple RID masters.
Open this question’s page →AD DS · AD DS | Deploy and manage AD DS domain controllers
✓ Correct answer
DCs consume local RID pools, then need the RID master for additional allocation. The schema master governs schema updates, the infrastructure master cross-domain references, and the domain naming master forest domain changes; none replenishes RID pools.
Open this question’s page →AD DS · AD DS | Deploy and manage AD DS domain controllers
✓ Correct answers
Permanent loss and impossible transfer with controlled retirement support seizure. Healthy planned maintenance supports transfer if a move is needed. FSMO is single-master coordination and cannot be duplicated across every DC.
Open this question’s page →AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
✓ Correct answer
The resource side must trust the account side to accept its users. Reversing the trust enables the opposite access direction. DNS forwarders provide discovery rather than an authentication relationship; a distribution group alone neither creates trust nor grants security permissions.
Open this question’s page →AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
✓ Correct answer
Selective authentication adds Allowed to authenticate on the target computer. Reading its object or listing a share does not satisfy that authentication gate. User password-reset delegation is a directory administration right rather than target-computer authentication authorization.
Open this question’s page →AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
✓ Correct answer
Forest trusts are transitive across domains in the two participating forests but not across a chain into a third forest. They do not require Domain Admin for normal resource access or copy user accounts/passwords into the other forest.
Open this question’s page →AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
✓ Correct answers
Trust validation establishes the relationship, while resource ACLs and selective authentication still control access. Trusts grant no automatic Modify permission, and SID filtering should not be universally disabled.
Open this question’s page →AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
✓ Correct answer
Subnet-to-site association supplies the missing locality mapping. Link costs choose replication routes, OUs scope policy/delegation, and functional level does not map client addresses to sites.
Open this question’s page →AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
✓ Correct answer
The interval operates inside the permitted schedule. It does not open closed hours or limit an open four-hour window to a single attempt. Cost changes route preference, not timing.
Open this question’s page →AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
✓ Correct answer
Site-link bridging can imply connectivity absent from a partially routed WAN. Changing timing alone cannot make an unreachable path work. Bridgehead selection also requires reachable paths and does not by itself correct inappropriate transitive assumptions.
Open this question’s page →AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
✓ Correct answers
Subnet and site objects map addresses to directory network locality. Distribution groups model messaging membership, and forest trusts connect identities rather than individual network prefixes.
Open this question’s page →AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
✓ Correct answer
The object under the destination's NTDS Settings represents inbound AD replication from the named source. The opposite direction requires its own topology; this is not merely a SYSVOL DFSR object.
Open this question’s page →AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
✓ Correct answer
SYSVOL templates/scripts use DFS Replication separately from AD containers. RID allocation concerns new SIDs; trust authentication concerns external access; the GC partial attribute set does not replicate SYSVOL files.
Open this question’s page →AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
✓ Correct answer
Source discovery and RPC/service reachability directly explain transport failures. FSMO seizure and object deletion are recovery changes unsupported by this evidence. Repeated synchronization does not restore an unreachable endpoint.
Open this question’s page →AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments
✓ Correct answers
Forest-wide schema/configuration and GC partial cross-domain replicas are the correct scopes. A writable DC has its own writable domain partition, not every domain. SYSVOL scripts use file replication rather than schema attributes.
Open this question’s page →AD DS · AD DS | Create and manage AD DS security principals
✓ Correct answer
The unchanged SID preserves the identity referenced by the ACL. Display-name matching and UPN spelling are not the security principal stored in the NTFS access entry. Renaming does not create a replacement SID or a second account.
Open this question’s page →AD DS · AD DS | Create and manage AD DS security principals
✓ Correct answer
AGDLP uses global role membership and a domain-local resource permission group. Individual ACL entries bypass that model, distribution groups are not DACL security principals, and global membership is limited to its own domain.
Open this question’s page →AD DS · AD DS | Create and manage AD DS security principals
✓ Correct answer
A fresh logon token can incorporate new membership. Distribution conversion removes the security-group purpose; GPO filtering does not replace the resource ACL. Display-name matching does not control SID-based file authorization.
Open this question’s page →AD DS · AD DS | Create and manage AD DS security principals
✓ Correct answers
Security-group rights simplify permission management, while intended OU and role placement supports policy and delegation. Recreation changes the SID unnecessarily; distribution groups cannot serve the required DACL authorization role.
Open this question’s page →AD DS · AD DS | Create and manage AD DS security principals
✓ Correct answer
AGUDLP aggregates domain global groups in a same-forest universal group and assigns rights through a resource domain-local group. One global group cannot contain accounts from both domains; distribution groups are not NTFS authorization principals. Nesting a domain-local group inside global groups violates the global membership model and reverses the intended hierarchy.
Open this question’s page →AD DS · AD DS | Create and manage AD DS security principals
✓ Correct answer
A resource-domain domain-local group can contain eligible trusted principals such as the external global group. A Resources global group cannot contain external users, and universal membership does not span forests this way. Trust access does not copy password databases.
Open this question’s page →AD DS · AD DS | Create and manage AD DS security principals
✓ Correct answer
Explicit domain/DC context and identity verification target the intended object. An unqualified lookup or unchecked first match retains ambiguity. More privilege does not distinguish same-named objects in different domains.
Open this question’s page →AD DS · AD DS | Create and manage AD DS security principals
✓ Correct answers
Foreign security principals represent external identities, and domain-local resource groups can incorporate eligible trusted principals. Universal membership remains within its forest; trust validation does not refresh already issued logon tokens.
Open this question’s page →AD DS · AD DS | Create and manage AD DS security principals
✓ Correct answer
A gMSA supports multiple approved hosts and managed passwords. An sMSA is for one host; LocalService does not provide the required shared domain identity. A shared Domain Admin password violates the least-privilege service design.
Open this question’s page →AD DS · AD DS | Create and manage AD DS security principals
✓ Correct answer
A stale machine token can omit the newly granted host-group membership. Adding all users broadens secret access, and Domain Admins is unnecessary service privilege. Recreating root keys per startup introduces risk without addressing host-token state.
Open this question’s page →AD DS · AD DS | Create and manage AD DS security principals
✓ Correct answer
The convergence period and healthy replication allow DCs to generate the same managed credentials reliably. Backdating is a lab shortcut, not a production repair. A gMSA uses generated managed passwords, and disabling Kerberos does not fix KDS readiness.
Open this question’s page →AD DS · AD DS | Create and manage AD DS security principals
✓ Correct answers
Application compatibility and host retrieval authorization are required. Domain Admin membership is not a default or necessary prerequisite. Manual password entry defeats the managed-account model.
Open this question’s page →AD DS · AD DS | Manage Windows Server by using domain-based Group Policies
✓ Correct answer
Link order 1 has highest precedence at the same container. The largest number and creation date do not supply this precedence. Conflicting single-value settings do not always merge, although settings in separate areas can accumulate.
Open this question’s page →AD DS · AD DS | Manage Windows Server by using domain-based Group Policies
✓ Correct answer
Replace uses only the computer-location user GPO list. Merge retains the ordinary user list before adding the computer-based list. GPOs cannot be linked directly to user accounts, and disabling computer processing prevents the intended loopback configuration.
Open this question’s page →AD DS · AD DS | Manage Windows Server by using domain-based Group Policies
✓ Correct answer
Enforcement does not grant Read or Apply Group Policy permissions. It is not a Schema Admin-only mode, survives ordinary block inheritance, and does not disable computer settings.
Open this question’s page →AD DS · AD DS | Manage Windows Server by using domain-based Group Policies
✓ Correct answers
Scope/permissions and result/replication checks identify application failures. A forced refresh cannot remove extension restart/logoff requirements. Central Store files define editor templates rather than proving client policy application.
Open this question’s page →AD DS · AD DS | Manage Windows Server by using domain-based Group Policies
✓ Correct answer
Item-level targeting scopes just the Finance item. Filtering the whole GPO also removes unrelated maps for others; groups are not direct GPO link containers. Replacing every map neither provides membership targeting nor avoids disruption.
Open this question’s page →AD DS · AD DS | Manage Windows Server by using domain-based Group Policies
✓ Correct answer
Update can preserve the existing mapping while changing specified properties. Delete removes it; Create normally leaves an existing item unchanged rather than overwriting it. Privileged membership does not correct replacement semantics.
Open this question’s page →AD DS · AD DS | Manage Windows Server by using domain-based Group Policies
✓ Correct answer
Preferences can persist unless supported removal behavior or an explicit cleanup action is used. A lingering mapping does not prove current targeting. Apply once prevents reapplication rather than guaranteeing cleanup, and renaming the GPO does not delete the old mapping.
Open this question’s page →AD DS · AD DS | Manage Windows Server by using domain-based Group Policies
✓ Correct answers
Apply once is an initial-only processing choice. The separate removal option provides deliberate cleanup and selects Replace where supported. These statements describe each option individually; they do not prescribe combining them. Apply once does not mean repeated replacement, and preferences can persist after leaving scope unless cleanup is configured.
Open this question’s page →Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
✓ Correct answer
A shared Windows Admin Center gateway provides the common management URL. Individual desktop installations do not provide the requested shared endpoint. A data collection rule defines telemetry collection, and an RDS licensing server issues client access licenses rather than acting as a server-management console.
Open this question’s page →Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
✓ Correct answer
The Arc WAC extension and outbound service endpoints support the portal experience without inbound connectivity. AMA supplies telemetry rather than this console; inbound WinRM alone does not deploy the portal extension. A desktop gateway is a separate deployment and does not configure the requested Arc portal access.
Open this question’s page →Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
✓ Correct answer
Windows Admin Center Administrator Login supplies the documented data action in addition to Reader. Virtual Machine Administrator Login targets a different Azure VM sign-in experience, onboarding permission registers Arc servers rather than granting WAC login, and VM resource contribution does not replace the WAC login data action.
Open this question’s page →Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
✓ Correct answers
The documented Azure login roles and required outbound service reachability are both necessary. A public RDP rule is not part of this connection path, a workspace shared key does not authenticate WAC, and the portal supports its own tool set rather than requiring all local gateway extensions.
Open this question’s page →Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
✓ Correct answer
Invoke-Command runs the query on the specified remote computers and returns results. Enter-PSSession creates a single interactive session; local Get-Service examines the local host. Creating sessions alone does not execute the requested query.
Open this question’s page →Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
✓ Correct answer
The additional resource request introduces a second-hop identity boundary. Check the executing identity and supported delegation design. The working first-hop transport, demonstrated SMB connectivity and successful name resolution do not establish the identity that accesses C.
Open this question’s page →Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
✓ Correct answer
The constrained endpoint grants the requested operation without broad standing privilege. Unrestricted script execution or local Administrators defeats the boundary. Changing startup type does not restrict what operators can execute through an unrestricted endpoint.
Open this question’s page →Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
✓ Correct answers
Configure the run-as identity and authorize that identity at the resource. gMSA status does not confer universal share permissions. Domain Admins membership is unnecessary and excessive for the operators. Unrestricted external commands weaken JEA rather than satisfying the defined resource rights.
Open this question’s page →Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
✓ Correct answer
The second-hop documentation explicitly identifies the WinRM limitation of resource-based constrained delegation. Delegation support is service-specific. DNS zone type does not remove that protocol limitation, and TrustedHosts does not grant endpoint authorization or automatically delegate credentials.
Open this question’s page →Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
✓ Correct answer
Remoting commonly returns serialized data rather than the live remote object. Execute the operation remotely while that object exists there. A same-named local service is a different target; wrapping data or creating a new session does not reconstruct the old copy's native methods.
Open this question’s page →Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
✓ Correct answer
Installed OpenSSH binaries do not start a listener. Check sshd and then its network path. Authorized keys and host-key trust become relevant after transport reaches the server; an allow rule does not start a stopped SSH service.
Open this question’s page →Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
✓ Correct answer
PowerShell over SSH needs its configured subsystem even when ordinary SSH succeeds. WinRM is another transport, a password change does not define the missing subsystem, and -ComputerName selects the WSMan path rather than repairing SSH configuration.
Open this question’s page →Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
✓ Correct answer
The requested JEA hosting model is supported through Windows PowerShell endpoints over WSMan/WinRM. Current SSH remoting does not provide that endpoint-configuration/JEA model. A firewall rule alone is not a server or endpoint, and an RDP desktop does not impose the requested PowerShell role capabilities.
Open this question’s page →Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
✓ Correct answers
Expected host-key validation establishes server trust, and the correct account's key file with appropriate ACLs supports key authentication. WinRM TrustedHosts is separate; a different user's file does not authorize the intended user. Administrative accounts still need the correct configured key location and permissions.
Open this question’s page →Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
✓ Correct answer
NLA authenticates before the full remote session is established. A TLS certificate protects server identity/transport, while group membership and logon rights authorize access; those controls alone do not select the NLA pre-session authentication behavior.
Open this question’s page →Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
✓ Correct answer
The deny remote-logon right overrides an allow right. Group membership and name resolution do not remove that restriction. RDS licensing grace does not override security user-rights assignments. Review effective policy and the intended group scope.
Open this question’s page →Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
✓ Correct answer
Administrative RDP access is not a substitute for multiuser RDS application delivery and licensing. Disconnecting users or changing group membership does not create the required licensing entitlement. Azure Reader concerns control-plane visibility and does not change Windows desktop-service licensing.
Open this question’s page →Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment
✓ Correct answers
Ping proves neither the RDP listener/packet path nor authentication and authorization. Inspect those layers. Successful ICMP is already demonstrated; DNS does not explain this stated IP connection, and a resource display name does not prove RDP readiness.
Open this question’s page →Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
✓ Correct answer
Azure Arc represents the existing server for supported governance and extensions while it runs in place. Migration discovery, telemetry alone, or an unsupported extension target does not establish that Arc management representation.
Open this question’s page →Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
✓ Correct answer
The agent requires its own supported path to Azure service endpoints. A user display name or inbound RDP does not provide that path. Browser proxy settings alone do not configure the Connected Machine agent's effective proxy.
Open this question’s page →Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
✓ Correct answer
Arc management connectivity does not configure a guest telemetry pipeline. AMA plus a suitable DCR association collects the required counters. Heartbeats alone, an unconfigured AMA, and resource diagnostics alone do not establish the specified guest-counter collection.
Open this question’s page →Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
✓ Correct answers
Arc onboarding requires local installation permissions, appropriate Azure authorization and functional connectivity/time. Workload migration and DC promotion are not prerequisites. Copying an existing registration violates the need for a unique machine identity.
Open this question’s page →Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
✓ Correct answer
Audit reports guest state without applying it. Initial application with monitoring describes Apply and Monitor; automatic drift repair describes Apply and Autocorrect. Resource tag checks do not evaluate the stated guest TLS configuration.
Open this question’s page →Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
✓ Correct answer
Apply and Monitor establishes the configuration and observes subsequent drift. Audit does not provide the initial application; Autocorrect would repair drift without the requested separate approval. A resource tag check does not manage the guest setting.
Open this question’s page →Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
✓ Correct answer
Azure VM guest configuration needs its supported extension and system-assigned identity. A user-assigned identity alone is not that prerequisite; AMA is a telemetry agent, and tags do not install the guest configuration engine.
Open this question’s page →Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
✓ Correct answers
Azure VM prerequisites and the Arc agent’s included capability differ. Audit only reports, Apply and Monitor observes later drift, and resource metadata does not prove guest registry state. These distinctions prevent deploying the wrong prerequisites or assuming remediation occurred.
Open this question’s page →Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
✓ Correct answer
Check the Arc catalog and deployment requirements because support is not identical across execution environments. A matching name or ping response does not verify handler support. An on-premises server is not placed into an Azure VM availability set merely by Arc registration.
Open this question’s page →Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
✓ Correct answer
Protected settings are designed for sensitive handler input. Ordinary settings, names and tags can expose the secret through routine configuration access. Protected settings still require appropriate access control and logging hygiene; they are not a reason to broadcast secrets elsewhere.
Open this question’s page →Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
✓ Correct answer
The failure identifies a package path separate from the working Arc connection. Restore that path and inspect results/logs. Azure authorization, display names and heartbeat-only checks do not repair the unreachable package URL.
Open this question’s page →Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
✓ Correct answers
Use the Azure provisioning error and local execution evidence to isolate the fault. Connected does not certify each extension, handler upgrade is not OS patch installation, and broadly granting deployment rights adds privilege without diagnosing the failure.
Open this question’s page →Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
✓ Correct answer
Update Manager uses the guest’s configured update mechanism and source. It does not override WSUS with a universal Azure repository. Workspace data and resource tags are not operating-system update content repositories.
Open this question’s page →Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
✓ Correct answer
Customer Managed Schedules is the documented orchestration choice for scheduled VM patching. The alternative orchestration modes have different behavior and do not replace the required schedule prerequisites; extension-handler upgrades are distinct from OS patches.
Open this question’s page →Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
✓ Correct answer
The incomplete installation in a short window calls for installation details, elapsed time and servicing/reboot review. Assessment does not prove installation, handler upgrades are separate, and selection criteria do not explain completion once the server was already included.
Open this question’s page →Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
✓ Correct answers
Separate waves and health checks preserve and verify a surviving application path. Simultaneous restarts increase outage risk. Assessment does not prove post-installation availability, and ignoring required reboots can leave updates incomplete.
Open this question’s page →Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
✓ Correct answer
Runtime scope selection depends on its criteria such as tags. Correct and verify that membership. Classification, orchestration mode or manual assessment alone does not make a mismatched resource satisfy the dynamic tag criteria.
Open this question’s page →Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
✓ Correct answer
A configured worker executes through its own network and environment. The cloud sandbox does not inherit a laptop VPN; Arc registration alone does not create a worker. A worker without the required route still cannot reach branch-only shares.
Open this question’s page →Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
✓ Correct answer
Draft testing/saving is separate from publishing the version used by normal jobs. An open test pane does not publish it. Worker dependencies may be necessary but do not publish the intended runbook definition.
Open this question’s page →Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
✓ Correct answer
The enabled Automation account system-assigned identity takes precedence for the documented Arc-worker sign-in path. The Arc identity cannot replace it in this configuration, and the Automation account user-assigned identity is not supported for that hybrid flow. Windows System is the local execution context rather than the selected Azure identity.
Open this question’s page →Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
✓ Correct answers
Windows and Azure operations use separate authorization layers. Grant the actual identity the rights needed at each resource. Azure Contributor does not automatically grant domain SMB/NTFS rights, local administrator status does not grant Azure storage data access, and connectivity does not supply either authorization.
Open this question’s page →Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
✓ Correct answer
PowerShell can continue after nonterminating errors. Inspect the actual operations and error streams, and design failure handling to match the required outcome. Repeated execution without diagnosis can repeat a partial failure, and classifying every error as networking ignores the available evidence.
Open this question’s page →Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
✓ Correct answers
Deliberate authentication plus an explicit subscription context avoids accidentally using a previous worker session’s saved context. Assuming the previous subscription is correct is unsafe. Plaintext secrets and broad Owner permissions neither isolate the intended context nor satisfy least privilege.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
Enhanced Session Mode uses the Hyper-V path and supports local-drive redirection without guest IP connectivity. Network RDP requires a reachable guest IP. Basic VMConnect provides console access but lacks enhanced resource redirection, and full-screen basic display changes presentation rather than adding that feature.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
Use enhanced session mode requests the feature for that user and complements the already enabled host policy. Full-screen basic mode does not request redirection. An IP port-forwarding rule and access VLAN concern network RDP paths rather than the Hyper-V enhanced transport.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
The guest must be ready and have Remote Desktop Services enabled. Host policy does not automatically enable that guest service. A VM generation does not substitute for the service, and an external switch supplies networking rather than the missing session endpoint.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answers
Host permission and guest Remote Desktop Services are required; the user's enhanced-session setting must also be enabled. A public IP and an external switch are unnecessary for the Hyper-V transport. Shared AD-domain membership is not a general enhanced-session prerequisite; valid guest logon rights still matter.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
Invoke-Command with VMName uses PowerShell Direct on the local host to execute inside the guest. Get-VM queries host VM objects. Invoke-Command and Enter-PSSession with ComputerName rely on the guest's network remoting path, which is broken here.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
A persistent New-PSSession with VMName retains the Direct guest context and supports repeated session operations and file copying. Public IPs are unnecessary for Direct. Get-VM queries virtualization objects, and host rights do not replace valid guest credentials.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
PowerShell Direct targets a VM running locally on the host where the operation executes, so first accessing HV01 addresses placement. Opening guest WinRM or changing TrustedHosts concerns network remoting and does not change Direct's locality. Installing PowerShell 7 does not convert Direct into a cross-host discovery mechanism.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answers
Compatible socket endpoint/tooling and a test without guest networking verify the intended path. A TCP 22 test only verifies IP SSH. Linux PowerShell does not provide the Windows PowerShell Direct guest endpoint. Disabling host-key checking weakens authentication and does not create socket support.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
ExposeVirtualizationExtensions makes the CPU capability available to the middle VM. MAC spoofing concerns nested network traffic. Outer-host management tools do not expose guest CPU instructions, and a larger vCPU count alone does not enable nesting.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
Internal switching plus NAT presents the middle VM's reachable path to the surrounding network and needs inner-guest addressing. MAC spoofing conflicts with the stated constraint. A private switch alone has no external routing path. A memory ceiling does not establish connectivity.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
The AMD path requires the documented newer outer host OS and VM configuration. The Intel minimum is not the AMD rule. Upgrading only the guest or increasing vCPUs does not supply the required outer-host support and configuration version.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answers
The running nested hypervisor imposes the memory-change restriction, and NAT clients need correctly configured addressing and gateway. Dynamic Memory cannot vary that middle VM's memory normally in this state. New-NetNat creates translation rather than a DHCP scope, and exposing extensions does not install the Hyper-V role.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
Startup RAM must meet boot requirements; a high maximum only permits later growth. Dynamic Memory does not preallocate every maximum, its buffer is not a permanent maximum reservation, and priority governs relative host allocation rather than bypassing guest boot needs.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
The specified Dynamic Memory range matches boot, idle, and peak needs while allowing demand-based changes. Static 1 GB may not meet boot requirements and does not use Dynamic Memory buffer behavior. A maximum is not guaranteed reserved RAM. Static 6 GB stays fixed rather than ballooning to a minimum.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
Smart Paging is a constrained restart mechanism and does not substitute for failover capacity. It does not guarantee failover startup RAM, more paging-file space does not remove that physical requirement, and priority expresses relative preference rather than reserving every maximum.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answers
Demand versus assignment and host/guest paging evidence reveal allocation pressure. Maximum RAM is a ceiling rather than an allocation promise. Buffer is attempted extra memory, and priority neither proves sufficient capacity nor rules out an application leak.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
Heartbeat is the dedicated guest responsiveness signal. Guest Service Interface supports operations such as file copy, KVP exchanges metadata, and time synchronization coordinates clocks; none is the dedicated heartbeat indication.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
Guest Service Interface supports Copy-VMFile. Heartbeat reports responsiveness, shutdown coordinates a graceful guest stop, and backup/VSS integration coordinates consistency rather than this file-copy channel.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
Production consistency depends on healthy guest VSS writers and backup integration. Standard checkpoints capture memory instead of supplying the required production mechanism. Disabling backup integration does not repair writers, and file copying does not coordinate application quiescing.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answers
Integration functions need host configuration and supported guest implementation. KVP may fail separately from the network. Running state does not establish application health, Linux feature support varies, and PowerShell Direct still requires valid guest credentials.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
DDA gives one VM the complete assignable device and native driver access. GPU partitioning shares GPU fractions. Enhanced Session Mode redirects session resources, and Guest Service Interface supports integration tasks such as file copy; neither assigns a whole accelerator.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
Static memory, TurnOff, and dismount-before-assignment meet DDA's state and ownership requirements. Dynamic Memory and Save are unsupported. An active host-owned device cannot simultaneously be passed through. A guest driver cannot substitute for hardware isolation and assignability verification.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
The combined assigned devices need sufficient mapped-I/O address space plus overhead. Ordinary RAM alone does not change that mapping gap. Dynamic Memory is unsupported with DDA, and counting only one device can still leave the combined requirement unsatisfied.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answers
GPU pools can support restart placement in the documented clustered design, and DDA still dedicates the complete device. DDA does not support live migration or Dynamic Memory. Cluster membership does not establish device-class or hardware-vendor support.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
GPU partitioning supplies hardware-isolated fractions and supports qualifying Server 2025 live migration. DDA dedicates the whole device and blocks live migration. Enhanced sessions concern interactive resource redirection, while checkpoints capture recovery state; neither supplies the required shared accelerator design.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
Paravirtualization indicates driver capability without enabled SR-IOV, so firmware configuration is relevant. Ordinary VM RAM does not enable SR-IOV. DDA establishes a different whole-device ownership model, and unsupported partition counts do not correct firmware readiness.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
EPYC 7002 supports partitioning but not GPU-P live migration; qualifying DMA bit-tracking hardware is required. Increasing partition count or guest VRAM does not add that CPU capability. A GPU cannot simultaneously provide DDA and GPU-P.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answers
Homogeneous GPU configuration and qualifying hardware/drivers meet the documented migration requirements. Partition count must come from supported values. DDA does not provide live migration, and consumer GPU support cannot be inferred without a supported hardware/driver entry.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
ProductionOnly permits the production mechanism or failure, avoiding standard fallback. Production can fall back to Standard. Standard captures memory state, and Disabled prevents the required checkpoint altogether.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
Hyper-V removal coordinates the dependency chain and merges retained changes. Direct AVHDX deletion destroys part of that chain. A child depends on its parent, so detaching the parent is unsafe. Restoring discards or changes the intended current state rather than simply removing the no-longer-needed recovery point.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
ProductionOnly fails when production consistency cannot be obtained, matching the failed writer. It does not capture saved memory. External switching is not a checkpoint prerequisite, and a memory ceiling does not repair VSS writer failures.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answers
Standard checkpoint memory and the dependent disk chain explain recovery behavior. Checkpoints are not independent off-host copies. Production consistency still requires supported healthy guest applications/writers. Hyper-V-managed removal, rather than manual AVHDX deletion, performs supported merging.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
The cluster manages VM recovery and requires accessible storage and clustered roles. Independent hosts with inaccessible local files cannot recover those VMs automatically. Checkpoints supply local recovery state, and enhanced sessions provide access; neither creates failover orchestration.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
Add-ClusterVirtualMachineRole creates the cluster-managed VM role. Get-ClusterGroup inspects existing roles. Move-VM performs a supported VM move rather than registering a cluster role, and Checkpoint-VM creates a recovery point.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
Surviving-node RAM and compute capacity must accommodate the selected failure tolerance. A witness supplies quorum votes rather than VM memory. Live migration needs a functioning source, and checkpoint storage cannot supply required physical startup RAM.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answers
Planned migration transfers running state from a live source, while cluster failover restarts using accessible disks. Switch names must also map to correct networking. A cloud witness participates in quorum, and host clustering does not automatically implement application-level guest clustering.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
Disk capacity and partition size are separate, so extend the guest partition. Optimize-VHD reclaims eligible physical file space rather than extending a volume. Block size is not a partition-extension operation, and another differencing disk adds a dependency rather than growing the guest filesystem.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
The supported SCSI attachment provides the online resize path. IDE requires the VM to be offline, so VHDX format alone does not bypass controller constraints. Editing a parent behind an active checkpoint child risks the disk chain rather than supplying a valid online operation.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
A VHDX cannot be shrunk below its reported MinimumSize. Resize-VHD can shrink VHDX rather than VHD. Compaction does not automatically remove the virtual capacity boundary, and drive-letter changes do not alter the VHDX allocation/layout constraints.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answers
Differencing disks need parent data, and dynamic files grow with writes. Compaction targets eligible file space rather than automatically reducing guest capacity. A guest partition needs its own extension, and a virtual maximum does not guarantee physical host capacity.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
DHCP Guard restricts DHCP-server messages from the VM without being a blanket DHCP-client prohibition. Router Guard addresses unauthorized routing advertisements. MAC spoofing changes permitted source-MAC behavior, and port mirroring copies traffic for analysis rather than blocking rogue DHCP replies.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
The guest adapter needs the correct switch and its own access VLAN. A management OS VLAN setting does not automatically apply to guest adapters. An unrestricted trunk is unnecessary and needs guest tag handling. A Windows IP address cannot connect a disconnected virtual NIC.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
DHCP Guard blocks the very server messages this authorized VM must send. Router Guard addresses different traffic, and MAC spoofing does not remove DHCP Guard filtering. Trunk mode introduces VLAN-handling changes rather than correcting the identified guard rule.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answers
Port mirroring creates diagnostic copies, and permitted MAC spoofing allows the nested source addresses. DHCP Guard and Router Guard filter their respective traffic and do not create captures. Trunk mode controls VLAN tags, not authorization for different source MACs.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
SET integrates host uplinks and the vSwitch using switch-independent operation. Guest-only LBFO does not team host uplinks, and a single guest NIC cannot provide such a guest team. SET does not require LACP. Unrelated vSwitches alone do not implement a common teamed uplink.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
The multi-adapter New-VMSwitch with EnableEmbeddedTeaming creates the intended host SET. A private switch has no physical uplinks. AllowTeaming permits guest teaming rather than creating a host team. A switch on NIC1 alone does not supply the two-uplink embedded team.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
A common uplink remains a single failure boundary for both guest paths. Guest teaming does not survive host loss automatically. LACP is not a universal supported guest-teaming requirement, and another virtual IP does not create physical path independence.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answers
Matched adapters and correct switch-independent physical configuration meet SET's design. Aggregate bandwidth is not a single-flow guarantee. AllowTeaming affects guest adapters, and arbitrary dissimilar drivers/adapters do not meet SET compatibility requirements.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
Private switching connects attached VMs only. Internal also connects the host. Both external variants attach to a physical network; disabling management-OS sharing removes the host's shared adapter but does not isolate the VMs from that physical network.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
An Internal switch includes the host virtual adapter without a physical uplink. Private excludes host participation. NetAdapterName creates an external switch. VLAN configuration changes an adapter's tagging and does not create the required switch.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
Internal switching supplies local Layer 2 connectivity; external access needs routing/NAT and a usable gateway. Another isolated switch, a traffic permission alone, or a VLAN tag does not create the missing Layer 3 path.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answers
Sharing creates the host virtual-adapter path, and rebinding can disrupt the management session. AllowManagementOS does not configure NAT. An external uplink connects to the physical network. Host and guest adapter VLANs are separately configured.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
Replica maintains an asynchronous independent-site VM copy. A local cluster around source storage does not by itself create the remote copy. A source-volume checkpoint shares that volume's failure boundary. Live migration is a planned move from a healthy host, not an offline disaster-recovery replica.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
Certificate-based HTTPS encrypts the Replica transport. Kerberos authenticates HTTP but does not supply HTTPS encryption. Interval changes affect timing, and a Broker supplies cluster routing, not transport encryption by itself.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
Asynchronous replication cannot restore unsent changes, and fencing avoids competing copies. VM configuration does not contain all unsent transactions. Parallel activation creates conflict risk. Zero loss depends on a successful coordinated final transfer during planned failover, which is unavailable here.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answers
Test failover creates an isolated temporary copy for boot/application checks while primary operation and replication continue. A primary shutdown is a planned-failover step rather than required testing. The temporary test copy does not permanently replace the replica, and replication health alone does not validate recovery connectivity.
Open this question’s page →Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
✓ Correct answer
A persistent managed data disk provides storage independent of the temporary host-local lifecycle. Temporary/resource storage and allocation-local scratch paths are disposable. An ephemeral OS disk is intended for replaceable instances and is not an appropriate sole durable database copy.
Open this question’s page →Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
✓ Correct answer
Guest disk initialization and filesystem creation are separate from Azure attachment. Resizing the VM does not create a filesystem, host caching does not format it, and changing LUN does not automatically create the guest volume.
Open this question’s page →Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
✓ Correct answer
A VM-size throughput ceiling requires an appropriate compatible VM capacity or workload redesign. Disk capacity alone does not remove that ceiling. Premium SSD v2 has no host caching support. A temporary disk cannot preserve the required durable data model.
Open this question’s page →Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
✓ Correct answers
The two disk classes are data-only, and expansion still needs guest partition work. Separate snapshots do not guarantee multi-disk consistency. ZRS provides disk redundancy rather than VM replicas. Ordinary managed-disk shrinking is unsupported; migrate to a smaller disk when required.
Open this question’s page →Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
✓ Correct answer
A scale set supplies horizontal instance orchestration and autoscale; load balancing directs traffic across healthy instances. A larger single VM is vertical capacity without automatic instance scaling. An availability set controls placement, and disk snapshots preserve recovery data rather than manage instance counts.
Open this question’s page →Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
✓ Correct answer
Deallocation may be required to place the VM on hardware offering the target size. Guest configuration cannot change Azure's allocated SKU. Disk capacity does not expose another hardware family, and an availability set does not replace the required resize/placement workflow.
Open this question’s page →Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
✓ Correct answer
Stopped can retain compute allocation whereas Deallocated releases it. A clean guest shutdown or flushed disk writes does not deallocate the Azure resource. Persistent disk charges can continue after deallocation and do not prove allocated compute remains.
Open this question’s page →Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
✓ Correct answers
Resize must fit quota and supported resources, and horizontal scaling needs an explicit state design. Autoscale does not automatically copy local databases. Flexible uses standard VM objects/APIs rather than only Uniform's child APIs. Deallocation can lose temporary data.
Open this question’s page →Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
✓ Correct answer
Multiple instances across zones provide the intended physical separation when application failover is configured. One zonal VM is not automatically replicated. A single fault domain shares infrastructure, and a larger single VM remains one application instance.
Open this question’s page →Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
✓ Correct answer
An availability set distributes the VMs across infrastructure and maintenance groups. Deliberate co-placement increases shared failure exposure. Disk ZRS does not supply VM placement or running application instances. Static IP allocation stabilizes addresses rather than isolating hardware.
Open this question’s page →Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
✓ Correct answer
Clients need a load-balancing or application/client failover path to the surviving instance. Update-domain settings, disk redundancy, or more capacity on an unselected VM do not redirect requests from the failed address.
Open this question’s page →Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
✓ Correct answers
Fault domains and zones define their respective infrastructure boundaries. VM replicas and application-data replication require explicit designs. Zones remain inside one region, so they do not by themselves provide cross-region recovery.
Open this question’s page →Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
✓ Correct answer
Bastion reaches private VM IPs through a managed RDP/SSH service. JIT controls time-limited port access but does not create the connection path. Public VM IPs conflict with the stated design, and availability sets govern placement rather than remote-session transport.
Open this question’s page →Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
✓ Correct answer
Premium includes native-client capabilities and private-only deployment. Basic lacks the required advanced native-client features, Developer uses a shared development model, and Standard provides native-client capabilities but not Premium's private-only deployment feature.
Open this question’s page →Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
✓ Correct answer
JIT permits a network window while guest authentication and logon rights remain required. It does not assign Remote Desktop Users membership, turn an NSG rule into a credential, or grant OS rights through a longer window.
Open this question’s page →Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
✓ Correct answers
Effective rules determine whether JIT restrictions work, and guest service/authentication prerequisites remain necessary. JIT does not create routes, Bastion does not bypass guest authentication, and deployment requirements vary by Bastion tier and private-only design.
Open this question’s page →Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
✓ Correct answer
Azure NIC static allocation establishes the supported predictable address. Guest-only arbitrary addressing can conflict with platform provisioning. Dynamic allocation is not guaranteed sequential, and reserved addresses cannot be assigned to the VM.
Open this question’s page →Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
✓ Correct answer
Both associated NSGs must allow the flow; the NIC deny still blocks it. One NSG's allow cannot override the other. DNS suffix does not repair an explicit IP/port deny, and unrelated outbound traffic does not authorize a new inbound flow.
Open this question’s page →Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
✓ Correct answer
The new private-subnet default requires explicit outbound connectivity to public endpoints. Private DNS can resolve names but cannot create egress. Another NIC without a routing/translation plan adds no Internet path. Inbound RDP permission is unrelated to the required outbound update flow.
Open this question’s page →Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
✓ Correct answers
Forwarding is configured at Azure NIC and guest layers, and paths must exist in both directions. Guest-only configuration does not replace NIC forwarding settings. Peering is not automatically transitive, and DNS resolution alone establishes neither routes nor security permissions.
Open this question’s page →Networking · Networking | Implement on-premises and hybrid name resolution
✓ Correct answer
AD integration supplies directory replication, multi-master writable replicas, and secure updates. File-backed secondaries are read-only. A stub holds authority-locator records rather than a full writable database. A conditional forwarder routes queries rather than hosting the AD records.
Open this question’s page →Networking · Networking | Implement on-premises and hybrid name resolution
✓ Correct answer
ForestDnsZones provides the forest-wide directory scope. DomainDnsZones limits the application-partition scope to one domain. A local zone file and workstation caches do not supply forest-wide AD zone replication.
Open this question’s page →Networking · Networking | Implement on-premises and hybrid name resolution
✓ Correct answer
Secure updates enforce identity and ownership, so aligned authorized DHCP credentials and ACL review address the cause. Anonymous writes weaken the stated security requirement. TTL governs caching rather than write permissions, and stub zones are not complete writable record stores.
Open this question’s page →Networking · Networking | Implement on-premises and hybrid name resolution
✓ Correct answers
AD replication and secure update support are core properties. Writable directory-backed hosting requires an eligible DNS domain controller and relevant partition. Separate zone transfers are not the required AD replica path. DomainDnsZones is domain-scoped rather than forest-wide.
Open this question’s page →Networking · Networking | Implement on-premises and hybrid name resolution
✓ Correct answer
A secondary receives the full read-only zone copy through transfers. A stub retains authority-locator records, a conditional forwarder routes queries, and an independent primary creates a separate writable authority rather than the requested synchronized read-only copy.
Open this question’s page →Networking · Networking | Implement on-premises and hybrid name resolution
✓ Correct answer
CNAME points the alias to the canonical name so that target resolution determines the address. PTR is for reverse mapping, NS identifies zone authority, and an A record stores an IPv4 address rather than a DNS-name target.
Open this question’s page →Networking · Networking | Implement on-premises and hybrid name resolution
✓ Correct answer
Older data at the authoritative secondary points to its transfer path and state. Client caches do not explain that server's stored older records, and TTL is caching behavior rather than database synchronization. A secondary is read-only and cannot be repaired by treating it as the writable update authority.
Open this question’s page →Networking · Networking | Implement on-premises and hybrid name resolution
✓ Correct answers
A maps IPv4 and PTR supports reverse names. AAAA maps IPv6, CNAME is an alias rather than a zone copy, and NS identifies authoritative name servers; DNSSEC RRSIG holds signatures.
Open this question’s page →Networking · Networking | Implement on-premises and hybrid name resolution
✓ Correct answer
A conditional forwarder chooses targets by suffix while preserving other paths. A general forwarder changes broader recursive behavior. An empty primary makes this server authoritative and may return terminal negatives. Hosts-file entries do not provide maintainable suffix-based DNS forwarding.
Open this question’s page →Networking · Networking | Implement on-premises and hybrid name resolution
✓ Correct answer
Set-DnsServerForwarder configures the general upstream resolver path. Creating a primary zone changes authority, an A record maps a name to an address, and clearing cache removes stored answers without configuring upstream targets.
Open this question’s page →Networking · Networking | Implement on-premises and hybrid name resolution
✓ Correct answer
Local authority determines the result for its namespace, and NXDOMAIN is terminal. It is not the same as a timeout. A general forwarder does not override hosted authority, and a DNS-server alias does not change the query-resolution precedence.
Open this question’s page →Networking · Networking | Implement on-premises and hybrid name resolution
✓ Correct answers
Fallback needs permitted recursion/root-hint behavior and remaining time after applicable forwarders are exhausted. Terminal authoritative negatives are not simply discarded. Identical hosted-zone and conditional-forwarder names cannot coexist, and reverse zones are not required for normal forward Internet resolution.
Open this question’s page →Networking · Networking | Implement on-premises and hybrid name resolution
✓ Correct answer
The inbound endpoint listens for queries into Azure and resolves in the linked context. Outbound endpoints send rule-selected queries out. The special Azure resolver address is not a directly routed on-premises endpoint, and a ruleset link alone does not provide an inbound listener.
Open this question’s page →Networking · Networking | Implement on-premises and hybrid name resolution
✓ Correct answer
The outbound endpoint, suffix rule and ruleset links establish Azure-to-on-premises DNS forwarding. Inbound alone serves queries arriving into Azure. An empty hosted private zone does not fetch on-premises authoritative records; connectivity alone does not configure the DNS path.
Open this question’s page →Networking · Networking | Implement on-premises and hybrid name resolution
✓ Correct answer
The missing DNS forwarding path explains the different resolution context; verify the correct service suffix and linked private data. An outbound endpoint is not the inbound listener. Replacing private data with public addresses defeats the private requirement. Network connectivity alone does not route DNS queries to the proper resolver.
Open this question’s page →Networking · Networking | Implement on-premises and hybrid name resolution
✓ Correct answers
Zone links select private authoritative resolution context, while ruleset links expose forwarding rules; custom servers must forward appropriately. Peering does not automatically publish private zones, the resolver does not build the VPN, and DNS correctness does not grant application access.
Open this question’s page →Networking · Networking | Implement on-premises and hybrid name resolution
✓ Correct answer
Policies can select scope-specific records by appropriate source/interface criteria. TTL changes caching rather than source-specific answers. PTR is reverse mapping, and a general forwarder does not implement authoritative scoped answers for the same hosted name.
Open this question’s page →Networking · Networking | Implement on-premises and hybrid name resolution
✓ Correct answer
The policy must reference existing criteria and authoritative scoped data. A default record does not automatically create another scope. Recursion scopes hold recursion settings rather than authoritative record sets. Nondefault scopes do not support the default-scope scavenging/dynamic-update workflow.
Open this question’s page →Networking · Networking | Implement on-premises and hybrid name resolution
✓ Correct answer
Scoped records can replicate through AD while query policies remain local. ForestDnsZones does not replicate those policy definitions. Identical data does not guarantee identical handling, and TTL controls caching rather than policy deployment.
Open this question’s page →Networking · Networking | Implement on-premises and hybrid name resolution
✓ Correct answers
Unmatched clients need suitable default behavior, and cached answers influence observed weight distribution. DNS weights do not provide application health probes. Dynamic updates apply to the default scope, and forwarding can make the authoritative server see the forwarder's source rather than the original client's subnet.
Open this question’s page →Networking · Networking | Implement on-premises and hybrid name resolution
✓ Correct answer
DNSSEC signs data for authenticity and integrity validation. Secure dynamic updates authorize record modification rather than validating received answers. TTL and aliasing do not add cryptographic answer validation.
Open this question’s page →Networking · Networking | Implement on-premises and hybrid name resolution
✓ Correct answer
The parent DS connects the trusted delegation to the child's key. TTL does not authenticate delegation. A published child DNSKEY or newly signed child records still leave the stated parent-to-child trust chain incomplete.
Open this question’s page →Networking · Networking | Implement on-premises and hybrid name resolution
✓ Correct answer
DnssecOk requests DNSSEC data; trust-chain validation and required policy must be checked. It does not encrypt traffic. An untrusted or invalid signature is not proof of authenticity, and nslookup is not an equivalent DNSSEC-aware enforcement test.
Open this question’s page →Networking · Networking | Implement on-premises and hybrid name resolution
✓ Correct answers
RRSIG supplies signatures and NSEC/NSEC3 prove nonexistence. DNSSEC does not encrypt queries. Update authorization does not replace answer validation, and parent delegation/trust publication requires its own process.
Open this question’s page →Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
✓ Correct answer
A relay forwards the initial DHCP requests across the routed boundary and supplies subnet context. DNS forwarding and PTR records handle name resolution, not DHCP broadcast delivery. A shorter lease affects timing rather than making routers forward broadcasts.
Open this question’s page →Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
✓ Correct answer
Add-DhcpServerInDC registers DHCP authorization. Scope creation defines an address pool, option configuration supplies client settings, and lease inspection reads assignments; none performs AD authorization.
Open this question’s page →Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
✓ Correct answer
The identified inactive scope must be made usable and checked for capacity/options. DNS TTL does not activate DHCP. Reservations are scope settings and do not automatically activate it. Network reachability does not remove the domain authorization requirement.
Open this question’s page →Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
✓ Correct answers
Clients need matching active scopes and relay/transport reachability. Role installation does not build scopes. AD authorization is a Windows DHCP directory control rather than a universal network firewall, and VPN connectivity does not automatically implement broadcast relay.
Open this question’s page →Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
✓ Correct answer
Link-local addressing suggests lease acquisition failed but does not isolate the cause. It does not prove DNS corruption or a VPN failure. A reservation only works when the matching DHCP client can obtain its lease; it does not guarantee routed addressing during acquisition failure.
Open this question’s page →Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
✓ Correct answer
IP flow verify tests the applicable TCP/UDP security decision and identifies matching rules. DNS lookup verifies name data, Running verifies VM allocation/state, and disk listings concern storage; none evaluates the specified NSG flow.
Open this question’s page →Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
✓ Correct answer
IP failure beyond the subnet points toward gateway/routing/security and return-path evidence. TTL, a forward record, and PTR creation concern names and do not repair a failed routed connection when the destination IP is already known.
Open this question’s page →Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
✓ Correct answers
Application-port/listener tests and bidirectional routes address the remaining connectivity layers. DNS only supplies the address. Reserved Azure addresses cannot be assigned, and ICMP failure is not conclusive evidence about TCP.
Open this question’s page →Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
✓ Correct answer
Exclusions explicitly remove those addresses from dynamic offers. Reverse DNS maps addresses to names. A shorter lease does not prohibit duplicate allocation of static infrastructure addresses. A superscope groups scopes rather than excluding addresses.
Open this question’s page →Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
✓ Correct answer
Option 006 selects the DNS resolvers needed for AD records. Option 003 supplies a gateway address, not a domain-name resolver. Option 015 supplies a suffix but does not replace the DNS server list. Lease duration does not choose the resolver.
Open this question’s page →Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
✓ Correct answer
Superscopes represent a multinet scope grouping; network segmentation and routes must be designed separately. They do not tag packets, are not DNS directory partitions, and adding address ranges does not create router interfaces.
Open this question’s page →Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
✓ Correct answers
Option 003 provides the gateway and 006 the DNS server list. Option 015 supplies a domain suffix rather than resolver addresses. Exclusions restrict pool addresses; superscope labels do not create routes.
Open this question’s page →Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
✓ Correct answer
A reservation preserves DHCP leasing/options for the matching client. A manual static IP disables the requested lease workflow. DNS records do not select a lease, and an exclusion alone stops ordinary offers without assigning the address to this device.
Open this question’s page →Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
✓ Correct answer
Add-DhcpServerv4Reservation binds the address to ClientId. An exclusion only withholds an address from dynamic offers. Router option configuration supplies a gateway. Add-DhcpServerInDC registers server authorization rather than reserving a client's address.
Open this question’s page →Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
✓ Correct answer
The reservation matches the request's identifier, which changed with the NIC. DNS TTL and gateways do not define that match. The descriptive printer/reservation name is not a substitute for the configured ClientId.
Open this question’s page →Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
✓ Correct answers
Reservations still use DHCP and require identifier matching. They do not remove acquisition/renewal dependencies. Exclusions only restrict pool use, and reverse DNS is not the client identifier used for reservation selection.
Open this question’s page →Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
✓ Correct answer
Hot standby matches active local service backed by a standby partner. Load balance normally distributes client service across both partners. One scope supports only two partners, and the described Windows failover protocol does not support DHCPv6 scopes.
Open this question’s page →Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
✓ Correct answer
Later scope configuration changes need explicit replication from the desired source. Automatic lease synchronization is not the same operation. Deleting a lease database removes state rather than safely copying settings, and different DNS credentials can break secure record updates.
Open this question’s page →Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
✓ Correct answer
The client relay needs a path to the surviving DHCP02. MCLT governs lease timing, not routing. Server-to-server failover communication and a larger reserve cannot deliver client requests whose relay still targets only the failed endpoint.
Open this question’s page →Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
✓ Correct answers
Communication failure must be diagnosed, and safe takeover timing/ownership prevent conflicting leases. Immediate unrestricted pool reuse risks duplicates. Communication Interrupted does not prove a dead partner, and a single scope cannot join a three-partner failover relationship.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Azure Files
✓ Correct answer
Direct Azure Files supplies the managed SMB endpoint. File Sync adds Windows Server synchronization; DFS Replication requires file servers; an iSCSI LUN supplies blocks and needs a file server to expose SMB.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Azure Files
✓ Correct answer
Private-link DNS must send the normal file endpoint name to its private IP. ACL inheritance concerns authorization after connection; signing governs SMB security negotiation; redundancy does not correct client DNS.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Azure Files
✓ Correct answer
Moving between HDD and SSD requires a new share and migration. HDD access tiers are not an SSD conversion; ZRS changes redundancy; cloud tiering manages a server cache.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Azure Files
✓ Correct answers
Direct SMB requires TCP 445 and correct private-endpoint DNS/routing. Azure Files does not offer the Windows Server SMB-over-QUIC transport; File Sync endpoints are optional; Azure manages the share filesystem.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Azure Files
✓ Correct answer
The share gate limits access to reading even when Modify allows more. File ACLs cannot expand the share role; Reader does not grant ACL administration; differing levels are not inherently a denial.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Azure Files
✓ Correct answer
Elevated Contributor permits permission changes when the file ACL also authorizes them. Resource Reader provides management visibility; SMB Reader cannot modify permissions; Contributor with Read ACL cannot administer ACLs.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Azure Files
✓ Correct answer
The storage-account application must be excluded from applicable MFA requirements for this flow. A tenant-wide exclusion is unnecessary; a second identity source is unsupported; subscription Owner does not fix ticket issuance.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Azure Files
✓ Correct answers
User-specific share roles target Entra representations of AD identities, and ACLs also apply. Only one user identity source is enabled; management Contributor is not SMB data access; SAS is not an SMB user authentication replacement.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Azure Files
✓ Correct answer
File Sync provides server endpoints and cloud tiering. A snapshot is a recovery view; a DFS namespace only provides referrals; the iSCSI proposal does not provide this supported synchronization/cache design.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Azure Files
✓ Correct answer
The cloud endpoint storage account must be in the storage sync service region. Relocating only the Windows server, changing the share access tier, or adding a server endpoint does not change the incompatible cloud endpoint location.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Azure Files
✓ Correct answer
An 80 percent free-space target permits much less local cached data. It is not a cached-file percentage; tiering retains cloud content; free-space pressure takes priority over the date policy.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Azure Files
✓ Correct answers
Cached files remain local; tiered files need recall connectivity. Local backup can omit or recall placeholders; tiering preserves cloud content; File Sync server endpoints require NTFS.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Azure Files
✓ Correct answer
Endpoint errors and progress distinguish communication health from file synchronization. Resource-group availability is not per-file evidence; Online is insufficient; a namespace display name does not report sync results.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Azure Files
✓ Correct answer
The server-online metric and server dimension detect communication loss, and an action group routes notification. Per-file errors measure a different condition; capacity measures storage use; an action group without an alert condition cannot detect the outage.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Azure Files
✓ Correct answer
An advancing count shows real progress, though throughput and item failures still merit monitoring. Duration alone does not justify re-registration; Online does not clear errors; progress is not evidence of an unsupported filesystem.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Azure Files
✓ Correct answers
Scanners and cache settings can drive recall and pressure. Online concerns communication, not recall outcomes; sync uses TCP HTTPS; share quota alone does not explain endpoint recall behavior.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Azure Files
✓ Correct answer
DFS Namespaces preserves the logical UNC path and referrals. DFS-R supplies replication rather than that namespace. Local drive letters do not preserve the domain UNC, and a snapshot is a data recovery view rather than a namespace root.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Azure Files
✓ Correct answer
The initial endpoint uploads the complete dataset with tiering disabled. Immediate tiering and concurrent overlapped members do not follow the transition; a DFS-R read-only folder is unsupported.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Azure Files
✓ Correct answer
DFS target configuration and cached referrals determine which server the logical path returns. Successful File Sync upload does not update every namespace target. Cache policy and cloud access tier affect data placement/performance rather than referral selection.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Azure Files
✓ Correct answers
Convergence and namespace user tests establish data and access readiness. Copying does not recreate every share setting; premature seed removal risks incomplete data; dual replication is not a safe default rollback design.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Azure Files
✓ Correct answer
RoboCopy can migrate Windows shares over SMB. DFS Namespaces supplies referrals; Storage QoS manages I/O; key escrow protects encryption recovery and does not migrate data.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Azure Files
✓ Correct answer
A write freeze and final delta capture accepted source changes before redirection. Preserved timestamps alone do not prove those changes were copied. Repeated passes during continuing writes do not establish a final consistent cutover, and mapped-drive changes do not transfer missing data.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Azure Files
✓ Correct answer
Code 3 can combine copied files and extra files; it is below the failure threshold of 8. Nonzero is not automatically fatal, and copy success proves neither share configuration nor a need to reformat.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Azure Files
✓ Correct answers
Metadata assessment and a reconciliation-aware rollback plan protect fidelity and accepted writes. Azure Files does not reproduce every NTFS feature; copy counts do not prove effective access or application readiness; copying does not assign Azure RBAC.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Windows Server file shares
✓ Correct answer
Share Read limits remote access to reading. NTFS cannot expand that gate; ordinary reading rights do not administer shares; hidden naming has no permission effect.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Windows Server file shares
✓ Correct answer
Access-based enumeration filters visible entries using access. Hidden naming only affects browsing of the share itself; caching changes offline behavior; a broad grant does not selectively hide project folders.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Windows Server file shares
✓ Correct answer
Open SMB/application handles can explain a workbook-specific sharing violation. A share that allows creating files is not simply read-only for all operations. Enumeration controls visibility, and the hidden-name suffix does not release a lock.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Windows Server file shares
✓ Correct answers
Folder ACLs and group-based share access provide the two authorization gates. A hidden name is not security; share creation does not replace all file ACLs; blanket volume ownership is unnecessary and expands control.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Windows Server file shares
✓ Correct answer
A hard folder quota enforces the tree limit across owners. A soft quota only measures/notifies; a per-user quota follows ownership; enumeration controls visibility rather than capacity.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Windows Server file shares
✓ Correct answer
Auto-apply creates individual template-based subfolder quotas. One parent quota combines all users; screens match filenames; namespace targets do not enforce storage limits.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Windows Server file shares
✓ Correct answer
FSRM's supported filesystem is NTFS. A drive letter, resilient layout, or deduplication does not change FSRM's ReFS support boundary.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Windows Server file shares
✓ Correct answers
Passive screening plus reporting observes behavior without blocking. Active screening enforces a block; extension rules do not inspect safety; FSRM screening does not replace folder authorization.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Windows Server file shares
✓ Correct answer
DFS Namespaces provides referrals and a logical path. DFS-R copies files; Storage Replica copies volume blocks; S2D pools cluster storage. None of those alone creates the namespace.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Windows Server file shares
✓ Correct answer
Targets need consistent coordinated content and permissions. DFS-N does not replicate; drive letters do not coordinate data; namespace servers generally refer clients rather than proxy each file operation.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Windows Server file shares
✓ Correct answer
Repeated staging cleanup under churn calls for staging capacity, free space, and backlog review. Namespace availability and referral caching concern DFS-N rather than DFS-R staging. The initial primary member is not a permanent write master.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Windows Server file shares
✓ Correct answers
DFS-N routes clients and DFS-R synchronizes suitable folders. DFS-R has no distributed document lock; targets alone do not synchronize; the initial primary member is not a lasting write master.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Windows Server file shares
✓ Correct answer
Server 2025 Standard supports QUIC over UDP 443 with TLS. SMB Direct is RDMA for suitable networks; File Sync is synchronization, not the client transport; SMB1 over TCP 443 is not this feature.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Windows Server file shares
✓ Correct answer
New-SmbMapping with QUIC exercises the intended UDP transport and SMB access. Test-NetConnection tests TCP; share-access inspection is local permission evidence; RDMA inspection concerns SMB Direct.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Windows Server file shares
✓ Correct answer
Renewal changes the certificate thumbprint, so mapping must reference the new valid certificate. Share ACLs do not select the tunnel certificate. RDMA belongs to SMB Direct, and Server 2025 Standard already supports QUIC.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Windows Server file shares
✓ Correct answers
The server certificate and UDP transport are core requirements. RDMA belongs to SMB Direct; client certificates are an optional admission layer; user authentication and ACLs remain required.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Windows Server file shares
✓ Correct answer
Encryption protects confidentiality. Signing authenticates message integrity; enumeration changes visibility; a hidden name only affects browsing and does not encrypt traffic.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Windows Server file shares
✓ Correct answer
Get-SmbConnection reports active negotiated connection details. Client configuration lists local settings rather than proving a particular negotiated dialect, share access lists permissions, and RDMA inspection establishes adapter capability rather than SMB dialect.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Windows Server file shares
✓ Correct answer
Kerberos service tickets depend on correct name/SPN identity, explaining a new-alias failure after NTLM blocking. Dialect range, signing, and session timeout do not create the missing Kerberos service identity.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Windows Server file shares
✓ Correct answers
Multichannel discovers RDMA, and Server 2022 or later supports encrypted direct placement. Signing alone is not confidentiality; the historical blanket encryption limitation is obsolete; cloud tiering is unrelated.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answer
GPT supports the large disk. Conventional MBR has about a 2-TiB addressability limit. NTFS formatting and drive-letter assignments do not remove that partition-table address limit.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answer
After the disk exposes extra capacity, the intended partition/filesystem still needs extension. A rescan discovers capacity but does not guarantee extension; compaction reclaims eligible file allocation; another partition does not enlarge the existing volume.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answer
Thin free space is logical, while the full backing pool cannot allocate more physical storage. Advertising more virtual capacity or extending logical limits does not add the required physical pool capacity.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answers
Identity and ownership checks prevent acting on the wrong disk or shared owner. Disk numbers alone are insufficient; RAW can indicate damaged existing data rather than empty media; mount points can replace drive letters.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answer
Simple provides striping without redundancy and fits reproducible scratch data. Mirrors and parity reserve capacity for protection; parity is not overhead-free.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answer
A suitable mirror protects against a drive failure with good write behavior. Simple layouts lack redundancy regardless of provisioning; a quota limits consumption but does not protect data.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answer
The repair job reports reconstruction still in progress. Mounted access, a newly added disk, or one device's healthy status does not prove virtual-disk redundancy has already been restored.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answers
Placement requirements and repair headroom determine safe growth. Thin logical space omits physical availability; mirrors consume extra copies; resiliency does not protect against replicated deletion or all disasters.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answer
Hyperconverged S2D combines storage and compute on the same nodes. Disaggregated S2D separates compute hosts. Conventional single-server Storage Spaces does not pool local drives across cluster nodes, and a SAN-only design uses external shared storage instead.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answer
Validation checks prerequisites before enablement. Roles alone do not validate hardware; network preparation precedes deployment; a mirror does not replace cluster quorum.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answer
Current fault placement, repairs and quorum determine safe maintenance. Copy count alone is insufficient; removing witness can reduce voting resilience; a VM heartbeat does not verify storage repair.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answers
Datacenter and validated hardware/networking are required. S2D uses local drives rather than requiring a SAN; ReFS is not bootable; DFS namespaces do not supply the S2D cluster.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answer
Synchronous replication waits for remote log persistence. Asynchronous mode can lose recent writes; DFS-R waits for file closure; weekly copies have a large recovery-point gap.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answer
The Standard volume limit applies to replicated data volume size. A small log, DFS namespace or asynchronous mode does not remove the edition restriction.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answer
A growing asynchronous queue indicates changes arrive faster than the link or destination can persist them. Block replication does not wait for file closure. Quotas do not add throughput, and changing mode does not remove the physical capacity bottleneck.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answers
Topology testing and proper volume/log preparation support the design. Writable independent destination use conflicts with block replication; harmful changes replicate; automatic application recovery requires an additional supported failover design.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answer
Deduplication consolidates repeated chunks. Enumeration controls visibility; signing protects traffic integrity; a namespace routes users without consolidating storage.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answer
Each possible owner needs deduplication support. Current-owner-only installation fails after ownership changes; client or namespace roles do not supply the owning node filesystem filter.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answer
Disabling does not expand existing optimized files; supported unoptimization does. Garbage collection reclaims unreferenced chunks, while scrubbing checks integrity rather than expanding all content.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answers
Optimization is background work and expansion needs capacity. Garbage collection reclaims unused chunks, not feature disablement; dedup does not extend FSRM filesystem support; storage savings do not verify backups.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answer
SMB Direct uses RDMA for efficient storage traffic. QUIC secures remote SMB transport; DFS-R copies files asynchronously; classification assigns file properties rather than changing data transport.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answer
Multichannel discovers RDMA paths; disabling it disables SMB Direct. RDMA is not negotiated independently; QUIC is a different configured transport; filesystem read-only state is unrelated.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answer
RDMA byte counters show actual Direct transfer. Capability alone does not prove use. Multichannel can also use TCP, and speed/CPU observations are suggestive rather than conclusive transport evidence.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answers
Both RDMA endpoints and Multichannel are required. Modern Server versions support encrypted direct placement; UDP 443 belongs to QUIC; ordinary guest vNICs do not inherit RDMA automatically.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answer
Aggregated shares one allocation across assigned flows. Dedicated provides independent VM/disk groupings; an NTFS quota limits bytes; PFC controls network flow behavior rather than VM disk IOPS.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answer
256 divided by 8 equals 32. One applies only to an I/O no larger than the normalization size; 8 confuses the unit size with count; 256 counts KiB rather than 8-KiB units.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answer
The disk references a policy GUID in the relevant storage system. A matching display name with another GUID does not satisfy that reference. A byte quota governs capacity, and free bytes do not establish a valid QoS policy.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answers
Physical performance and competing demand explain unmet reservations. Raising a number cannot create capacity; share permissions govern access; free bytes do not prove available IOPS or latency.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answer
Both File Sync and FSRM require NTFS. ReFS integrity and deduplication do not add those service requirements; FAT32 lacks the supported endpoint and quota environment.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answer
Resilient Storage Spaces supplies alternate copies for ReFS repair. A single unprotected copy cannot guarantee reconstruction; a DFS root and a quota do not provide a verified good data copy.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answer
Current ReFS does not support shrinking. Optimization and repair do not add that filesystem capability, and adjacent unallocated space does not remove the restriction; use a supported migration for a smaller layout.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answers
NTFS can boot Windows and ReFS can use BitLocker. DFS-R and FSRM require NTFS; mirroring does not change FSRM support; checksums detect damage but need recoverable data to repair it.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answer
iSCSI presents a LUN as a disk. SMB supplies file access; DFS Namespaces provides referrals; File Sync synchronizes files and does not present remote SCSI blocks.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answer
Initiator startup and persistent sessions control restart reconnection. Successful manual authentication already establishes that the credentials can work. A portal entry alone is not a saved persistent connection, and a drive letter cannot create the absent block-storage session.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answer
MPIO coordinates supported independent paths to the same device. Extra uncoordinated sessions and NIC teaming alone do not implement storage multipath ownership/failover. A descriptive target name does not control path recovery.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answers
CHAP and MPIO address authentication and path coordination respectively. IQNs are identifiers; ordinary NTFS cannot accept uncontrolled multi-host writes; target authorization is distinct from SMB share permissions.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answer
BitLocker protects locked data at rest. Signing protects network message integrity; enumeration and hidden names only affect access presentation and do not encrypt an offline disk.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answer
Full-volume encryption covers existing free sectors. Used-space-only encryption can leave old plaintext remnants until overwritten. Suspension changes protector enforcement without performing free-sector encryption, and ACLs do not encrypt deleted offline sectors.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answer
Temporary suspension with resumption handles an approved boot change. Permanent decryption removes at-rest protection; suspension does not prove escrow; filesystem choice does not resolve boot measurements.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answers
Protector/policy planning and verified escrow establish usable recovery. ACLs cannot substitute for decryption keys; conversion success is not escrow evidence; transport encryption protects a different layer.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answer
The recovery ID links the prompt to the corresponding protector record. Hostname, user display name and share name do not distinguish historical protectors.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answer
repair-bde can salvage data with matching package plus password/key to a separate safe target. A package alone is insufficient; ownership is not decryption; copying encrypted blocks alone does not reconstruct damaged BitLocker metadata.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answer
EFS needs the appropriate private key. BitLocker volume unlocking is a different layer, the public certificate alone cannot decrypt, and ownership or ACL administration does not provide decryption key material.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answers
Classifying the layer and preserving matching key material support correct recovery. TPM clearing does not recreate lost keys; RAW can be storage/filesystem damage; permanent disablement does not investigate the trigger.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answer
DEP targets execution from data-marked memory. ASLR randomizes layout; CFG restricts indirect calls; App Control publisher rules select trusted software rather than enforcing memory-page behavior.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answer
The full path scopes the program setting to its intended executable. A shared name or system-wide default broadens the affected programs. A firewall rule does not configure process mitigations.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answer
Events and reproduction identify the specific compatibility issue and permit a narrow exception. Blanket disablement abandons unrelated protection; policy application does not establish workload compatibility. Audit support varies by mitigation.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answers
Workflow testing and readable deployment XML support functional rollout. Audit availability is mitigation-specific, and publisher approval does not establish compatibility with process restrictions.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answer
Audit records would-block behavior without preventing code execution. Enforcement can disrupt unapproved software; a firewall rule controls traffic, and Credential Guard protects supported secrets rather than evaluating code trust.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answer
Hash rules identify specific file content; updates change that content. A hash rule does not imply a publisher rule or approval of every future version. A signature identifies the signer but still must satisfy the effective policy's allowed trust rules.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answer
OSConfig maintains desired policy and can restore manual removals. Audit is an execution mode rather than policy-removal authorization. AppLocker rules are a separate policy model, and user tokens do not redeploy code-integrity policy files. Use the OSConfig removal scenario to change desired state.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answers
Audit review and policy/workflow verification identify functional allow-rule requirements. AppLocker approval is independent, and the documented OSConfig App Control workflow requires Windows Server 2025.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answer
Eligible domain-joined non-DC Server 2025 systems default to Credential Guard without UEFI lock. It does not protect the full AD database, and becoming a DC excludes the documented default.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answer
Without UEFI lock retains remote administrative disablement. With UEFI lock adds a physical-presence removal requirement; disabling VBS removes its isolation foundation. AD DS role installation is unrelated and DC use is not recommended.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answer
SecurityServicesRunning reports actual operating state. An enabled editor setting, stored registry value, or executable file alone establishes configuration/presence rather than running isolation.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answers
Database coverage and Exchange incompatibility are documented boundaries. Credential isolation does not replace DC hardening or protect every secret voluntarily handed to an untrusted application.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answer
Warn and prevent bypass enables the control and closes the warning override. A bypassable warning or user choice fails the mandatory requirement; disabling the feature provides no reputation protection.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answer
Edge has a separate policy for preventing site-warning bypass. Explorer download warnings affect another surface; permitting the browser to run or to reach HTTPS does not configure its reputation-warning override behavior.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answer
Support and matching templates must be verified for the target platform and browser. Client MDM scope and editor visibility do not establish universal Server runtime support. SmartScreen complements antivirus.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answers
Explorer and Edge warning surfaces require separate verification. App Control selects trusted code to execute, while HTTPS firewall permission controls connectivity; neither alone enforces these reputation-warning bypass settings.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answer
The intended computer OU provides the relevant scope. GPOs do not link directly to users; unrelated user placement does not scope computer policy. ADMX files supply editor definitions rather than deploy policy by themselves.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answer
Representative pilot and recovery testing identify operational impact of rights and access changes. Baselines do not guarantee compatibility; suppressing audits hides evidence, and broad service privilege is not a safe compatibility remedy.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answer
Aligned authorities remove competing desired states. Faster refresh can intensify the conflict; blanket disablement abandons security. Moving a member server into the DC OU supplies inappropriate scope rather than resolving the setting ownership.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answers
Resultant-policy evidence and operational state establish application and behavior. Editor template availability does not deploy policy; some extensions need a restart or foreground processing regardless of forced refresh.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answer
OSConfig's documented Server baseline workflow does not support releases earlier than 2025. Module installation or more privilege cannot change OS support. WorkgroupMember distinguishes server role, not an older OS compatibility mode.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answer
DomainController matches the DC role. MemberServer and WorkgroupMember target different identities/roles; App Control audit is a code-control scenario rather than the full role security baseline.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answer
Drift control maintains the configured desired state. Group tokens do not restore arbitrary local settings, and an editor entry alone does not prove enforcement on the host. Installing the module alone does not configure all baseline scenarios.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answers
A scenario override changes desired state and subsequent compliance/workflow checks validate it. Repeated local edits fight drift control; installing a module alone does not apply a scenario.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answer
DFL 2016 enables LAPS AD encryption, while Server 2016 DCs lack current Windows LAPS DSRM management. The presence of Server 2016 does not prohibit encryption, and raising DFL does not install OS-level DSRM support. The relevant encryption requirement is the domain functional level.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answer
ADPasswordEncryptionPrincipal defines authorized decryption when the password is stored. Reading unrelated attributes or resetting expiration does not grant decryption. Renaming the local account does not determine who can decrypt its backed-up secret.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answer
AD expiration is a request/state change acted on by the device when it processes policy/state. It cannot instantly reach a disconnected guest. Schema ownership does not perform each local rotation, and expiration does not inherently disable the account.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answers
Schema attributes and computer self-write rights establish storage and backup authorization. Shared preference passwords defeat unique secret management, and reading delegation does not supply computer write rights.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answer
Plan 1 focuses on EDR via Defender for Endpoint. Plan 2 also includes it but is not the only plan. Antivirus presence and a workspace alone do not establish Defender for Servers plan protection.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answer
Plan 2 can be disabled at resource scope even though it cannot be enabled there. Subscription-wide removal is unnecessary for this exception. Guest account passwords do not change Azure plan configuration.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answer
Arc/antivirus status must be supplemented by MDE onboarding and connectivity evidence. Neither automatically confirms all protection; agentless scanning availability for cloud disks does not imply automatic physical on-premises disk scanning.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answers
The current agent architecture and onboarding-specific feature limits are documented. AMA remains relevant to selected collection benefits rather than universal EDR; Plan 2 cannot be enabled at individual resource scope.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answer
Matching explicit blocks override normal allows. Creation date and display-name ordering do not establish precedence, and Windows Firewall does not expose administrator-weighted rule order for this purpose.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answer
The inbound TCP 443 rule with source/profile scope matches the service access requirement. An unrestricted rule is too broad; an outbound rule does not permit inbound listening traffic. IPsec connection security does not itself authorize the application through the firewall.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answer
Required IPsec depends on compatible authentication and negotiation with active associations. Duplicate traffic allows or broader address/profile scopes do not satisfy a missing required security negotiation.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answers
Azure network controls and the guest's listener/firewall must both permit the path. Guest allows do not override NSG blocking, and IPsec negotiation rules do not create service listeners.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answer
FGPP assigns a PSO to users or global security groups. An OU-only password GPO does not provide a separate domain-user policy. Distribution ACL groups and subnet locality do not select password validation rules.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answer
Direct assignment takes priority over group-associated PSOs. Lowest numerical precedence resolves competition at the relevant level; settings do not automatically merge, and creation date is not the selection rule.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answer
The resultant-password-policy cmdlet reports the selected PSO. The domain default alone omits an overriding PSO, and a member server's local policy does not identify the domain user's FGPP. Policy names are not precedence rules.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answers
User objects and global security groups are supported subjects. PSOs are not OU-linked GPOs, and domain-local groups are not the supported group subject type.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answer
DC agents evaluate locally using downloaded/cached policy. The password is not sent for live cloud validation; the proxy is a retrieval relay rather than LDAP interception/reset logic. The feature supports on-premises AD DS.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answer
Audit records would-reject outcomes while allowing changes. Enforced rejects validation failures. Disabled or undeployed agents do not provide the needed impact evidence from the password filter.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answer
The documented requirement is DFSR, and agents do not work properly in an FRS domain despite installation. Adding a proxy or changing enforcement mode does not replace the required policy replication technology.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answers
Redundant consistent registration and complete writable-DC coverage support policy availability and enforcement. An unfiltered DC creates a bypass, and local validation does not require sending passwords to the cloud.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answer
Protected Users prohibits NTLM at the supported DFL, exposing the application's dependency. Membership does not inherently disable the account or remove every ACL right, and it does not rewrite an NTLM-only application to use Kerberos.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answer
AES key readiness supports permitted Kerberos authentication. DES-only or preauthentication removal weakens or conflicts with the required path; RODC caching does not create the required AES readiness.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answer
Protected Users supplies delegation restrictions independently of the flag. The flag is not the sole control; a shared administrator service password does not make restricted delegation safe. Assess dependency and a scoped solution rather than removing protection everywhere.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answers
Pilot and prerequisite checks identify compatibility before restriction. Service/computer accounts are not appropriate Protected Users members, and simultaneous untested enrollment can remove every recovery path.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answer
Removing unnecessary software and using secured administration reduces attack paths. Privileged-only browser use still exposes powerful credentials; inbound filtering does not remove risks from privileged browsing. A member-server baseline must not be assumed suitable for a DC's roles and dependencies.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answer
The supporting hypervisor, files, and management controls can undermine DC security. Guest encryption alone does not eliminate all fabric risks; OU relocation does not secure privileged host/storage access. In-guest membership review omits the surrounding infrastructure's authority.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answer
Backup protection and tested recovery preserve both secrecy and availability. Disabling backups removes recovery, configuration compliance does not establish restoration, and sole storage on the failed directory creates a recovery dependency.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answers
Minimal patched roles and a suitable Core/secure-administration design reduce exposure. Unrelated services and privileged browsing add attack opportunities on a directory authority.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answer
Scoped OU delegation grants the required directory task without OS/DC access. Domain Admins, DC backup privileges, and broad local logon exceed the helpdesk requirement.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answer
User rights restrict identities and firewall scope restricts source systems. A firewall-only rule leaves identity authorization separate; local logon is not the same as RDP control. Trust authentication does not establish a restricted DC management path.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answer
The nested deny directly blocks the logon despite other allows. Listener status, trust transitivity, and password length alone do not resolve a user-right denial caused by group membership.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answers
Guest/directory access and privileged supporting fabric access can both affect DC integrity. Application file ACLs and ordinary employee OU delegation protect narrower resources and do not cover these DC administrative control layers.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answer
The sensitive/nondelegable option directly restricts delegation. Removing preauthentication, using DES, or reversible storage weakens other authentication protections and does not express this nondelegation requirement.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answer
Smart-card interactive authentication depends on certificate trust and usable hardware with recovery planning. Password history, LDAP message signing, and nondelegation protect different concerns and do not establish the smart-card logon path.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answer
Removing preauthentication exposes AS-response material to unauthenticated requests. It does not force AES, prevent all NTLM relay, or require smart-card interactive logon.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answers
Preauthentication removal and reversible storage weaken credential protection. Nondelegation and an appropriately deployed smart-card requirement can strengthen selected accounts and are not the unsafe settings described.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answer
Schema Admins provides schema-change authority. Backup Operators supplies backup/restore privileges, Account Operators manages permitted accounts, and Print Operators manages printing-related operations; these operator roles are not substitutes for schema administration.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answer
Specific OU password-reset delegation matches the task. Backup rights can bypass data ACLs; Enterprise Admins and Schema Admins are far broader than ordinary account resets.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answer
Protected administrative objects can have AdminSDHolder-derived ACLs and disabled inheritance. Workstation GPO order, password complexity, and universal membership caching do not explain the protected-object directory permission boundary.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answers
Controlled membership and auditing limit privileged authority. Operator groups can grant excessive rights, and OU relocation alone does not remove protected-account ACL behavior.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answer
Scoped operation-specific delegation grants the requested directory tasks. Domain Admins and forest-wide writes exceed the scope. Kerberos delegation concerns forwarding user context to services, not granting password-reset administration.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answer
RBCD is authorized on the resource object. A traditional source-side constrained-delegation list is a different model; a user nondelegation flag restricts rather than grants delegation. An SPN identifies a service but does not alone authorize RBCD principals.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answer
Delegated operations are distinct, so membership edits require appropriate separate rights on the intended groups. Enterprise Admins is unnecessary for routine scoped administration. Preauthentication controls authentication behavior rather than the object ACL, and password-reset rights do not imply domain-wide group modification.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answers
Positive and negative scope tests establish the intended boundary. Protected accounts can have special ACL behavior; sensitive replication rights do not repair routine delegated administration safely.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answer
SASL sealing or TLS supplies confidentiality. Signing alone supplies integrity/authenticity without content encryption; a stronger password does not encrypt an unsigned session. Channel binding requires an applicable TLS session and is not a substitute for transport encryption.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answer
TLS protects simple-bind credentials, while an appropriate secure SASL method supplies its required protections. Opening an already reachable port cannot satisfy security requirements; schema privilege and blanket security removal do not provide protected authentication.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answer
TLS+SASL is the applicable CBT context, and Always rejects missing/invalid binding. TLS is not an exemption, unencrypted simple bind has no TLS binding context, and password length does not satisfy CBT.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answers
Signing provides integrity and CBT binds TLS+SASL authentication. CBT is not simple-bind transport encryption, and TLS security still depends on correct server/certificate identity validation.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answer
Kerberos requires a correct unique SPN tied to the service identity, so an alias can expose missing registration. Password length, replication scheduling, and backup privilege do not repair service-name ticket mapping.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
✓ Correct answer
Per-core and process counters can reveal a saturated serial execution path. A longer aggregate average can hide it, processor count does not show allocation/use, and overall idle capacity does not prove a serial process has spare execution capacity.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
✓ Correct answer
Shorter sampling can expose brief stalls and correlated bottlenecks. Longer intervals and daily averages hide them; a low average cannot rule out short severe events.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
✓ Correct answer
Availability, commitment, and process allocation distinguish pressure or leaks from legitimate paging. Pages/sec alone is not a diagnosis; CPU average does not establish memory behavior; paging can include file-backed reads rather than only pagefile writes.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
✓ Correct answers
Latency and throughput/IOPS establish observed storage performance in workload context. Healthy status does not rule out throttling or latency. A universal queue threshold ignores storage parallelism, and free capacity does not prove low I/O latency.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
✓ Correct answer
A scheduled DCS captures the overnight incident with relevant correlated counters. A noon chart and one later sample miss the incident period. A definition that never runs does not produce data.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
✓ Correct answer
Five-second sampling uses 00:00:05 and binary format uses bin. 00:05:00 selects five minutes, csv selects CSV output, and combining both wrong values changes both requested settings.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
✓ Correct answer
A suitable location and bounded log/stop policy control diagnostic storage use. Changing counter categories alone does not establish a limit. More frequent sampling usually increases data volume, and a different set name does not bound output.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
✓ Correct answers
Actual records and tested scheduling/stop/retention establish a usable capture. Definition creation alone is not collection. CPU-only data can miss the relevant bottleneck, and unbounded system-volume output can fill critical storage.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
✓ Correct answer
Azure Monitor supplies persistent data and alerting. A browser chart is not a retained alert service; DFS-R replicates files; Storage QoS controls I/O rather than notifications.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
✓ Correct answer
Arc, AMA and DCRs provide the supported hybrid guest collection path. Legacy-agent guidance is historical; Dependency Agent is not basic event collection and is deprecated; Reader does not collect guest data.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
✓ Correct answer
The working application separates its data path from WAC gateway/remoting and management authentication. Application success does not establish management reachability. Restarting the working application is not indicated, and its public service port does not exercise the WAC management path.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
✓ Correct answers
Data arrival and alert/action testing establish end-to-end operation. Local charts do not prove ingestion; aggregation can hide the full volume; deployment rights do not automatically imply all log-read rights.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
✓ Correct answer
Six-day predicted exhaustion meets Critical. Current 90-percent utilization is not the forecast criterion; spare space today does not imply OK; a valid adverse prediction is not an execution error.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
✓ Correct answer
System Insights runs local forecasts. Azure alerts require their Azure monitoring context; Dependency Agent Map is deprecated dependency mapping; hard quotas enforce current limits rather than forecasting trends.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
✓ Correct answer
The default model does not predict with zero to five days of input. None can therefore be expected, not an engine failure. Two days does not supply a 60-day forecast, and System Insights processing runs locally without requiring Azure.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
✓ Correct answers
Detailed output and workload context guide capacity planning. Forecasts summarize modeled capacity trends, not every burst or physical failure; operational fault monitoring remains necessary.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
✓ Correct answer
Provider/message/computer/time identify the event and incident context. IDs are provider-scoped, a level alone matches many events, and an export filename does not contain the relevant event semantics by itself.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
✓ Correct answer
epl exports the log. cl clears it; logman manages collectors rather than exporting this event log; Get-SmbSession reports SMB sessions.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
✓ Correct answer
Generation policy and retained accessible records must be checked in the correct log and period. No rows does not prove no event. System and Security are distinct logs, and increasing capacity alone does not enable an absent audit policy.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
✓ Correct answers
Provider detail and aligned time support correlation. IDs are not globally unique; clearing removes evidence; unbounded analytic logging can add overhead and excessive data.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
✓ Correct answer
The associated DCR supplies the requested guest event source and destination. An agent, workspace, or host-metric view alone does not define that Windows event collection path.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
✓ Correct answer
Standard Windows event DCR collection writes Event. SecurityEvent is used by the relevant Sentinel connector route; InsightsMetrics stores classic predefined performance; AzureActivity records management operations.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
✓ Correct answer
Heartbeat confirms communication but not matching event collection. Filter/source/association/table/time determine the data path; automatic legacy parallel installation is not a fix; partition style is unrelated.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
✓ Correct answers
For logs-based private collection, DCE/AMPLS integration and coherent endpoint DNS/routing are required. AMA still needs the appropriate rule association. A public answer does not validate private collection, and standard Windows events follow the Event table route rather than InsightsMetrics.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
✓ Correct answer
Azure VM deletion is a management-plane activity. Guest System logs do not inherently capture that Azure operation. Missing heartbeat can have several causes, and CPU metrics do not identify the exact deletion operation.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
✓ Correct answer
The requested fifteen-minute average maps directly to that aggregation/window. A one-minute maximum and a single sample detect brief peaks, while a daily minimum below the threshold measures a different condition.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
✓ Correct answer
A valid data/query path is needed before threshold tuning. Missing rows can be missing telemetry; severity and action duplication do not fix collection or query selection.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
✓ Correct answers
Condition and end-to-end action/resolution testing prove the alert works. Creation alone is insufficient; management rights and data reads differ; aggregated disks can mask the affected volume.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
✓ Correct answer
Guest memory requires a guest data collection path. Activity logs record management operations; DNS endpoints affect reachability; QoS governs I/O and does not collect memory metrics.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
✓ Correct answer
The selected OpenTelemetry metrics experience uses an Azure Monitor workspace. Log Analytics and InsightsMetrics belong to the classic logs-based route, while Event stores collected Windows events.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
✓ Correct answer
The predefined classic VM Insights performance records use InsightsMetrics. Additional standard counter rules can use Perf. Event holds Windows logs and AzureActivity holds control-plane operations.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
✓ Correct answers
AMA/rules establish collection and separate suitable rules extend it. Dependency Agent Map is deprecated; host metrics do not include all guest events; the classic predefined metrics DCR should not be arbitrarily edited.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answer
SMB requires TCP 445 and a working listener/security path. Ping covers ICMP, not SMB; CPU and hostname changes do not directly test the failing transport.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answer
TCP RDP depends on Azure controls, routing, and guest listener/firewall. Ping checks ICMP, Running reports VM state, and DNS supplies an address; none alone proves the specific RDP flow is allowed and accepted.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answer
Stateful filtering can reject an asymmetric return path. Replacing DNS does not change the demonstrated routes. A port change does not resolve routing/state ownership, and forward delivery alone does not prove bidirectional connectivity.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answers
Name/IP comparison separates resolution from routing and port/listener checks target the service. ICMP is independent; TCP does not prove UDP QUIC; simultaneous changes obscure the cause.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answer
NXDOMAIN identifies a missing-name DNS answer. SMB encryption, IOPS and Recycle Bin settings do not create the requested hostname record.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answer
Resolve-DnsName with Server and DnsOnly selects the stated resolver and excludes LLMNR/NetBIOS resolution. The unqualified query does not enforce those choices. A TCP test does not isolate that DNS reply, and clearing cache does not query the specified resolver.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answer
The hostname must resolve privately through the correct DNS and forwarding design. Quotas and cluster sizes do not alter DNS; extra cloud endpoints are not a DNS fix and a group has one cloud endpoint.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answers
Correct resolver selection, service records and response/cache comparison identify the failure. Public DNS cannot normally resolve private AD records; IP ping bypasses DNS; evidence should identify the resolver before blanket cache changes.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answer
CBS and the exact failure code expose servicing-stage problems. Namespace naming, storage reports and key IDs do not diagnose the update installer stage.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answer
WSUS approval and targeting control whether the server is offered the update. Component repair, download cache cleanup, and restart deadlines do not approve or target the missing package.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answer
The readable generated log is static and must be regenerated for later ETL data. It is not automatically appended, absence from that snapshot does not disprove a retry, and deleting the generated text does not by itself delete all source ETL traces.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answers
Package compatibility and dependency/supersedence state determine applicability. Download and ping do not prove it; an unrelated approval category cannot change the package requirements.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answer
NT5DS follows the domain hierarchy. Independent manual peers depart from the stated requirement; NoSync disables synchronization; DNS forwarding is not a Windows Time client type.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answer
The source query shows current selection. Configuration lists settings rather than establishing the selected source; SMB connection and replication summary commands do not report NTP source.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answer
Group Policy can reapply effective settings, so inspect its influence and configuration. Repeating a local edit does not address the source, a peer list alone does not identify controlling policy, and stripchart reachability/offset does not prove configuration precedence.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answers
The hierarchy source and UDP NTP path determine synchronization. TCP is not NTP validation; password resets do not correct skew; disabling sync cannot guarantee agreement.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answer
Persistent private allocation growth with pressure supports a leak/allocation investigation. DNS caching, encryption recovery and filename screening do not directly explain this memory trend.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answer
Provisioned disk and VM aggregate limits can throttle otherwise healthy storage. More capacity alone may not remove the VM ceiling. Healthy status and free bytes do not establish sufficient performance.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answer
Serial work can remain limited by one core even when total CPU is low. Aggregate averages hide that limitation, more cores do not automatically parallelize the thread, and memory is not the only possible bottleneck.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answers
Workload response and correlated resource evidence validate the repair. Reboot alone does not establish cause; idle/peak comparisons mislead; simultaneous changes obscure the effective intervention.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answer
A connection does not prove handler or script success. Arc uses its own extension-management path; network, identity and script problems can also fail an extension.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answer
Arc extension-service logs report package download/verification. CBS concerns servicing; a copy log and DFS referrals do not describe Arc handler provisioning.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answer
The script reached execution and needs the appropriate guest identity and path rights. Download success does not establish those rights. The Azure caller's control-plane role is not automatically the script's guest identity, and unchanged permission denial will recur.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answers
Agent/instance status and handler/script output distinguish the failing stage. Resource creation is insufficient; unchanged errors recur on blind reinstall; himds belongs to Arc Connected Machine agent.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answer
The matching password unlocks the encrypted volume. Ownership and naming do not decrypt; an unrelated protector record cannot unlock this volume.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answer
EFS retains a separate file-key requirement after BitLocker unlock. Partition identifiers, read roles and tiering policy do not provide the EFS private key.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answer
Repeated prompts can reflect changed boot validation or incorrect protector workflow. Enumeration, free-space totals and display names do not reconcile TPM boot measurements.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answers
Salvage needs valid matching password/key material, plus a matching key package when required, and a separate output that can be overwritten. The package does not replace keys. Failed partial conversion is unsupported, and ownership does not prove decrypted data.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answer
Disk loss is a lower block-storage/path symptom. Namespace appearance, group names and template descriptions do not restore the presented LUN.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answer
Thin logical capacity can exceed available physical pool allocation. Virtual maximums, filesystem free space, and share quotas do not establish free backing storage.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answer
Unexpected RAW can indicate damaged presentation or filesystem, so preserve and investigate. Initialization risks existing data; ownership and share naming do not reconstruct filesystem metadata.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answers
Current protection and quorum/capacity determine safe maintenance. A drive letter, theoretical copy count or one login does not verify remaining cluster resilience.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
✓ Correct answer
Recycle Bin recovers the restorable object and preserved links without a whole database restore. Whole-DC recovery is broader than required. SYSVOL is policy-file content, while recreating a display name does not restore the old object's identity and links.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
✓ Correct answer
The intended parent must exist before children can return there. A child restore does not automatically reconstruct all missing ancestors, and display-name matching is not a substitute for exact object and hierarchy restoration.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
✓ Correct answer
Recycle Bin is not retroactive for full preservation of earlier tombstones. It does not disable Kerberos; manual per-DC creation conflicts with replication; SMB roles do not alter AD retention.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
✓ Correct answers
Identity/state and parent validation establish a valid object restore. Retention is configurable; enablement is irreversible; SYSVOL file content is a separate recovery layer.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
✓ Correct answer
Nonauthoritative recovery or rebuild uses healthy partner data. Declaring the entire old forest authoritative can overwrite valid changes; Recycle Bin restores objects; BurFlags is a legacy FRS mechanism.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
✓ Correct answer
Marking the restored subtree before normal replication makes it win. Premature restart can reapply deletion; live database copying is unsupported; SYSVOL does not contain the AD user database.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
✓ Correct answer
DSRM uses that DC's separate local recovery Administrator credential. It is not guaranteed to match the domain Administrator password. A domain user's cached password and another server's local credential do not authenticate this recovery account.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
✓ Correct answers
A suitable backup/age and recovery credentials/scope support restoration. Checkpoints are not a universal backup strategy; AD DS Stopped is distinct from DSRM; indiscriminate authority can overwrite legitimate changes.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
✓ Correct answer
Nonauthoritative synchronization takes the good partner copy. Making damaged content authoritative propagates it; a user restore does not recover policy files; SYSVOL recovery is protected from ordinary DFS-R group editing.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
✓ Correct answer
4114 is expected after disabling the SYSVOL subscription. 4602 confirms authoritative initialization, while 4614 and 4604 belong to the later nonauthoritative initialization sequence.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
✓ Correct answer
DFS-R uses its specific subscription-attribute procedure. BurFlags is FRS-specific. AD GPO metadata restoration does not automatically restore corresponding SYSVOL files, and namespace priority does not repair replicated policy content.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
✓ Correct answers
A verified source and coordinated ordering seed a consistent domain copy. AD and SYSVOL replication differ; multiple conflicting authorities are inappropriate; AD object recovery does not automatically restore policy files.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
✓ Correct answer
Different directory state on DCs suggests replication divergence. Screening, volume encryption and SMB compression do not propagate AD user objects.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
✓ Correct answer
showrepl provides detailed inbound partner and naming-context status. replsummary is a broader summary. Time-source and client discovery commands supply different infrastructure evidence rather than the requested detailed replication partner report.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
✓ Correct answer
A long-stale DC can reintroduce obsolete data and needs a supported recovery decision. Forced sync and ping do not resolve that risk; namespace caching is unrelated to AD database age.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
✓ Correct answers
Partner/context status and infrastructure/security evidence isolate AD replication failures. Cached sign-in can bypass current DC reachability, DFS-R concerns SYSVOL rather than directory-object replication, and role ownership alone does not establish replication health.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
✓ Correct answer
A site-scoped discovery failure points to branch infrastructure and DC selection. Whole-domain restore is not justified; IOPS and display names do not locate the branch DC.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
✓ Correct answer
nltest dsgetdc tests suitable DC discovery. Replication summary examines DC replication, klist lists tickets, and Get-ADUser queries objects after a management connection; none is this focused client discovery command.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
✓ Correct answer
A stale stored credential explains repeated attempts immediately after a password change. Unlocking does not update that credential, longer lockout does not remove the cause, and a display-name change does not change the stored secret.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
✓ Correct answers
Separating discovery/authentication from resource authorization identifies the failing step. Local admin and cached logons do not prove live domain health; policy failures need scoped diagnosis before database recovery.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
✓ Correct answer
The non-unique principal error points to ambiguous registrations. Ticket expiry and time skew cause different failures; a completely missing principal instead aligns with a principal-unknown error.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
✓ Correct answer
-S adds after duplicate verification. -A lacks that preferred check; ticket purging does not register SPNs; replication summary reports AD replication rather than modifying service identity.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
✓ Correct answer
The alias needs correct resolution and Kerberos service identity. Ping proves neither ticket issuance nor SPN ownership; shrinking and forecast status do not configure the alias authentication path.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
✓ Correct answers
Service identity and constrained delegation/account policy govern backend access. First-hop success is insufficient; purging does not correct directory registrations; Kerberos time requirements remain despite DNS success.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
✓ Correct answer
Netlogon trust depends on the member machine secret matching its AD computer account password. User sign-in credentials, share authorization, and DNS caching are separate relationships and do not define that machine-account secret match.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
✓ Correct answer
The cmdlet tests the member channel against the selected DC. SMB handles, deleted-object restoration and forecasts do not test its Netlogon relationship.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
✓ Correct answer
The reference limits this cmdlet to domain members and warns of false errors on DCs. It does not conclusively diagnose forest trusts, guarantee a DC repair, or prove failure of all member authentication.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
✓ Correct answers
Infrastructure and DC consistency distinguish reachability/replication from a machine-secret mismatch. A reset cannot be assumed propagated through broken replication. Guest-local administration does not establish AD update rights, and interforest trusts are different relationships.
Open this question’s page →AD DS · AD DS | Deploy and manage AD DS domain controllers · Virtual machines · Virtual machines | Manage Windows Server VMs in Azure · Networking · Networking | Implement on-premises and hybrid name resolution
✓ Correct answers
The AD DS Azure architecture uses persistent data disks with None host caching and stable private NIC addresses. Domain members need DNS that can locate AD service records. Temporary disks can lose data; public resolvers do not host the private AD zone; public IPs are unnecessary for private domain replication.
Open this question’s page →AD DS · AD DS | Deploy and manage AD DS domain controllers · Security · Security | Secure AD DS
✓ Correct answer
Approved user and computer credentials must be available for the intended outage authentication path, with privileged accounts kept denied. User-only preparation can leave the computer authentication path unavailable. Broad directory replication rights can undermine the caching policy; local group membership does not supply uncached domain secrets.
Open this question’s page →AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments · AD DS | Create and manage AD DS security principals · Storage and file services · Storage and file services | Configure and manage Windows Server file shares
✓ Correct answer
Selective authentication requires Allowed to authenticate on the target computer in addition to existing share and NTFS access. A reverse trust supports the opposite access direction; granting the same resource ACL again does not pass the authentication gate; a DNS alias does not grant that right.
Open this question’s page →AD DS · AD DS | Create and manage AD DS security principals · Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment · Security · Security | Secure AD DS
✓ Correct answers
The KDS root key supports managed password generation, and authorized hosts must be permitted to retrieve the gMSA password. The service identity still needs access to the share. Local accounts create manual lifecycle work; an sMSA is tied to one host; allowing all computers weakens the requested scope.
Open this question’s page →AD DS · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments · Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
✓ Correct answer
AD subnet-to-site mapping helps clients locate an appropriate site and its domain controllers. DHCP lease duration does not establish AD site membership. Schema-master location does not direct routine client authentication. Public DNS alone cannot supply the domain locator records.
Open this question’s page →AD DS · AD DS | Manage Windows Server by using domain-based Group Policies · AD DS | Configure and manage multi-site, multi-domain, and multi-forest environments · Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
✓ Correct answer
GPO metadata in AD and files in SYSVOL use separate replication mechanisms. Investigate DFSR content and events on the affected DC even if GPMC metadata is current. They are not one atomic transaction, clients can use different DCs, and faster client refresh does not repair a stale server-side file replica.
Open this question’s page →Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment · Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
✓ Correct answer
Guest configuration assessment and telemetry collection have separate assignments and destinations. Arc connection alone is not evidence that either workload has been configured. A telemetry DCR does not by itself apply arbitrary configuration, and Machine Configuration does not replace AMA performance collection.
Open this question’s page →Hybrid server management · Hybrid server management | Configure remote management for Windows Server instances in a hybrid environment · AD DS · AD DS | Create and manage AD DS security principals · Security · Security | Secure AD DS
✓ Correct answers
Reviewed role capabilities restrict the exposed commands; an authorized gMSA can provide the required domain network identity. A virtual account does not automatically forward the connecting user credentials. Arbitrary external commands undermine the restricted endpoint, and permission to an unrestricted endpoint does not create a two-command boundary.
Open this question’s page →Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment · Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answer
Update Manager uses the configured Windows update source, so WSUS synchronization, approval targeting and applicability still matter. Changing the Arc resource region does not replace the guest source. A longer maintenance window cannot change package applicability or approval, and an unchanged repeated assessment does not correct the source configuration.
Open this question’s page →Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
✓ Correct answer
The enabled Automation account system-assigned identity takes precedence over the Arc worker identity in the stated documented managed-identity path and needs appropriate Azure permissions. Local NTFS rights govern local files, not Azure resources. The Arc role alone is insufficient for the selected principal, and schedule recreation does not select a different identity.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
A validated failover cluster provides automatic local VM recovery, while Hyper-V Replica provides the asynchronous DR copy. Replica alone is not synchronous automatic local HA. Co-located checkpoints do not protect against storage loss, and a manual-failover-only design does not meet automatic primary-site recovery.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM · Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answer
PowerShell Direct uses the host-to-guest channel and does not depend on guest networking or configured WinRM. Normal network remoting and RDP need the network path. An unrelated Bastion deployment cannot reach the local VM without a supported route.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM · Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answer
VHDX expansion increases disk capacity, but the guest partition and supported filesystem must also extend into the adjacent space. Optimize-VHD compacts eligible files; another virtual-disk expansion still leaves old partition boundaries; a checkpoint does not extend the guest volume.
Open this question’s page →Virtual machines · Virtual machines | Manage Hyper-V and guest VM
✓ Correct answer
Server 2025 GPU-P live migration requires supported GPUs/drivers, homogeneous partition configuration and suitable IOMMU DMA bit-tracking hardware. DDA assigns whole devices without this live-migration behavior. Unrelated GPU configurations are unsupported, and omitting the CPU/IOMMU prerequisite cannot establish live migration.
Open this question’s page →Virtual machines · Virtual machines | Manage Windows Server VMs in Azure
✓ Correct answers
Autoscale provides additional instances, while supported multi-zone placement and resilient traffic/application dependencies address zone loss. An availability set does not clone a VM across zones. Vertical resizing does not supply horizontal instances, and autoscale within one failed zone does not establish zone resilience.
Open this question’s page →Networking · Networking | Implement on-premises and hybrid name resolution · Storage and file services · Storage and file services | Configure and manage Azure Files
✓ Correct answer
A hybrid resolver path must connect on-premises queries to the Azure private-zone view. The Azure platform resolver address is not directly reachable as a general on-premises resolver. Hosts-file entries create manual lifecycle work. SMB authorization is independent of DNS resolution.
Open this question’s page →Networking · Networking | Implement on-premises and hybrid name resolution · Networking | Manage IP addressing in on-premises and hybrid scenarios
✓ Correct answer
Restore DNS servers that can resolve the AD zone and SRV locator records; domain DNS can forward external queries. Lease duration and reservations do not fix public-only DNS selection, and DNSSEC signing of a public zone does not publish private AD records.
Open this question’s page →Networking · Networking | Implement on-premises and hybrid name resolution · Security · Security | Secure Windows Server operating system
✓ Correct answer
DNSSEC validates DNS data authenticity and integrity when the chain and policy are correctly configured. It does not encrypt application traffic. IPsec encryption is a separate traffic control; an ordinary firewall allow rule does not validate DNSSEC signatures, and a DNS trust anchor does not create IPsec associations.
Open this question’s page →Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
✓ Correct answer
Failover configuration replication is the supported operation for scope properties, options and reservations. Lease synchronization is not a substitute for that explicit configuration workflow. Overlapping independent scopes risk conflicting leases; a shared-secret change does not replicate the intended settings.
Open this question’s page →Networking · Networking | Manage IP addressing in on-premises and hybrid scenarios
✓ Correct answer
Check relay GIADDR and any option 82 link-selection suboption, and identify the matching allocation scope. A correct client identifier in a different scope cannot override wrong subnet selection. Lease duration does not choose the subnet; option 003 is supplied after allocation, not used as the relay selector; free capacity in the new scope does not prove that requests select it.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Azure Files · Storage and file services | Configure and manage Windows Server file shares
✓ Correct answer
Azure File Sync supplies the NTFS server endpoint, cloud endpoint and cache policies. QUIC changes transport, not synchronization. Direct mounts do not make clients server endpoints, and client Offline Files is not the required server-side File Sync architecture.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Azure Files · Storage and file services | Configure and manage Windows Server file shares
✓ Correct answers
DFS Namespaces can retain the user path through suitable SMB targets. The documented migration begins with the complete initial upload without tiering, then coordinates DFSR disablement before adding the remaining endpoints. Controlled initial staging must not become indefinite competing replication. Replacing the namespace fails the preserved-path requirement, and enabling tiering prematurely does not establish placeholder compatibility.
Open this question’s page →Storage and file services · Storage and file services | Configure and manage Azure Files · Storage and file services | Configure and manage Windows Server file shares
✓ Correct answer
Contributor already passes the share write gate; the target folder needs appropriate file-side write permission. Reader would further restrict access. The working read path is not evidence for recreating the private endpoint, and changes outside the target ACL/inheritance scope do not grant its write access.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage · Storage and file services | Configure and manage Windows Server file shares
✓ Correct answer
Storage Replica replicates volume blocks and its asynchronous mode is appropriate when the supported synchronous latency requirement cannot be met and the RPO permits lag. Synchronous mode would affect the write path. DFSR is file replication with open-file limitations; namespace referrals do not replicate data.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage · Storage and file services | Configure and manage Windows Server file shares
✓ Correct answer
FSRM requires NTFS for its folder quotas and file screens. ReFS integrity features do not add FSRM support. Per-user quotas are a different control and are not a ReFS workaround; enabling deduplication does not change FSRM filesystem support.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage · Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answer
QoS distributes available performance and reports when storage cannot meet requested minima. Investigate physical contention/capacity and tune allocation or placement. A minimum cannot guarantee nonexistent capacity; raising every minimum or changing policy scope does not create more backend IOPS.
Open this question’s page →Storage and file services · Storage and file services | Configure Windows Server storage
✓ Correct answer
EFS file decryption requires the applicable owner or recovery-agent private key. BitLocker protectors unlock the volume and do not supply EFS private keys. A public certificate alone cannot decrypt the file key; taking ownership or changing ACLs does not supply decryption material.
Open this question’s page →Security · Security | Secure Windows Server operating system
✓ Correct answer
OSConfig drift control and a conflicting GPO can repeatedly write different values. Establish a consistent intended value and remove the conflicting source or apply a supported customization coherently. A one-time application does not neutralize other writers; a DC scenario does not match a member server; repeated reapplication leaves the underlying conflict.
Open this question’s page →Security · Security | Secure Windows Server operating system · Security | Secure AD DS
✓ Correct answer
Encrypted AD-backed LAPS separates permission to read the stored attribute from permission to decrypt its value. Review both delegations with least privilege. Read-only attribute access does not itself authorize decryption; local workstation administrators are not automatically authorized decryptors; password age changes do not grant decryption rights.
Open this question’s page →Security · Security | Secure Windows Server operating system · Security | Secure AD DS
✓ Correct answer
Credential Guard is not recommended on DCs and does not protect the AD database. Protected Users should not contain service or computer accounts and restricts NTLM and other authentication behaviors for suitable users. These controls do not have identical scope; permitting NTLM fallback is incorrect; correcting the server target alone does not correct the service-account design.
Open this question’s page →Security · Security | Secure AD DS
✓ Correct answer
The DC agent evaluates the password locally using its valid cached protection policy, alongside normal AD password policy. It does not send plaintext passwords for live approval. Cloud loss does not disable all AD checks or invalidate an already available cached policy.
Open this question’s page →Security · Security | Secure Windows Server operating system · Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answer
IPsec connection security rules negotiate authentication/encryption, while firewall traffic rules still authorize the application port and profile. Successful negotiation does not open every port. Encryption is not inherently incompatible with filtering, and another connection security rule does not substitute for the required traffic allowance.
Open this question’s page →Security · Security | Secure Windows Server operating system · Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
✓ Correct answer
Arc registration and a plan switch do not prove endpoint sensor onboarding or reporting. Verify the applicable plan integrations, required extensions and service connectivity. Connected status addresses Arc management; plan selection alone is incomplete; control-plane Activity Log alone does not establish endpoint-protection telemetry.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
✓ Correct answer
Storage performance can be capped by disk provisioning and VM aggregate limits, so correlate guest latency/queue with platform throughput/IOPS and demand. Low CPU does not rule out I/O pressure; a disk SKU alone omits VM caps; caching changes need workload and cache-path evidence and do not automatically remove all limits.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services · Hybrid server management · Hybrid server management | Manage Windows Server instances and workloads by using Azure services in a hybrid environment
✓ Correct answer
AMA needs the intended DCR associated with the machine before that rule supplies sources and destinations. A duplicate unassociated definition, a new interval on an unused rule or a different query table does not fix the missing resource association. After association, validate collection and the appropriate table.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Monitor by using Windows Server tools and Azure services
✓ Correct answer
Fired establishes that the detection condition ran; investigate the associated action group, receiver/delivery evidence, mailbox filtering and action suppression. Raising the threshold does not fix delivery. An unassociated replacement group cannot change this alert actions, and testing notification delivery need not wait for resolution.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
✓ Correct answer
DFSR SYSVOL uses its documented authoritative/nonauthoritative synchronization procedure and does not use FRS BurFlags. AD database restoration does not establish SYSVOL readiness, and copying files alone does not verify DFSR initialization or the resulting SYSVOL/NETLOGON shares.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Windows Server issues · AD DS · AD DS | Deploy and manage AD DS domain controllers
✓ Correct answer
The forest-root PDC emulator should use a reliable source, with downstream domain synchronization verified. Random independent sources can disagree; schema-master movement does not set time authority; a one-time member resync can recur against the unchanged unreliable source.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory
✓ Correct answer
On a member server, the supported secure-channel test/repair can address the computer-account password mismatch after restore; verify actual domain authentication afterward. User password resets and ticket purges do not reconcile the machine secret, and Test-ComputerSecureChannel is not valid for DC secure-channel diagnosis.
Open this question’s page →Monitoring and troubleshooting · Monitoring and troubleshooting | Troubleshoot Active Directory · Monitoring and troubleshooting | Troubleshoot Windows Server issues
✓ Correct answer
The requested SPN must identify the correct account uniquely so the service can receive a ticket for its key. More duplicates increase ambiguity; IP access can alter Kerberos behavior; purging the cache without correcting SPN ownership leaves the cause for future requests.
Open this question’s page →Permission is granted to use, copy, modify, and redistribute the original flashcards, questions, explanations, and handoff files in StudyByteLearn and elsewhere, including commercial use. Linked Microsoft documentation retains its existing terms; this permission does not grant rights to Microsoft trademarks or third-party materials. · Updated 2026-10-20
Created by Codex with parallel domain-authoring agents from Microsoft Learn documentation and the official AZ-802 study guide, checked on 2026-10-20. Each item received author inspection and independent AI content review against supporting documentation, including answer keys, versions, prerequisites, ambiguity, and explanations. Review evidence and source manifests accompany the pack. No live server commands were executed. Structural/import validation does not by itself establish accuracy.