A peat-bog teammate “optimizes” Domain 4 by adding Azure Cache for Redis and an App Service autoscale rule. What stays in scope for this domain?
Select an answer to reveal the explanation.
Short Explanation
Domain 4 is the skinny Application Insights lane—tests, alerts, metrics, logs, traces. Redis and autoscale live elsewhere; do not smuggle them in as “optimize.”
Full Explanation
On the current AZ-204 outline, Domain 4 (monitor, troubleshoot, and optimize) centers on Application Insights: instrumentation, metrics, logs, traces, availability tests, and alerts. For the peat-bog teammate who “optimizes” by adding Azure Cache for Redis and an App Service autoscale rule, those may be useful elsewhere, but they are not the Domain 4 skill group. Keep Domain 4 answers on Insights availability tests, alerts, and related telemetry.
Redis cache-hit tuning as the primary Domain 4 skill fails because Redis performance tuning is not the Application Insights monitoring skill the domain describes.
CDN edge rules marketed as Application Insights availability fails because CDN configuration is not Insights availability testing, even if both relate loosely to “being fast online.”
App Service autoscale rules as the Domain 4 optimize answer fails the domain boundary: autoscale belongs with compute hosting (Domain 1), not as a substitute for Insights availability tests and alerts in Domain 4.
Exam caveat: products can appear in multiple stories—Redis and autoscale are real Azure features—but exam items tagged to Domain 4 expect Insights-centric answers unless the stem clearly shifts domains. Operational check: when reviewing a study map or practice set labeled Domain 4, confirm each “optimize” answer references Insights tests, alerts, or telemetry—not cache SKUs or scale-out rules alone.