Microsoft Administering Windows Server Hybrid Core Infrastructure (AZ-800日本語版) - AZ-800日本語 Exam Practice Test

Explanation:
< File1 is deduplicated after the deduplication job runs. - YES
File3 is deduplicated after the deduplication job runs. - NO
File4 is deduplicated after the deduplication job runs. - NO
The Administering Windows Server Hybrid Core Infrastructure materials explain that Data Deduplication operates per-volume and only processes files on volumes where the role is enabled. The guide states that deduplication "is applied only to NTFS/ReFS volumes on which the Data Deduplication role is enabled," and that the General-purpose file server usage type applies default policies for typical data shares. It further specifies the file size limits: "Files smaller than 32 KB are not deduplicated; supported files are 32 KB up to multiple terabytes," and clarifies that optimization jobs process eligible files during scheduled runs.
Applying those rules:
* Volume D has Data Deduplication enabled (General-purpose). After moving File1 (500 KB) from C: to D:, it resides on a deduplicated volume and exceeds the minimum size threshold, so it will be deduplicated by the next optimization job.
* File3 (1 MB) is moved off the deduplicated volume (to E:), and dedup only affects enabled volumes; therefore it will not be deduplicated.
* File4 is a copy of File2 (10 KB) on D:. Because the file is smaller than the 32-KB minimum, it is not deduplicated even though it is on a deduplicated volume.
Thus the correct outcomes are YES for File1, NO for File3, and NO for File4.

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

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

Explanation:

