Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Microsoft Exam AZ-800 Topic 3 Question 50 Discussion

Actual exam question for Microsoft's AZ-800 exam
Question #: 50
Topic #: 3
[All AZ-800 Questions]

You have an on-premises server named Server1 that runs Windows Server. Server1 contains an app named App1 and a firewall named Firewall1.

You have an Azure subscription.

Internal users connect to App1 by using WebSockets.

You need to make App1 available to users on the internet. The solution must minimize the number of inbound ports open on Firewall 1.

What should you include in the solution?

Show Suggested Answer Hide Answer
Suggested Answer: A

To ensure that all computers in the domain use DNSSEC to resolve names in the adatum.com zone, you'll need to configure both the DNS servers and the client computers. Here's how you can do it:

Step 1: Sign the adatum.com Zone First, you need to sign the adatum.com DNS zone. This can be done using the DNS Manager or PowerShell. Here's a PowerShell example:

Add-DnsServerSigningKey -ZoneName 'adatum.com' -CryptoAlgorithm RsaSha256

Set-DnsServerDnsSecZoneSetting -ZoneName 'adatum.com' -DenialOfExistence NSEC3 -NSEC3Parameters 1,0,10,''

This will add a signing key and configure DNSSEC for the zone with NSEC3 parameters.

Step 2: Configure DNS Servers Ensure that your DNS servers are configured to support DNSSEC. This includes setting up trust anchors for the zones that you want to validate and configuring the DNS servers to provide DNSSEC validation for DNS queries.

Step 3: Configure DNS Clients For DNSSEC validation to occur on the client side, the client computers must be configured to trust the DNS server's validation process. This typically involves configuring the client's DNS settings to point to a DNS server that supports DNSSEC.

Step 4: Validate Configuration You can validate that DNSSEC is working correctly by using tools like nslookup or dig to query DNS records and check for the presence of DNSSEC signatures in the responses.

Note: The exact steps may vary depending on your environment and the version of Windows Server you are using. Ensure that you have the appropriate administrative rights to make these changes and that you test the configuration in a controlled environment before deploying it domain-wide12.

By following these steps, you should be able to ensure that all computers in your domain use DNSSEC to resolve names in the adatum.com zone.


Contribute your Thoughts:

Lorean
1 months ago
I'd go with Option D. Azure Application Gateway is a powerful and versatile solution that can handle all sorts of traffic, including WebSockets. Plus, it has that cool name - who doesn't love a good 'Gateway'?
upvoted 0 times
...
Charisse
1 months ago
ARR Version 2? That's a blast from the past! I doubt that's the best solution for this modern cloud-based scenario.
upvoted 0 times
Sharita
6 days ago
Yeah, Azure Application Gateway can help minimize the number of inbound ports open on Firewall1.
upvoted 0 times
...
Felix
16 days ago
I think Azure Application Gateway would be the best option for this scenario.
upvoted 0 times
...
...
Omega
1 months ago
Web Application Proxy sounds interesting, but I'm not sure it can handle the WebSockets requirement. Maybe it's worth looking into further.
upvoted 0 times
Lettie
6 days ago
C) Azure Relay
upvoted 0 times
...
Evan
17 days ago
B) Web Application Proxy
upvoted 0 times
...
Clare
18 days ago
A) Microsoft Application Request Routing (ARR) Version 2
upvoted 0 times
...
...
Angelo
2 months ago
I'm leaning towards Application Gateway. It can handle the WebSockets traffic and provide a single point of entry for external users, keeping the firewall locked down.
upvoted 0 times
Pamella
10 days ago
I agree, D) Azure Application Gateway sounds like the best solution. It can handle the WebSockets traffic efficiently while keeping the firewall secure.
upvoted 0 times
...
Lino
12 days ago
D) Azure Application Gateway is another option. It can provide SSL termination and load balancing for WebSockets traffic to App1.
upvoted 0 times
...
Fairy
12 days ago
I don't think Azure Relay is the best option in this scenario. Application Gateway seems like a better fit.
upvoted 0 times
...
Leonora
20 days ago
B) Web Application Proxy would be a good choice. It can securely publish App1 to the internet without exposing additional ports.
upvoted 0 times
...
Jannette
1 months ago
What about Azure Relay? Would that work as well?
upvoted 0 times
...
Ryann
2 months ago
I agree, it can handle the WebSockets traffic efficiently.
upvoted 0 times
...
Myra
2 months ago
I think Azure Application Gateway is the way to go.
upvoted 0 times
...
...
Laine
2 months ago
Azure Relay seems like a good choice here. It can expose on-premises resources to the internet without opening up a ton of ports on the firewall.
upvoted 0 times
...
Janey
2 months ago
I'm not sure about Azure Application Gateway. I think we should consider using Azure Relay instead.
upvoted 0 times
...
Alpha
3 months ago
I agree with Lillian. Azure Application Gateway can help minimize the number of inbound ports open on Firewall1.
upvoted 0 times
...
Lillian
3 months ago
I think we should include Azure Application Gateway in the solution.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77