MENU
You manage an application that runs in a Compute Engine instance. You also have multiple backend services executing in stand-alone Docker containers running in Compute Engine instances. The Compute Engine instances supporting the backend services are scaled by managed instance groups in multiple regions. You want your calling application to be loosely coupled. You need to be able to invoke distinct service implementations that are chosen based on the value of an HTTP header found in the request. Which Google Cloud feature should you use to invoke the backend services?
Suggested Answer: B
Get Premium Professional Cloud Developer Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
36 comments · newest first
JA
Jacklyn
11 months ago
I’m surprised this isn’t a trick question!
PH
Phuong
11 months ago
Internal HTTP(S) Load Balancing could work, but it’s not as flexible.
CL
Clay
11 months ago
Wait, are you sure? I thought Service Directory might fit too.
AL
Alpha
11 months ago
Totally agree, Traffic Director is the way to go!
DI
Dick
12 months ago
I think the answer is A, Traffic Director. It handles traffic routing based on headers.
RO
Rozella
12 months ago
Service Directory sounds familiar, but I can't recall if it directly helps with invoking services based on HTTP headers. I feel like I need to review that concept again.
SH
Sharita
1 year ago
I practiced a similar question about service invocation, and I think Anthos Service Mesh might be relevant, especially for managing microservices, but I'm not confident about the specifics.
AL
Allene
1 year ago
I think Internal HTTP(S) Load Balancing could work here since it can route traffic based on headers, but I need to double-check if it supports the level of granularity we need.
ME
Melvin
1 year ago
I remember studying about Traffic Director and how it helps with service discovery and traffic management, but I'm not entirely sure if it's the best fit for this scenario.
AN
Angelica
1 year ago
This is a tough one, but I think I've got a strategy. I'm going to carefully read through the requirements again and try to match them up with the features of each option. That should help me narrow it down.
MI
Minna
1 year ago
I'm pretty confident that the answer is Internal HTTP(S) Load Balancing. It can handle the dynamic scaling of the backend services and the routing based on the HTTP header seems like a good fit.
HA
Hayley
1 year ago
Okay, I think I've got this. The key is that we need to be able to invoke different service implementations based on an HTTP header. That sounds like a job for Anthos Service Mesh, which can handle advanced routing and traffic management.
PR
Providencia
1 year ago
Hmm, I'm a bit confused by the loose coupling requirement. I'm leaning towards Traffic Director since it can handle dynamic service discovery and load balancing, but I'm not sure if that's the best fit.
CA
Cammy
1 year ago
This looks like a tricky one. I'm not sure if I fully understand the requirements, but I think Service Directory might be the way to go since it allows for service discovery and routing based on metadata.
GL
Glenn
1 year ago
I'm a bit confused on this one. The question mentions interface protocol policies, but the answer choices don't seem to directly match that. I'll need to review the ACI object types and how they relate to interface policies.
MA
Marquetta
1 year ago
Ah, I know this one! Successful partnerships require complementary strengths, a common customer base, and good chemistry between the partners. I'm pretty sure the answer is D, "All of the above."
IN
In
1 year ago
Service Directory for sure! It's the perfect solution for this use case. Plus, it's just fun to say 'Service Directory' - it's like a superhero name for your APIs!
JO
Johnetta
1 year ago
True, Traffic Director is another good option for invoking backend services based on HTTP headers.
KI
Kimbery
1 year ago
I think Traffic Director could also work well for this scenario.
LE
Lemuel
1 year ago
I agree, Service Directory makes it easy to invoke different service implementations based on HTTP headers.
TO
Torie
1 year ago
Service Directory is definitely the way to go. It's like having a superhero for your APIs!
RI
Rikki
1 year ago
Internal HTTP(S) Load Balancing could work, but it doesn't really address the dynamic service selection based on the HTTP header. I'd say Service Directory is the way to go.
LO
Lon
1 year ago
C) Anthos Service Mesh
IZ
Izetta
1 year ago
B) Service Directory
CA
Cammy
1 year ago
A) Traffic Director
RE
Rebbecca
2 years ago
Why do you think that? I thought Traffic Director would be the best choice for this scenario.
HA
Hayley
2 years ago
Hmm, I'm not sure. Anthos Service Mesh also seems like a good choice for managing and routing traffic to the backend services. But Service Directory might be the simpler solution here.
MI
Mitzie
1 year ago
Service Directory might be a simpler solution for invoking distinct service implementations.
MA
Marvel
1 year ago
I think Anthos Service Mesh could be a good option for managing traffic.
MA
Mary
2 years ago
I think I'd go with Service Directory. It seems like the best option to decouple the calling application from the backend services and allow for dynamic service discovery based on the HTTP header.
AN
Andrew
1 year ago
D) Internal HTTP(S) Load Balancing
KR
Kristofer
1 year ago
C) Anthos Service Mesh
OL
Olene
1 year ago
B) Service Directory
TR
Tresa
1 year ago
A) Traffic Director
CA
Catina
2 years ago
I disagree, I believe the correct answer is C) Anthos Service Mesh.
RE
Rebbecca
2 years ago
I think the answer is A) Traffic Director.