MENU
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
Your Azure environment contains multiple Azure virtual machines.
You need to ensure that a virtual machine named VM1 is accessible from the Internet over HTTP.
Solution: You modify an Azure Traffic Manager profile.
Does this meet the goal?
Suggested Answer: B
Get Premium AZ-900 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
112 comments · newest first
TH
Thomas Scott
1 month ago
May be B is not correct Traffic Manager is DNS-based and doesn't expose endpoints.
RA
Rajesh Chauhan
1 month ago
That's true, but Traffic Manager only distributes DNS traffic; VM1 still needs a public IP and port 80 open for HTTP access.
LI
Linda Phillips
29 days ago
Exactly, Traffic Manager distributes DNS only; VM1 still needs a public endpoint with port 80 open to allow HTTP access.
LA
Laura Brown
28 days ago
That's right, but a nuance: Traffic Manager only handles DNS, not the actual endpoint; VM1 still needs a public IP and port 80 open to serve HTTP.
GE
Geeta Dubey
1 month ago
You're right: Traffic Manager handles DNS, not actual traffic. It won't expose HTTP endpoints. To access VM1 over HTTP, VM1 must have a public IP and port 80 open (or equivalent frontend).
UM
Umar Nawaz
30 days ago
Exactly. The DNS routes at Traffic Manager, but HTTP still requires a reachable public IP on VM1 and port 80 open.
EM
Emma Mitchell
1 month ago
I was stuck by the DNS-only behavior too; I thought it would expose HTTP, but VM still needs a public IP and port 80.
SA
Samira Islam
1 month ago
Right, and because Traffic Manager is DNS-based, VM1 must have a reachable public IP and port 80 open for HTTP to work.
IS
Isha Saxena
1 month ago
Agree, Traffic Manager is DNS-based and doesn't expose endpoints; you still need a publicly reachable HTTP endpoint for VM1.
MO
Mohit Kapoor
1 month ago
That's a good point, but Traffic Manager only handles DNS. It doesn't expose HTTP endpoints, so VM1 still needs a publicly reachable endpoint.
BU
Bushra Ahmed
1 month ago
That's true, but the subtlety is Traffic Manager only handles DNS; it doesn't expose or proxy HTTP traffic, so VM1 must expose a public HTTP endpoint directly.
BR
Brian Harris
1 month ago
I was also tangled, thinking Traffic Manager could expose HTTP. That DNS-only detail clarified it for me after your note.
RO
Rosa Michel
1 month ago
You're right to wonder about exposure. Traffic Manager being DNS-based means it doesn't expose HTTP endpoints; VM1 still needs a publicly reachable HTTP endpoint.
AN
Anthony King
1 month ago
Because Traffic Manager is DNS-based and only redirects to a reachable endpoint, VM1 must itself host a public HTTP endpoint; Traffic Manager alone doesn't expose HTTP directly.
DI
Diego Ricci
1 month ago
That's right, Traffic Manager only routes DNS, VM1 must serve public HTTP. Also ensure VM1's endpoint is healthy and reachable on port 80.
PR
Priya Verma
1 month ago
Why would B be incorrect if Traffic Manager still routes HTTP traffic despite DNS-based endpoints?
ST
Stephanie Miller
1 month ago
I was stuck between B and the DNS-based endpoint idea. Realizing Traffic Manager only routes DNS, not expose endpoints, helped.
KH
Khalid Malik
1 month ago
That's true; Traffic Manager handles DNS routing, not exposing endpoints. To reach HTTP from the Internet, ensure VM1 has a public IP and port 80 reachable, not just DNS.
HA
Hana Rahman
1 month ago
Because Traffic Manager only answers DNS queries and directs clients to an endpoint, it does not proxy or guarantee HTTP reachability. B would be wrong because HTTP still travels directly to the endpoint.
NI
Nisha Tiwari
1 month ago
You're right that Traffic Manager handles DNS, but it doesn't proxy HTTP traffic; B would be incorrect because it doesn't guarantee end-to-end HTTP reachability.
RI
Rizwan Jamil
1 month ago
That's a subtle distinction: Traffic Manager doesn't route HTTP traffic; it only resolves DNS to an endpoint, and the HTTP request goes directly to that endpoint.
JI
Jian Kim
1 month ago
Yes, that's true; Traffic Manager resolves DNS only. To expose VM1 over HTTP, you still need a publicly reachable endpoint (public IP) behind the profile.
OL
Olivia Williams
1 month ago
Agree, B seems unlikely since Traffic Manager is DNS-based.
IN
Ingrid Rodriguez
1 month ago
I was stuck between A and B too, the DNS based tip made me doubt, but I realized Traffic Manager doesn't expose HTTP endpoints directly.
RI
Richard Evans
1 month ago
You're right, B is unlikely since Traffic Manager is DNS-based. But note the goal is VM1 accessibility over HTTP, which Traffic Manager alone doesn’t provide.
PA
Pallavi Joshi
1 month ago
That's true, but Traffic Manager's DNS routing directs clients to configured endpoints, which can be a VM1 HTTP endpoint. It doesn't expose endpoints itself.
MA
Magnus Esposito
1 month ago
That's true, but the subtle distinction is Traffic Manager doesn't expose endpoints itself; it routes to configured endpoints like VM1 HTTP, which must be publicly reachable.
WE
Wei Lee
1 month ago
Because Traffic Manager is DNS-based and only directs clients to endpoints, modifying the profile can meet the goal if VM1 has a public HTTP endpoint; Traffic Manager doesn't proxy, endpoints handle it.
KA
Katya Petrov
1 month ago
That's true, but the distinction is that Traffic Manager doesn't expose HTTP itself; modifying the profile affects DNS routing to VM1's public endpoint, which handles HTTP.
NA
Natasha Pedersen
1 month ago
I see it differently. B is correct because Traffic Manager only handles DNS and doesn't expose HTTP endpoints directly, you still need a reachable endpoint.
YU
Yusuf Choudhury
30 days ago
That's true, but the nuance is Traffic Manager only handles DNS; it won't expose HTTP endpoints. You still need a reachable HTTP endpoint behind VM1.
CL
Clara Colombo
30 days ago
True, and that reinforces B; Traffic Manager handles DNS and won't expose HTTP endpoints, you still need a reachable HTTP endpoint behind VM1.
KH
Khadijah Rizvi
1 month ago
I was torn between A and B too, assuming Traffic Manager exposed endpoints, but your DNS point showed a reachable endpoint is needed.
RI
Rizwan Raza
29 days ago
Yes, that's right. Since Traffic Manager is DNS-based, you still need a reachable HTTP endpoint for traffic to flow.
IB
Ibrahim Zaidi
1 month ago
You're right that Traffic Manager doesn't serve HTTP; the key distinction is that DNS-based routing only works if VM1 exposes a reachable HTTP endpoint. So Traffic Manager alone doesn't ensure HTTP access.
LU
Lucia Colombo
29 days ago
That's true, but the missing piece is VM1 must expose a public HTTP endpoint. Traffic Manager only DNS routes and won't create the endpoint.
AI
Aisha Nawaz
1 month ago
You're right Traffic Manager is DNS-based and doesn't expose endpoints. The solution meets the goal only if VM1 has a public HTTP endpoint; Traffic Manager would route to that endpoint, not host it.
JO
John Anderson
1 month ago
That's right, B is not correct. Traffic Manager doesn't expose endpoints, it routes to VM1's public HTTP endpoint.
DA
Daniel Clark
1 month ago
Agree. Traffic Manager doesn't host endpoints; it just directs traffic to VM1's public HTTP endpoint if present.
AD
Aditya Chaudhary
1 month ago
You're right. The key difference is that Traffic Manager DNS-routes to a public HTTP endpoint; it does not expose one itself on VM1. Without VM1 offering a public HTTP endpoint, the goal fails.
AM
Amit Singh
1 month ago
User N: That's true, and a subtle distinction: Traffic Manager routes to VM1's public HTTP endpoint, it doesn't create or expose the endpoint itself.
HA
Hana Malik
1 month ago
I was tangled by whether Traffic Manager actually hosts endpoints or just directs to them, and realizing it's DNS only helped.
SU
Sunita Mishra
1 month ago
Exactly. Traffic Manager is DNS-based and doesn't host endpoints, and the goal relies on VM1 having a reachable public HTTP endpoint that Traffic Manager can direct traffic to.
RA
Rachel Carter
1 month ago
I was torn between A and B too, Traffic Manager's DNS role confused me, but it can route to a public VM endpoint.
CL
Clara Larsen
1 month ago
That's true, but Traffic Manager's DNS routing still enables HTTP access if VM1 has a public endpoint, and exposure happens at the endpoint rather than in Traffic Manager.
TH
Thomas Bianchi
1 month ago
That's true, and you're right the exposure happens at the VM1 public endpoint, not in Traffic Manager itself.
JA
Jae Zhou
1 month ago
A is correct. The key difference is Traffic Manager is DNS based and routes to a public VM endpoint; it doesn't proxy HTTP traffic itself, it simply directs clients to the endpoint.
HA
Hao Cho
1 month ago
Yes, that’s true, but the subtle point is Traffic Manager only redirects DNS; VM1 still needs a public HTTP endpoint and firewall rules to be accessible.
AL
Alejandro Morozov
1 month ago
I was stuck between A and B too; the DNS bit tripped me up, but I learned Traffic Manager can route to a public VM.
HA
Hamza Raza
1 month ago
That point about DNS is partly true, but Traffic Manager doesn’t expose endpoints itself, it routes DNS to your real HTTP(S) endpoints, which must be publicly reachable.
NE
Neha Pillai
1 month ago
I think B is correct Traffic Manager is DNS-based and won't expose HTTP.
AM
Amira Baig
1 month ago
I also hesitated between A and B since DNS routing seemed unrelated to HTTP. Realizing Traffic Manager can affect accessibility clarified it.
MI
Minhee Zhang
1 month ago
That's true, but remember Traffic Manager changes which endpoint the client reaches via DNS; it doesn't host or directly expose HTTP on VM1.
MA
Manon Martinez
30 days ago
That's right, but Traffic Manager only influences DNS routing, not HTTP exposure; VM1's accessibility still relies on the endpoint being available.
AI
Aisha Islam
1 month ago
You're right that DNS routing matters. The key difference is Traffic Manager is DNS-based but it decides which endpoint your HTTP request reaches, so it can affect HTTP accessibility.
JI
Jiyeon Tanaka
1 month ago
Exactly. So Traffic Manager can affect HTTP accessibility by directing the request to the chosen endpoint.
TH
Thomas Collins
1 month ago
I felt the same, stuck between A and B thinking DNS has nothing to do with HTTP. Seeing Traffic Manager influence accessibility finally clicked.
AM
Amira Sheikh
29 days ago
Exactly. Traffic Manager modifies DNS routing, not the HTTP traffic itself, so accessibility hinges on the endpoints' public exposure and configuration, not the profile alone.
RA
Rahul Sinha
1 month ago
Agree, B is correct because Traffic Manager is DNS-based.
RA
Rajesh Reddy
1 month ago
That's true, but remember Traffic Manager only handles DNS; to make VM1 HTTP accessible, the endpoint it points to must be publicly reachable (public IP or load balancer).
AN
Anya Laurent
29 days ago
That's true, but modifying the Traffic Manager profile can meet the goal if VM1 is exposed via a public IP or load balancer. Traffic Manager handles DNS only.
AN
Ankit Pandey
1 month ago
I was torn between A and B as well, unsure how DNS routing makes HTTP reachable. That reminder that Traffic Manager handles DNS clarified it.
BI
Bilal Khan
29 days ago
That's true, but DNS based routing doesn't serve HTTP itself. Ensure the endpoints behind Traffic Manager actually expose HTTP on a public IP.
AN
Ana Larsen
1 month ago
You're right that B can’t guarantee HTTP reach; the key difference is Traffic Manager is DNS-based and only directs traffic, it doesn't serve HTTP or expose VM1 directly.
BR
Brian Collins
1 month ago
That's true, but remember Traffic Manager is DNS-based and only directs traffic; to expose HTTP publicly you still need a reachable endpoint like a load balancer or Application Gateway.
BU
Bushra Iqbal
1 month ago
Agree, Traffic Manager handles DNS, not HTTP; ensure VM1 has a public IP and an open HTTP endpoint behind it.
YU
Yusuf Raza
1 month ago
Because Traffic Manager only routes DNS requests, modifying it alone won't expose HTTP; VM1 must have a public IP with an open HTTP endpoint for Internet access.
CA
Carlos Gonzalez
1 month ago
That's true, but note the subtle distinction: Traffic Manager DNS only; VM1 still needs a public IP and an open HTTP endpoint for Internet access.
SU
Sumayya Rahman
1 month ago
I was between A and B as well, thinking Traffic Manager could serve HTTP; realizing it's DNS-based helped me focus on VM1's public IP.
SN
Sneha Nair
30 days ago
Exactly; DNS-based means VM1's public IP and an open HTTP endpoint are still required, since Traffic Manager only directs clients, not serve HTTP traffic.
KH
Khanh Pham
1 month ago
Yes, your point that Traffic Manager is DNS based is correct, however VM1 must still have a public IP and an HTTP endpoint since Traffic Manager does not serve HTTP.
JI
Jiyeon Yamamoto
1 month ago
That's right, but the goal is HTTP access; Traffic Manager doesn’t serve HTTP, so relying on it alone won’t expose VM1.
IV
Ivan Petit
1 month ago
You're right that B highlights DNS-based routing, but the tricky part is Traffic Manager doesn't expose HTTP endpoints by itself. You still need an HTTP endpoint in the backend or a public load balancer.
GA
Gaurav Kumar
1 month ago
You're right that Traffic Manager provides DNS routing, but the key is it does not publish HTTP endpoints itself. VM1 must be behind an HTTP endpoint such as a public load balancer.
HA
Hassan Abbasi
1 month ago
True, but the goal requires an HTTP endpoint publicly accessible; Traffic Manager only routes DNS, VM1 must be behind a public HTTP endpoint or load balancer.
TH
Thi Suzuki
1 month ago
That's a subtle distinction, Traffic Manager doesn't expose HTTP itself, so VM1 must have a public HTTP endpoint behind a load balancer or similar.
VI
Vikram Agarwal
1 month ago
Exactly. That distinction matters: Traffic Manager handles DNS, but you still need a reachable HTTP endpoint behind a public load balancer for VM1 to be accessible.
AL
Ali Farooqi
1 month ago
I too was tangled by the idea of exposing HTTP via Traffic Manager, until I realized endpoints matter before routing.
WA
Walid Farooqi
30 days ago
Yes, that's confusing at first; Traffic Manager handles DNS, not HTTP exposure; ensure a public HTTP endpoint behind a load balancer to reach VM1.
AL
Ali Hussain
1 month ago
I don't think B is right because Traffic Manager doesn't host HTTP but can enable internet access by routing to VM1's public HTTP endpoint.
JO
Joshua Green
1 month ago
That's true, but the distinction is that Traffic Manager doesn't host HTTP; it merely routes DNS to VM1's endpoint, so B doesn't guarantee direct HTTP exposure.
HA
Hafsa Qureshi
30 days ago
That's true, but the subtle point is Traffic Manager doesn't host HTTP; it routes to VM1's endpoint, which enables the HTTP access.
JA
James Campbell
1 month ago
I was also torn between A and B at first; Traffic Manager is DNS routing, not hosting HTTP, which clarified it for me.
GE
Geeta Gupta
1 month ago
That's right. Traffic Manager DNS routing doesn't host HTTP; it only directs clients to VM1's HTTP endpoint, so the endpoint must actually serve HTTP for access.
BI
Bilal Choudhury
1 month ago
You're right that B can route to VM1, but the key distinction is Traffic Manager doesn't host HTTP. It enables access by directing traffic to VM1's public HTTP endpoint.
RA
Rachel Robinson
1 month ago
That's true, but the key point is Traffic Manager doesn't host HTTP; it routes traffic to VM1's public HTTP endpoint, enabling access without hosting HTTP.
NI
Nisha Pandey
1 month ago
That's true, but the distinction matters: Traffic Manager doesn't expose VM1 to the Internet over HTTP; it only routes DNS traffic.
CH
Charles Mitchell
30 days ago
That's true, but the nuance is Traffic Manager handles DNS, not the HTTP exposure; it doesn't make VM1 reachable over HTTP by itself.
BU
Bushra Rahman
29 days ago
Right, the nuance matters: Traffic Manager handles DNS and doesn't expose VM1 over HTTP, you still need a publicly reachable endpoint or HTTP facing service.
HA
Hanna Bruno
1 month ago
Because Traffic Manager only routes DNS traffic, it doesn't expose VM1 over HTTP itself; you still need a reachable HTTP endpoint behind the DNS to make it accessible.
YU
Yuki Choi
29 days ago
I agree; Traffic Manager handles DNS routing, not HTTP exposure, so VM1 is accessible only via a reachable HTTP endpoint behind the DNS.
JE
Jennifer Clark
1 month ago
I was stuck on whether Traffic Manager actually exposes HTTP. That note about it only routing DNS clarified the confusion for me too.
ST
Steven Thompson
30 days ago
Exactly. The subtle distinction is that Traffic Manager only routes DNS and does not directly expose VM1 over HTTP, you still need a public endpoint or load balancer.
WA
Walid Rahman
1 month ago
Isn't DNS-based Traffic Manager only for name resolution and not for exposing HTTP endpoints?
CA
Carlos Ferrari
1 month ago
Same confusion here between A and B. I thought DNS only resolves names, but the explanation clarified Traffic Manager points clients to VM1, exposing HTTP.
OL
Olivia Taylor
30 days ago
User 3: You're right to ask. Traffic Manager is DNS-based and doesn’t expose HTTP itself; it directs clients to VM1’s HTTP endpoint so it’s reachable.
ME
Melissa Davis
1 month ago
You're right that Traffic Manager is DNS-based, but the key is it directs clients to an HTTP endpoint rather than exposing HTTP itself.
HA
Hassan Iqbal
1 month ago
That's right to an extent, but Traffic Manager doesn't expose HTTP; it uses DNS to route clients to an HTTP endpoint.
AN
Antoine Laurent
1 month ago
That's true, but to make VM1 HTTP reachable you still need an endpoint that serves HTTP (public IP or load balancer); Traffic Manager only routes DNS.
MA
Matthew Evans
1 month ago
User N: That's true, yet the key distinction is Traffic Manager provides DNS-based routing to endpoints that host HTTP; it doesn't expose HTTP itself.
JO
Johnna
5 days ago
I feel the same. Traffic Manager doesn't meet the goal.
SU
Sunshine
10 days ago
Agreed, B) No. It doesn't directly allow HTTP access.
SH
Shaun
15 days ago
I think the answer is B) No. Traffic Manager is for routing, not direct access.
YO
Youlanda
20 days ago
Just to clarify, this won't meet the goal at all.
IS
Isabella
26 days ago
No way, you need to set up a public IP or NSG rules for VM1.
RE
Reiko
1 month ago
Wait, I thought Traffic Manager could handle that?
LI
Lili
1 month ago
Totally agree, modifying the Traffic Manager won't help with HTTP access.
LE
Lettie
1 month ago
That's not the right solution. Traffic Manager is for routing, not direct access.
IR
Iraida
2 months ago
I'm not entirely sure, but I feel like we need to configure a public IP or something else for direct access.
RA
Rachael
2 months ago
This question feels familiar; I practiced a similar one where we had to set up NSGs instead.
IN
Ines
2 months ago
I think modifying a Traffic Manager profile wouldn't directly make VM1 accessible over HTTP. It seems like a "No" to me.
JO
Joana
2 months ago
I remember studying about Azure Traffic Manager, but I thought it was more for load balancing than direct access.