試験Mule-101 トピック5 問題42 スレッド
Salesforce Mule-101のリアル試験問題集
問題 #: 42
トピック #: 5
問題 #: 42
トピック #: 5
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?
おすすめの解答：D 解答を投票する
The Challenge: In a microservices architecture, a single user request might traverse dozens of different services. If an error occurs or latency is high, looking at the logs of just one service isn't enough.
Distributed Tracing: This is the specific technology used to track a request as it hops between services.
How it works: It assigns a unique Trace ID (Correlation ID) to the request at the entry point. This ID is passed to every downstream service. Tracing tools (like Anypoint Monitoring's Telemetry or Jaeger) verify the full path, showing exactly how long the request spent in each hop.
Distributed Tracing: This is the specific technology used to track a request as it hops between services.
How it works: It assigns a unique Trace ID (Correlation ID) to the request at the entry point. This ID is passed to every downstream service. Tracing tools (like Anypoint Monitoring's Telemetry or Jaeger) verify the full path, showing exactly how long the request spent in each hop.
Tazaki 2026-03-05 07:46:41
コメント
他人の解答コメントを賛成するのも、その解答に一票を入れることになります。したがって、すでに同じ意見の投票コメントが存在する場合、新規コメントをする代わりに賛成することもできます。
コメントを通報する
コメント中
今すぐ 新規登録 / ログイン （無料です）。