The health-department Fn team wants a span tree for each immunization-appointment Function invocation. Where should those traces be sent?
Select an answer to reveal the explanation.
Short Explanation
Traces belong in an APM domain—the collector that draws the span tree. Monitoring charts and Logging search will not show that tree, and Service Mesh is not the Functions tracing path.
Full Explanation
Official Functions tracing sends spans to Application Performance Monitoring. An APM domain is the collector instance that stores and visualizes those traces—the place the health-department Fn team should send a span tree for each immunization-appointment Function invocation. Monitoring charts, Logging lines, and mesh products do not replace that APM domain role for function traces.
Sending spans only into OCI Monitoring charts as ordinary metric data points loses the span-tree structure; metrics answer how often/how long, not the hierarchical trace. Logging Search plaintext lines are for log content, not the APM trace store. OCI Service Mesh is not the required tracing product for Functions—Functions tracing docs point at APM domains, not mesh as the mandatory collector.
Exam caveat: you still need IAM and application/function tracing enablement against the domain’s data keys; creating a domain alone does not emit spans until tracing is enabled on the app and functions. Operational check: create or select an APM domain, enable Functions application tracing attached to that domain, enable the function, invoke an appointment call, and open the resulting trace in APM rather than looking for spans inside Monitoring or Logging alone.