A company has an application that runs across multiple AWS Regions. The application is experiencing performance issues at irregular intervals. A developer must use AWS X-Ray to implement distributed t

Question

Options

• AUse the X-Ray console to add annotations for AWS services and user-defined services.
• BUse Region annotation that X-Ray adds automatically for AWS services. Add Region annotation
• CUse the X-Ray daemon to add annotations for AWS services and user-defined services.
• DUse Region annotation that X-Ray adds automatically for user-defined services. Configure X-Ray

• A
  7% (2)
• B
  79% (23)
• C
  3% (1)
• D
  10% (3)

Explanation

Option B is correct because AWS X-Ray automatically appends a Region annotation to traces for AWS managed services (like Lambda, DynamoDB, etc.), enabling multi-region filtering out of the box. For user-defined (custom) services, developers must explicitly configure the X-Ray SDK in their application code to add Region annotations - this combination gives full visibility across regions for troubleshooting.

Why the distractors are wrong:

• A is wrong because you use the X-Ray SDK (not the console) to add annotations programmatically; the console is a visualization/analysis tool, not an instrumentation tool.
• C is wrong because the X-Ray daemon is a relay agent that buffers and forwards trace segments to the X-Ray API - it does not add annotations; that responsibility belongs to the SDK.
• D is wrong because it inverts the truth: X-Ray adds Region annotations automatically for AWS services, not user-defined services; custom services require explicit SDK configuration.

Memory tip: Think "AWS = automatic, custom = configure it yourself." AWS-managed services get Region metadata for free; anything your team wrote needs manual SDK instrumentation to carry the same context.

No community discussion yet for this question.