Study guide

3.3 Merging Questions to Add Columns

Tanium Certified Operator TCO

Track your progress as you read

Finished sections get a check mark.

1 Tanium Certified Operator Exam and Platform Foundations

1.1 The Tanium Certified Operator Exam: Blueprint, Logistics and Certification Path 1.2 Tanium Platform Components, Client Registration and Linear Chain Peering

2 Asking Questions (22% of the TCO Blueprint)

2.1 Sensors: Execution Model, Output Structure and Data Types 2.2 Parameterized Sensors and Question Parameter Syntax 2.3 Issuing Questions in Interact: Ask a Question, Question Builder and Question Anatomy 2.4 Creating Saved Questions: Reissue Intervals, Merge and Drill-Down Flags, and RBAC 2.5 Defending Tanium as an Efficient User of Network Resources

3 Refining Questions (23% of the TCO Blueprint)

3.1 Targeting Endpoints: from and with Filters, Operators and Boolean Logic 3.2 Drilling Down into Question Results 3.3 Merging Questions to Add Columns 3.4 Computer Groups: Management versus Filter, Dynamic versus Manual 3.5 Custom Tags and Tag-Based Grouping

4 Taking Action (15% of the TCO Blueprint)

4.1 Packages: Anatomy, Command Syntax, Parameters and File Distribution 4.2 Deploying Actions: Entry Points, Targeting, Distribution and Approval 4.3 Verifying Endpoint State and Automating with Scheduled Recurring Actions

5 Navigation and Basic Module Functions (23% of the TCO Blueprint)

5.1 Console Layout, the Main Menu and Where Things Live 5.2 Operations Modules: Deploy, Patch, Asset, Performance and Provision 5.3 Security and Risk Modules: Threat Response, Comply, Enforce, Reveal, Discover and Integrity Monitor 5.4 Interpreting Module-Specific Historical Results and Tanium Data Service 5.5 Choosing the Right Area: Client Status, Direct Connect and Action History 5.6 Content Sets, Roles and Personas: Why You Can See What You Can See

6 Report Generation and Data Export (17% of the TCO Blueprint)

6.1 Exporting Question Results: CSV, Headers, Flatten Rows and Copy 6.2 Creating Reusable Reports with Tanium Reporting 6.3 Dashboards, Boards and Metric Sources: Trends, Its Replacement and Migration 6.4 Scheduled Delivery and Exporting to External Systems with Tanium Connect

3.3 Merging Questions to Add Columns

Key Takeaways Explain This Topic AI

Merging issues a second question in the background and re-displays the Question Results grid with one or more additional columns for the merged sensors.

Merge operations automatically apply to all results, so unlike drill-down there is no need to select grid rows before merging.

Only non-counting questions can be used in merge operations, so a counting question must first be made non-counting by adding a per-endpoint sensor such as Computer Name.

In a merge question you add sensors to the get clause but not filters to the from clause, because the from clause is set automatically from the rows in the results grid.

A saved question appears on the Merge dialog only when it is in a content set you can read and has the setting that displays it in the list of questions available to merge.

Last updated: August 2026

3.3 Merging Questions to Add Columns

Quick overview: Merge answers a different need from drill-down. Question results often lead to additional questions — you have a list of endpoints and running processes, and now you want the last logged-in user next to each one. Merging issues a second question in the background and re-displays the Question Results grid with one or more additional columns . It applies to all results automatically, and it accepts only non-counting questions .

1. What merging is for

Tanium's own framing: the results of a question that returns computer names and running processes might indicate that some endpoints are running a suspicious process; you can merge the initial question with another question to learn more information, such as the last logged-in user.

The pattern is enrichment . You are not narrowing the population — you are widening what you know about it. BEFORE MERGE AFTER MERGE

  • ----------- -----------
  • Computer Name | Running Process Computer Name | Running Process | Last Logged In User
  • WKS-0101 | odd.exe WKS-0101 | odd.exe | corp\jsmith
  • WKS-0233 | odd.exe WKS-0233 | odd.exe | corp\aroy
  • SRV-0410 | odd.exe SRV-0410 | odd.exe | corp\svc_backup