In the Administering Windows Server Hybrid Core Infrastructure guidance on trusts, Microsoft clarifies that a one-way outgoing trust from the local domain means the local domain trusts the specified external domain; therefore, "security principals from the t rusted (specified) domain can be authenticated to access resources in the trusting (local) domain." Furthermore, external trusts are non-transitive and scoped only to the two domains that participate in the trust; they do not flow through to other domains or forests. The materials also state that parent-child trusts inside a forest are two-way and transitive, allowing authentication to cross between parent and child domains, but this transitivity does not extend across an external trust to another forest.
Applying these rules:
* The external one-way outgoing trust is configured on east.contoso.com # adatum.com. Thus, east.
contoso.com trusts adatum.com, allowing users from adatum.com to be granted access to resources in east.contoso.com. Therefore, User1 (adatum.com) can be assigned permissions on Share3 (east.contoso.
com) # Yes.
* User2 (contoso.com) attempting to access Share1 (adatum.com) relies on a path that would require trust from adatum.com to contoso.com or a transitive hop through east.contoso.com. Because the trust is external and non-transitive, and there's no trust from adatum.com to contoso.com, permissions cannot be assigned # No.
* User3 (east.contoso.com) to Share1 (adatum.com) would require adatum.com to trust east.contoso.com.
The configured direction is the opposite (east # adatum, outgoing), so east users are not trusted by adatum # No.

Explanation:
Yes
Yes
No
The Administering Windows Server Hybrid Core Infrastructure materials describe how Azure AD Connect filtering and sign-in methods affect user capabilities. Un der Domain/OU filtering , it states that when "Sync selected domains and OUs" is configured, only objects in the selected OUs are synchronized to Azure AD. In the exhibit, OU1 is selected and OU2 is not; therefore User1 (in OU1) is synchronized, and User2 (in OU2) is not synchronized and will not exist in Azure AD for group membership.
For sign-in, the guide explains Pass-through Authentication (PTA) : "When you enable Pass-through Authentication and disable Password Hash Synchronization, the user's sign-in to Microsoft 365 is validated against on-premises Active Directory by the PTA agent contacting domain controllers." Thus, when User1 signs in to Exchange Online , authentication is performed by on-premises AD DS via PTA.
Regarding Self-Service Password Rese t (SSPR) , the hybrid password management section specifies: "If Password writeback is enabled in Azure AD Connect, synchronized users can reset or change their passwords in Azure AD and the change is written back to on-premises Active Directory." Because t he configuration shows Enable Password writeback and User1 is synchronized, User1 can use SSPR .
Finally, since User2 is not synchronized (OU2 excluded), User2 does not exist in Azure AD and cannot be added to Group1 in the tenant.

Explanation:

In the Administering Windows Server Hybrid Core Infrastructure objectives for managing Hyper-V, enabling nested virtualization is the required step when you must "run virtual machines inside a virtual machine." The referenced guidance states that Hyper-V on a VM is supported only when the host exposes hardware virtualization features to the guest. The prescriptive step is: "Turn off the VM and run Set-VMProcessor - VMName < V MName > -ExposeVirtualizationExtensions $true to enable nested virtualization." The module further notes that this action "passes through Intel VT-x/AMD-V to the guest so the guest OS can install the Hyper-V role and create VMs." It also clarifies that "the setting is applied on the parent host for the target VM and requires the VM to be powered off before the change is committed." Because the technical requirement says "Ensure that you can run virtual machines on VM1", VM1 must be able to host Hyper-V while itself running as a VM on Server2. The first and essential cmdlet is therefore Set- VMProcessor with the -ExposeVirtualizationExtensions switch set to $true against VM1. Other optional settings (for example, MAC spoofing on the vNIC or static memory) may be configured later if needed, but exposing virtualization extensions is the enabling prerequisite that satisfies the requirement.

See the solution of this Task below.
Explanation:
To collect the recommended Windows Performance Counters from SRV1 in a Log Analytics workspace, you can follow these steps:
Step 1: Access the Log Analytics Workspace Log in to the Azure portal and navigate to your Log Analytics workspace.
Step 2: Configure Performance Counters In the Log Analytics workspace, select Advanced settings and then choose Data > Windows Performance Counters1. You can add the recommended performance counters by selecting the + button. If you're using legacy agent management, you can add counters from the Legacy agents management menu2.
Step 3: Add P erformance Counters Select the counters you want to collect. You can add common counters quickly by checking the boxes next to them. For specific counters, enter the name of the counter in the format object(instance)\counter. For example, to collect the Pr ocessor Time counter for all instances of the Processor object, specify Processor(_Total)\% Processor Time.
Step 4: Set Sample Interval When adding a counter, you can set the sample interval, which is the frequency at which data is collected. The default is 10 seconds, but you can change this to a higher value if needed.
Step 5: Apply Configuration After adding the desired performance counters, select Apply at the top of the screen to save the configuration.
Step 6: Install and Configure the Agent Ensure t hat the Microsoft Monitoring Agent (MMA) is installed on SRV1. Configure the agent to report to your Log Analytics workspace by specifying the workspace ID and key during setup.
Step 7: Verify Data Collection After the agent is configured, it will start co llecting the specified performance counters. You can verify the data collection in the Log Analytics workspace by running queries against the collected data.
Note: The legacy Log Analytics agent will be deprecated by August 2024. Migrate to the Azure Monit or agent before this date to continue ingesting data3.
By following these steps, you should be able to collect the recommended Windows Performance Counters from SRV1 in your Log Analytics workspace. Ensure that you have the necessary permissions and that S RV1 has network connectivity to Azure services.

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

See the solution of this Task below.
Explanation:
To map \\dd.contoso.com\instal1 as drive H for all users using Group Policy Preferences and ensure that the new drive mapping takes precedence over any existing mappings, follow these steps:
Step 1: Open Group Policy Management Console Open the Group Policy Management Console (GPMC) on a machine that has administrative privileges over the domain.
Step 2: Create or E dit a GPO Create a new Group Policy Object (GPO) or edit an existing one that applies to the users who need the drive mapping.
Step 3: Navigate to Drive Mappings In the GPO Editor, navigate to:
User Configuration - > Preferences - > Windows Settings - > Drive Maps
Step 4: New Drive Mapping Right-click on Drive Maps and select New - > Mapped Drive.
Step 5: Configure Drive Mapping In the New Drive Properties window, configure the following settings:
Action: Select Replace. This action will overwrite any existing mappings with the same drive letter.
Location: Enter the UNC path \\dd.contoso.com\instal1.
Drive Letter: Choose H: from the drop-down menu.
Reconnect: Check this option if you want the drive mapping to persist across logon sessions.
Label As: Optionally, provide a label for the drive mapping.
Hide/Show this drive: Set according to your preference.
Hide/Show all drives: Set according to your preference.
Step 6: Common Tab Go to the Common tab and configure the following:
Run in logged-on user's security con text (user policy option): Check this option.
Item-level targeting: Click on Targeting and set up any specific criteria if needed.
Step 7: Apply the GPO Click Apply and then OK to save the drive mapping configuration.
Step 8: Link the GPO Link the GPO to a n Organizational Unit (OU) or domain that contains the users who should receive the drive mapping.
Step 9: Update Group Policy Instruct users to log off and log back on, or use the gpupdate /force command to refresh Group Policy on their computers.

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

See the solution of this Task below.
Explanation:
One possible solution to ensure that a DHCP scope named scope1 on SRV1 can service client requests is to activate the scope on the DHCP server. A scope must be activated before it can assign IP addresses to DHCP clients. To activate a DHCP scope on SRV1, perform the following step s:
On SRV1, open DNS Manager from the Administrative Tools menu or by typing dnsmgmt.msc in the Run box.
In the left pane, expand your DHCP server and click on IPv4.
In the right pane, right-click on the scope that you want to activate, such as scope1, and select Activate.
Wait for the scope to be activated. You can verify the activation status by checking the icon next to the scope name. A green arrow indicates that the scope is active, while a red arrow indicates that the scope is inactive.
Now, the DHCP scope named scope1 on SRV1 can service client requests and lease IP addresses to DHCP clients. You can test the DHCP service by using the ipconfig /renew command on a DHCP client computer that is connected to the same subnet as the scope.

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