An E-commerce application is built using microservices architecture design with several components. In AppDynamics, how should the Transaction…

In AppDynamics, when managing complex applications such as those built on a microservices architecture, Transaction Detection rules should be logically grouped and applied using "Scopes." A scope defines a specific logical grouping of tiers or nodes within an application environment. By assigning a custom transaction detection rule to a specific scope, administrators can precisely control how business transactions are identified and named for that particular subset of microservices, without affecting the global application rules. This prevents rule conflicts and ensures that discovery is tailored to the unique frameworks, entry points, or naming conventions of each distinct microservice component.

A. Automatic Discovery applies global default rules across the entire application, which lacks the granular control needed for distinct components in a microservices architecture.

C. Transaction Groups are used to visually organize and aggregate already-discovered Business Transactions in the UI, not to define or group the detection rules themselves.

D. Backend Detection rules define how downstream databases or external services are identified, rather than grouping entry point detection rules for the microservices themselves.

1. Cisco AppDynamics Official Documentation, "Transaction Detection Rules," Section: Scope-Level Rules.

2. Cisco AppDynamics Official Documentation, "Business Transactions," Section: Managing Complex Architectures.