That third column is what turns a technical finding into an actionable one — three endpoints, but one of them is a service account on a server, which is a different conversation from two workstations.

  • 2. The rules that govern merging
  • Merges apply to everything

Merge operations automatically apply to all results. You do not need to select grid rows before merging. This is the single most common point of confusion between merge and drill-down, and it is a favourite exam discriminator.

Only non-counting questions

You can use only non-counting questions in merge operations.

A counting question groups identical results and shows a Count ; a non-counting question returns one row per endpoint. Merging a per-endpoint attribute into an aggregated row is meaningless — there is no single "last logged-in user" for the 32,000 endpoints collapsed into one Windows 11 row — so the platform simply does not allow it.

Tip

The fix when Merge refuses your question: add a sensor that is unique per endpoint — Computer Name is the usual choice — to the get clause. That makes every row distinct, converts the question to non-counting, and merging becomes available.

3. The workflow

On the Question Results page, click Merge in the grid toolbar.

Add questions using one of the tabs, then click Merge :

Saved Questions — lists saved questions assigned to content sets for which you have Saved Question read permission, and which have the Display this question in the list of questions that are available to merge setting enabled.

Create / build a question — compose the merge question directly.

The Question Results grid re-displays with the additional columns.

Use the Edit button in the grid header to modify the merge settings afterwards.

The from clause is handled for you

When you build a merge question, you add sensors to the get clause but you do not add filters to the from clause. The from clause is determined automatically by the rows in the Question Results grid. Trying to re-specify targeting in a merge question is a category error — the population is already fixed by the question you are merging into.

4. Merge versus drill down, side by side

  • Merge Drill down
  • Intent Add attributes to the population you already have Narrow to the endpoints behind selected rows
  • Row selection Not needed — applies to all results Required
  • Output Same grid, extra columns New grid, fewer endpoints
  • from clause Set automatically by the grid contents Filters the selected results
  • Question type Non-counting only Works from counting or non-counting results
  • Saved question flag Available to merge Available for drilling down (with a Show all questions override)
  • Typical trigger "I need one more column" "Which machines were those?"
  • 5. Worked example: from a distribution to a decision

Requirement: identify which endpoints are running an out-of-date browser build, and who is using them, so the service desk can contact the right people.

Step What you do Why this step

1 Get Installed Applications having Installed Applications:Name contains Chrome from all machines with Operating System contains Windows Column filter keeps the grid to Chrome rows; with keeps it to Windows endpoints

2 Notice the grid is counting — versions are aggregated Useful for seeing the version spread, useless for contacting users

3 Add Computer Name to the get clause and re-ask Converts to a non-counting question, one row per endpoint, now merge-eligible

  • 4 Click Merge , add Last Logged In User Enrichment applies to all rows automatically
  • 5 Click Merge again, add Open Ports or another context sensor if needed Merges stack; the grid keeps widening

6 Select up to 100 rows and Deploy Action , or export the grid Chapter 4 covers deployment; chapter 6 covers export

Notice what happened at step 3: the decision to make the question non-counting was driven by what you needed to do next , not by the question itself. That is the practical judgement the Refining Questions domain is testing.

6. Common mistakes

Mistake What actually happens

Selecting rows first, expecting merge to respect the selection Merge applies to all results regardless of what you selected

Trying to merge a counting question The question is not eligible; add a per-endpoint sensor

Adding a from filter to the merge question The from clause is set automatically from the grid; your filter has no place to go

Assuming a colleague's saved question will appear It appears only if it is in a content set you can read and has the available to merge flag

Merging when you meant to narrow You end up with a wider grid and the same endpoint count; drill down instead

Loading diagram... Merge decision path