MENU
A DevOps team has adequate observability of individual system behavior and performance, but it struggles to track the entire lifecycle of each request across different microservices.
Which additional observability approach should this team consider adopting?
Suggested Answer: B
Get Premium Salesforce Certified MuleSoft Platform Integration Architect (Mule-Arch-202) Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
31 comments · newest first
AM
Amber
7 months ago
Yeah, tracing is essential for understanding the full request lifecycle.
BU
Bulah
7 months ago
Tracing shows the path of requests. Very important for microservices!
MA
Malcolm
7 months ago
I feel like analytics could help too, but not as much as tracing.
GO
Goldie
7 months ago
Agreed! Metrics are useful, but tracing gives a complete picture.
CH
Cherri
7 months ago
I think tracing is the way to go. It helps track requests across services.
DO
Dorian
7 months ago
Analytics could help, but it’s not as direct as tracing.
DA
Daron
8 months ago
Metrics are important too, but tracing seems more relevant.
FR
Francoise
8 months ago
Wait, can tracing really handle all that?
DE
Delmy
8 months ago
Totally agree, C is the best choice!
DO
Dorethea
9 months ago
I think tracing is the way to go here.
TA
Tambra
9 months ago
Tracing is the answer, no doubt. Gotta follow that request like a detective!
LU
Luisa
9 months ago
Tracing, baby! The only way to really see what's happening end-to-end.
MA
Maddie
9 months ago
C) Tracing is the answer. Anything else is just a band-aid.
SE
Serina
9 months ago
Tracing, for sure. Can't beat that for understanding the full lifecycle.
RO
Rozella
9 months ago
Definitely C. Tracing is the only way to get that end-to-end visibility they need.
TO
Torie
10 months ago
Analytics sounds interesting, but I feel like it might not provide the detailed request tracking we need.
CA
Cathrine
10 months ago
I remember we discussed metrics in class, but they seem more about performance rather than tracking request lifecycles.
MA
Marsha
10 months ago
I think tracing might be the right choice here since it helps track requests across microservices, but I'm not entirely sure.
MA
Marti
10 months ago
Tracing is definitely the way to go. It will allow us to see the full path of each request and identify any bottlenecks or issues across the different microservices.
RO
Roslyn
10 months ago
Data mining could also be an interesting approach, but I'm not sure it would give us the level of visibility we need on the request lifecycle. Tracing is probably the safer bet.
LA
Lashon
10 months ago
C) Tracing is the way to go. Gotta see that request journey across all the services!
EV
Evangelina
11 months ago
Tracing seems like the obvious choice to me. It's specifically designed to help teams understand the end-to-end flow of requests through a distributed system.
CA
Carole
11 months ago
Data mining seems too complex for this issue. Stick with tracing.
DA
Danica
11 months ago
I vaguely recall a practice question about observability, and tracing was highlighted as crucial for understanding request flows.
GL
Glenn
11 months ago
I'm a bit confused on the difference between metrics and tracing. Can someone clarify which one would be better for this scenario?
JU
Jutta
12 months ago
I think tracing would be the best approach here to track the entire lifecycle of each request across different microservices.
LE
Levi
6 months ago
Tracing will give us the visibility we need across services.
JO
Joanna
6 months ago
I think analytics could help, but tracing is the best fit.
LA
Lavonna
6 months ago
Metrics are important too, but tracing is more comprehensive.
ME
Meaghan
6 months ago
Definitely! It provides a clear view of the request flow.
OR
Oren
11 months ago
I agree, tracing seems essential for tracking requests.