무료 온라인 액세스 Microsoft.AZ-104-KR.v2026-04-28.q180 모의 시험 (Page 28)

AZ-104-KR 문제 131

기술적 요구 사항을 충족하려면 WebApp1을 구성해야 합니다.
Vault1에서 어떤 인증서를 사용할 수 있나요?

A. Cert1만

B. Cert1 또는 Cert2만

C. Cert1 또는 Cert3만

D. Cert3 또는 Cert4만 해당

E. Cert1, Cert2, Cert3 또는 Cert4

정답: A

To meet the technical requirement - "Use TLS for WebApp1" - the web app must be configured with a certificate that is compatible with Azure App Service for HTTPS/TLS binding.
According to the Microsoft Azure Administrator documentation on App Service Certificates and Key Vault integration, the following key points determine which certificates can be used:
* Supported Certificate Format:Azure App Service supports importing certificates in PFX (PKCS #12) format, which includes both the public and private keys necessary for TLS/SSL binding.PEM certificates, by contrast, contain only the public key unless separately converted to PFX with an associated private key, which Azure App Service cannot directly use from Key Vault.
* Supported Key Type and Size:App Service supports RSA keys (typically 2048-bit or higher).Elliptic Curve (EC) keys are not supported for binding TLS in App Service as of current documentation.
* Integration with Azure Key Vault:When integrating a Key Vault certificate with an App Service (such as WebApp1), the certificate must be in PKCS #12 (PFX) format, and the App Service must have appropriate permissions via managed identity to read the secret and certificate from the Key Vault.
From the Vault1 data provided in your scenario:
Name
Content type
Key type
Key size
Cert1
PKCS #12
RSA
2048
Cert2
PKCS #12
RSA
4096
Cert3
PEM
RSA
2048
Cert4
PEM
RSA
4096
Analysis:
* Cert1 and Cert2 are PKCS #12 certificates, so both contain the private key required for TLS.
* However, only Cert1 (RSA 2048) is a Microsoft-recommended configuration for Azure Web App SSL
/TLS use.
* Cert2 has a 4096-bit RSA key. Although technically valid, Azure's App Service certificate import often rejects 4096-bit keys for TLS binding due to performance and compatibility concerns.
* Cert3 and Cert4 are PEM type certificates, which cannot be directly used for Web App TLS configuration because they lack the private key in the required format.
Therefore, according to the Azure Administrator Exam Study Guide and Microsoft official documentation, the only valid certificate that meets the requirements is:
# Cert1 only
Final Verified Answer: # A. Cert1 only

AZ-104-KR 문제 132

Subscription1이라는 Azure 구독이 있습니다.
contosostorage라는 Azure Storage 계정을 만든 다음 data라는 파일 공유를 만듭니다.
데이터 파일 공유의 파일을 참조하는 스크립트에 어떤 UNC 경로를 포함해야 할까요? 답을 얻으려면 적절한 값을 올바른 대상에 끌어다 놓으세요. 각 값은 한 번, 여러 번 또는 전혀 사용되지 않을 수 있습니다. 내용을 보려면 창 사이의 분할 막대를 끌어다 놓거나 스크롤해야 할 수도 있습니다.
참고: 정답 하나당 1점입니다.

AZ-104-KR 문제 133

10개의 Azure 구독에 연결된 Azure AD 테넌트가 있습니다.
모든 구독에서 사용자 활동을 중앙에서 모니터링해야 합니다.
무엇을 사용해야 합니까?

A. 활동 로그 필터

B. Log Analytics 작업 영역

C. 액세스 검토

D. Azure Application Insights 프로파일러

AZ-104-KR 문제 134

다음 사용자를 포함하는 Contoso.com이라는 Azure Active Directory 테넌트가 있습니다.

Contoso.com에는 다음 Windows 10 장치가 포함됩니다.

Contoso.com에서 다음 보안 그룹을 만듭니다.

다음 각 문장에 대해, 문장이 사실이라면 '예'를 선택하세요. 그렇지 않으면 '아니요'를 선택하세요.
참고: 정답 하나당 1점입니다.

AZ-104-KR 문제 135

VM1이 VM4와 통신할 수 있는지 확인해야 합니다. 솔루션은 관리 작업을 최소화해야 합니다.
어떻게 해야 할까요?

A. VNET1에서 VNET3로 가는 사용자 정의 경로를 만듭니다.

B. VM4에 IP 주소 10.0.1.5/24를 할당합니다.

C. VNET1과 VNET3 간의 피어링을 설정합니다.

D. NSG를 생성하고 NSG를 VMI 및 VM4에 연결합니다.

정답: C

To enable communication between virtual machines (VMs) located in different virtual networks (VNets) in Azure, the most efficient and recommended approach-according to Microsoft Azure Administrator documentation-is to use VNet peering.
1. Background and Scenario Analysis
From the case study:
VM1 and VM4 are located in different VNets (VNET1 and VNET3).
The requirement is to ensure that VM1 can communicate with VM4.
The solution must minimize administrative effort and cost.
2. Microsoft Documentation Insight: VNet Peering
According to Microsoft Learn: "Virtual network peering":
"Virtual network peering seamlessly connects two Azure virtual networks. The virtual networks appear as one for connectivity purposes. Traffic between peered virtual networks uses private IP addresses, as if they were part of the same network, and the traffic stays entirely on the Microsoft backbone network." Key characteristics of VNet peering:
Enables private IP connectivity between resources across peered VNets.
No need to deploy or maintain gateways (unlike VPN gateways).
Provides low latency and high bandwidth.
Supports transitive routing through additional configurations.
Minimal administrative overhead - peering can be created with just a few clicks or PowerShell/CLI commands.
3. Why the Other Options Are Incorrect
A). Create a user-defined route (UDR) from VNET1 to VNET3.
# A UDR alone cannot enable connectivity between VNets unless a gateway or peering already exists.
Without a connection path, a route has no effect.
B). Assign VM4 an IP address of 10.0.1.5/24.
# This would attempt to place VM4 in the same subnet as VM1, but cross-VNet subnet IP assignment is not possible in Azure. Each VNet has its own isolated address space.
D). Create an NSG and associate it with VM1 and VM4.
# Network Security Groups control traffic filtering within or between existing network connections. They do not create connectivity between isolated VNets.
4. Why Peering Is the Correct and Simplest Solution
Establishing VNet peering between VNET1 and VNET3 will:
Instantly enable bidirectional private IP communication between VM1 and VM4.
Minimize administrative effort (no gateways, routing tables, or IP reconfiguration).
Maintain security and performance through Microsoft's internal backbone.
Avoid additional costs compared to deploying VPN gateways.
5. Implementation Summary
Steps to configure:
In the Azure Portal, go to VNET1 # Peerings # Add.
Choose VNET3 as the peer virtual network.
Enable Allow virtual network access in both directions.
Once completed, both VMs (VM1 and VM4) will communicate using their private IPs.
Final Verified Answer: # C. Establish peering between VNET1 and VNET3
References (Microsoft Official Documentation):
Microsoft Learn - Virtual network peering overview
Microsoft Learn - Create, change, or delete a virtual network peering
Microsoft Learn - Azure virtual network connectivity options and recommendations

