最新的Microsoft Azure Administrator (AZ-104 Korean Version) - AZ-104 Korean免費考試真題

See below explanation
Explanation:
Azure portal create public container
To create a container in the Azure portal, follow these steps:
Step 1. Navigate to your new storage account in the Azure portal.
Step 2. In the left menu for the storage account, scroll to the lob service section, then select Blobs.
Select the + Container button.
Type a name for your new container: bios
Set the level of public access to the container: Select anonymous access.

Step 3. Select OK to create the container.
References:
https://docs.microsoft.com/en-us/azure/storage/blobs/storage-quickstart-blobs-portal

說明：（僅 Fast2test 成員可見）

說明：（僅 Fast2test 成員可見）

Explanation:
Box 1: Yes
VM1 has public IP address 131.107.10.10.
VM1 is connected to VNet1/Subnet1.
Networking is allowed for VNet1 on subnet for IP addresses 131.107.10.10, and 150.120.10.10, and for 170.20.10.10.
Box 2: No
VM2 is on VNet1/Subnet2.
Networking only allowed on Subnet1.
Box 3: No
VM3 has public IP address 170.20.10.10.
VM3 is connected to VNet1/Subnet1.
Networking is allowed for VNet1 on subnet for IP addresses 131.107.10.10, and 150.120.10.10, and for 170.20.10.10.
VM3 can use its public address 170.20.10.10.

Explanation:
Box 1: No
Azure DNS provides automatic registration of virtual machines from a single virtual network that's linked to a private zone as a registration virtual network. VM5 does not belong to the registration virtual network though.
Box 2: No
Forward DNS resolution is supported across virtual networks that are linked to the private zone as resolution virtual networks. VM5 does belong to a resolution virtual network.
Box 3: Yes
VM6 belongs to registration virtual network, and an A (Host) record exists for VM9 in the DNS zone. By default, registration virtual networks also act as resolution virtual networks, in the sense that DNS resolution against the zone works from any of the virtual machines within the registration virtual network.
Reference:
https://docs.microsoft.com/en-us/azure/dns/private-dns-overview

See below explanation
Explanation:
You can filter network traffic to and from Azure resources in an Azure virtual network with a network security group. A network security group contains security rules that allow or deny inbound network traffic to, or outbound network traffic from, several types of Azure resources.
A network security group contains security rules that allow or deny inbound network traffic to, or outbound network traffic from, several types of Azure resources.
Step A: Create a network security group
A1. Search for and select the resource group for the VM, choose Add, then search for and select Network security group.
A2. Select Create.

The Create network security group window opens.
A3. Create a network security group
Enter a name for your network security group.
Select or create a resource group, then select a location.
A4. Select Create to create the network security group.
Step B: Create an inbound security rule to allows HTTPS over TCP port 443 B1. Select your new network security group.
B2. Select Inbound security rules, then select Add.
B3. Add inbound rule
B4. Select Advanced.
From the drop-down menu, select HTTPS.
You can also verify by clicking Custom and selecting TCP port, and 443.
B5. Select Add to create the rule.
Repeat step B2-B5 to deny TCP port 80
B6. Select Inbound security rules, then select Add.
B7. Add inbound rule
B8. Select Advanced.
Clicking Custom and selecting TCP port, and 80.
B9. Select Deny.
Step C: Associate your network security group with a subnet
Your final step is to associate your network security group with a subnet or a specific network interface.
C1. In the Search resources, services, and docs box at the top of the portal, begin typing Web01.
When the Web01 VM appears in the search results, select it.
C2. Under SETTINGS, select Networking. Select Configure the application security groups, select the Security Group you created in Step A, and then select Save, as shown in the following picture:

References:
https://docs.microsoft.com/en-us/azure/virtual-network/tutorial-filter-network-traffic

說明：（僅 Fast2test 成員可見）

Explanation:
Role3 is an Azure subscription role and you are able to clone Azure subscription roles and custom roles.
https://learn.microsoft.com/en-us/azure/role-based-access-control/custom-roles-portal Role4 is an Azure AD role and it just are able to clone customer roles.
https://learn.microsoft.com/en-us/azure/active-directory/roles/custom-create

說明：（僅 Fast2test 成員可見）