Microsoft AZ-802 : Administering Windows Server

Correct Answer: B  🗳️

Explanation: Only visible for Free4Torrent members. You can sign-up / login (it's free).

Correct Answer:

Explanation:

First action: Enable supplemental allow rules in the base policy. Second action: Create a signer rule in a supplemental policy.
A Windows Defender Application Control supplemental policy is a separate policy that expands what an existing, enforced base policy allows, without editing the base policy ' s own allow rules, but a base policy must explicitly permit supplemental policies before any supplemental policy can be linked to and take effect alongside it, which is why enabling supplemental allow rules in the base policy has to happen first; this is a one-time change to the base policy ' s own options (adding the Enabled:Allow Supplemental Policies rule option), not a modification of its allow rules, so it satisfies the requirement not to change the base policy ' s allow rules. With supplemental policies permitted, creating a signer rule inside a new supplemental policy, keyed to the vendor ' s single code-signing certificate rather than to individual file hashes, allows every binary the vendor signs with that certificate, including all of App1 ' s monthly updates, without requiring the supplemental policy (or the base policy) to be edited again each time a new signed build ships, which directly minimizes ongoing policy maintenance. The supplemental policy can then be deployed only to the six pilot servers, leaving the other 34 servers unaffected. Adding hash-based rules or path rules to the base policy would both violate the no-base-policy-allow-rule-changes requirement and would require constant hash updates every time the vendor releases a new monthly build, and putting the pilot servers into audit mode would stop enforcing the base policy ' s controls entirely rather than selectively permitting App1.

Correct Answer: C  🗳️

Explanation: Only visible for Free4Torrent members. You can sign-up / login (it's free).

Correct Answer: D  🗳️

Explanation: Only visible for Free4Torrent members. You can sign-up / login (it's free).

Correct Answer:

Explanation:
1. On Server2, install the Azure File Sync agent. 2. Register Server2 with the Storage Sync Service. 3. Add a server endpoint to the sync group.
Because Server1 already syncs with share1, the Storage Sync Service resource, the sync group, and the cloud endpoint pointing at share1 already exist; adding Server2 does not require recreating any of that infrastructure.
To bring a new server into an existing Azure File Sync topology, you first install the Azure File Sync agent on that server, which provides the components needed to communicate with the Storage Sync Service.
Immediately afterward (and typically as part of the same setup wizard), you register the server with the existing Storage Sync Service, which establishes trust and identity for Server2 within that Azure resource.
With Server2 registered, the final step is to add a server endpoint to the existing sync group, specifying the local path on Server2 that should participate in the sync relationship with share1; this triggers the initial synchronization and ongoing multi-master sync between Server2 ' s folder and the cloud endpoint (and therefore with Server1, indirectly). Adding a Storage Sync Service to the subscription and adding a cloud endpoint to the sync group are both one-time setup actions that were already completed when Server1 was originally configured, so neither belongs in this three-step sequence.