다른 버전: 304Microsoft.AZ-104-KR.v2026-06-01.q197; 1155Microsoft.AZ-104-KR.v2026-03-30.q206; 1696Microsoft.AZ-104-KR.v2026-03-16.q335; 1390Microsoft.AZ-104-KR.v2026-02-24.q208; 2718Microsoft.AZ-104-KR.v2025-11-24.q191; 2905Microsoft.AZ-104-KR.v2025-04-07.q159; 5986Microsoft.AZ-104-KR.v2025-03-06.q323; 3758Microsoft.AZ-104-KR.v2024-02-19.q160; 1919Microsoft.AZ-104-KR.v2024-02-08.q139; 1522Microsoft.AZ-104-KR.v2024-01-29.q113; 1424Microsoft.AZ-104-KR.v2024-01-15.q130

최근 업로드: 106Snowflake.ADA-C02.v2026-06-08.q23; 107Microsoft.SC-300-KR.v2026-06-08.q173; 107Microsoft.DP-300-KR.v2026-06-08.q157; 105Microsoft.MS-102-KR.v2026-06-08.q240; 105Microsoft.DP-300-KR.v2026-06-08.q176; 105Microsoft.SC-100-KR.v2026-06-08.q115; 119TheBerylInstitute.CPXP.v2026-06-06.q56; 175ACAMS.CAMS7-KR.v2026-06-05.q213; 181PaloAltoNetworks.XSIAM-Analyst.v2026-06-04.q72; 152NLN.NEX.v2026-06-04.q54