How deeply is RUM tested in the Dynatrace Associate exam - settings, configuration or just concepts?

[billyharris]

Hello,

I'm currently preparing for the Dynatrace associate certification exam and RUM (real user monitoring) is one of the areas I'm finding a bit hard to scope out.

I understand that knowing RUM settings and their purpose is important for the practical section but I'm struggling to figure out how deep I need to go. Specifically, I'd love some clarity on the following:

I'd love some clarity on a few things. First, I'm not sure whether RUM is tested mainly at a conceptual level like understanding what it is and why it's used or whether the practical section actually asks you to do hands-on configuration tasks.

I'm also not sure which RUM settings I should really focus on like user session properties, user tagging, conversion goals, or injection rules. On top of that, I'm wondering if there are any RUM-related DQL queries I should get comfortable with.

And lastly, does Real User Monitoring for mobile apps get tested separately from web and browser RUM or is it all covered together?

I've gone through the Dynatrace essentials learning plan on DT university but feel the RUM coverage there is fairly high-level. If anyone who has recently taken the updated exam (with the practical section) could share their experience, I'd really appreciate it!

Thanks in advance

[patrickrsmith · Accepted solution]

Hi @billyharris, RUM spans both sections, so it’s worth covering both angles.

You should know what RUM is, why it’s used, and where the main settings live. In the practical part, I mostly saw things like recognizing existing setups or checking configurations not building anything complex from scratch. For me, the Dynatrace essentials learning plan was enough for the concepts and doing some scenario-style practice questions available on CertBoosters helped me get a better feel for the level of detail they expect.

Settings to focus on, I’d prioritize:

• Application detection rules - how traffic gets grouped into apps
• User tagging rules - assigning meaningful usernames to sessions
• Agentless RUM - typically used when OneAgent can’t be installed on a host
• Data retention values - these come up a lot in MCQs and are easy points once memorized (e.g., non-aggregated user actions = 10 days, sessions/aggregated data = 35 days, session replay = configurable up to 35 days)

Conversion goals and session properties are worth a conceptual read but felt less heavily tested.

DQL does appear in the practical section. Be comfortable querying user.sessions and user.events and building basic timeseries queries. most of this shows up in notebooks.

Mobile vs Web: Not tested as separate domains but know the differences: mobile sessions timeout after 10 minutes of inactivity (vs. 35 minutes for web), crashes are grouped by app version and pages are web-only (mobile uses views).

the official Dynatrace docs are available during the practical section but time is tight. Knowing where things live and skipping/returning to harder questions really helps. Good luck!