Unpivoting is the specific data transformation operation used in TIBCO Spotfire to restructure a data table from a short/wide format to a tall/skinny format. This process converts columns into rows, creating a new category column and a new value column from the original column headers and their cell values. This transformation is essential for preparing data for certain types of visualizations and analyses where data needs to be aggregated or compared across categories that were originally represented as separate columns.

A. Calculation: This involves creating new columns using expressions based on existing data, not restructuring the table's fundamental layout from wide to tall.

C. Renaming Columns: This is a metadata operation that changes the name of a column but does not alter the structure or dimensions of the data table.

D. Pivot: This is the inverse operation of unpivot. It transforms data from a tall/skinny format to a short/wide format by converting row values into new columns.

E. Normalization: This is a broader database design concept aimed at reducing data redundancy and improving data integrity, not the specific name of the wide-to-tall transformation operation in Spotfire.

1. TIBCO Spotfire® Analyst User's Guide

Version 12.0 LTS

"Unpivoting data" section. The documentation states

"Unpivoting is a way to transform data from a wide

or cross-table

format to a tall

or stacked

format. When you unpivot

the data in a selection of columns is transformed into two new columns: a category column and a value column." This directly defines the process described in the question.

2. TIBCO Spotfire® Analyst User's Guide

Version 12.0 LTS

"Details on Unpivot" section. This section provides a visual example and further details: "The columns that you choose to unpivot are removed from the data table

and their names and values are added in the two new columns." This confirms the structural change from wide (multiple original columns) to tall (two new columns).

When configuring IronPython scripts in TIBCO Spotfire, they can be parameterized to interact dynamically with the analysis file. The script parameter configuration allows for several types of inputs. These include direct references to objects within the analysis such as a specific Page, Data Table, or Visualization. Additionally, scripts can accept fundamental Data types like strings, integers, or booleans. These are often passed as 'Value' parameters, which can be fixed literals, derived from expressions, or linked to document properties, enabling the script to receive and process specific data values.

C. Action Control: An Action Control is a user interface element (e.g., a button) that triggers the execution of a script; it is the initiator of the action, not an input parameter passed to the script.

---

1. TIBCO Spotfire® Analyst User's Guide (Version 12.0.x)

Chapter: "Action controls"

Section: "Details on Script Parameters".

This section explicitly lists the available parameter types that can be passed to a script. The list includes: Value

DataTable

DataColumn

DataMarking

Filter

Page

and Visualization.

This directly supports options A ("Page or data table")

B ("Visualization")

and D ("Data types

" which corresponds to the Value parameter type). It also confirms that "Action Control" (Option C) is not a valid parameter type.

2. TIBCO Spotfire® API Reference

Namespace: Spotfire.Dxp.Application.Scripting.

The documentation for the ScriptParameter class and its usage within the API shows how parameters representing application objects (Page

DataTable

Visualization) and literal values (string

int

etc.) are defined and passed to a script manager for execution. This corroborates the types of inputs a script is designed to receive.

The mod-manifest.json file is the core configuration file for a TIBCO Spotfire visualization mod. It contains essential metadata that Spotfire uses to register and render the new visualization. The manifest explicitly lists all the files that comprise the mod (e.g., JavaScript, CSS, HTML) within a files array. It also defines the data mapping structure, including the properties of each data axis, such as its name, mode (categorical or continuous), and its intended placement within the visualization, under an axes array. These definitions are crucial for Spotfire to understand the mod's requirements and integrate it into the analysis environment.

B. CORS configuration data: Cross-Origin Resource Sharing (CORS) is a security policy handled at the server or web application level, not within an individual visualization mod's manifest.

C. Visualizations affected by the mod: A mod defines a new, self-contained visualization type; it does not list or modify other existing visualizations within the Spotfire environment.

1. TIBCO Spotfire® Mods Developer Documentation

"The mod-manifest.json file". This official documentation details the structure of the manifest. It explicitly describes the files property as an "Array of strings with paths to the files that constitute the mod" and the axes property as an "Array of objects

where each object defines an axis." This directly supports answers A and D.

2. TIBCO Spotfire® Mods Developer Documentation

"Add an axis". This section provides a detailed example of defining an axis within the mod-manifest.json

including properties like name

mode

and placement

confirming the details mentioned in option D.

The most direct and primary method for editing the content of a text area in TIBCO Spotfire is by using the controls located on the visualization's title bar. Clicking the "Edit text area" button (often represented by a pencil icon) on the title bar immediately places the text area into edit mode. This allows for the direct manipulation of text, the insertion of images, links, property controls, and action controls. This context-sensitive approach is the standard and most efficient user interaction for modifying text area content.

A. The properties dialog is used to configure the settings and appearance of the text area, such as its title and data, not to edit its primary content.

B. The Visualizations menu is used to add new visualizations to the analysis page, not to edit the content of existing ones.

C. While an edit option exists under the main Edit menu, the button on the title bar is the more direct, common, and context-specific method.

1. TIBCO Spotfire® Analyst User's Guide

Version 12.0 LTS

Chapter: "Visualizations"

Section: "Text Area"

Subsection: "Editing a Text Area".

This section explicitly states: "On the text area title bar

click the Edit text area button

Edit. The text area is now in edit mode and the toolbar is displayed." This directly supports option D as the correct answer.

2. TIBCO Spotfire® Analyst User's Guide

Version 12.0 LTS

Chapter: "Visualizations"

Section: "Text Area"

Subsection: "Text Area Properties".

This documentation details the settings available in the Properties dialog

such as General (Title)

Data

and Fonts. It makes no mention of editing the core HTML content

confirming that option A is incorrect.

3. TIBCO Spotfire® Analyst User's Guide

Version 12.0 LTS

Chapter: "Creating an Analysis"

Section: "Adding visualizations".

This section describes the function of the Visualizations menu and flyout

confirming its purpose is to add new visualizations

which invalidates option B.

A parallel coordinate plot represents each row in a data table as a single polyline that intersects a series of parallel vertical axes. Each axis corresponds to a different column (variable) from the data table. The statement that a row is mapped as a bar is incorrect; this describes the fundamental element of a bar chart, not a parallel coordinate plot. The core visual element for a data row in this plot is a line, not a bar.

A. This is incorrect because each vertical axis in a parallel coordinate plot represents a different variable, and these variables almost always have different units and ranges, thus requiring separate scales.

C. This is incorrect because, like all visualizations in TIBCO Spotfire, the parallel coordinate plot is interactive and the data it displays can be limited by one or more active filtering schemes.

D. This is incorrect because TIBCO Spotfire normalizes the scale for each axis (typically to a 0-100 range) to allow for visual comparison of patterns across variables with different original scales.

---

1. TIBCO Spotfire® Analyst User's Guide (Version 12.0 LTS)

"What is a Parallel Coordinate Plot?".

Reference for Correct Answer (B): The documentation states

"Each row in the data table is represented by a line." This directly contradicts the claim that a row is mapped as a bar.

Reference for Incorrect Option (A & D): The same section explains

"Each of the columns selected on the Y-axis is given its own Y-axis... The values in each column are normalized so that the minimum value for each column is 0 and the maximum value is 100." This confirms that each column has its own axis (and thus its own underlying scale) and that the values are normalized for display.

Reference for Incorrect Option (C): In the section "Limiting What is Shown in Visualizations"

the guide details how filtering schemes and other methods apply to all visualizations. Specifically

the "Data" page in the visualization properties allows for limiting data by filtering.

The TIBCO Spotfire library employs a hierarchical permission model for folders. The Browse permission is the most basic level, allowing a user to see the folder's existence in the library tree. The Access permission allows the user to open that folder and view its contents (e.g., analyses, data files). According to official TIBCO documentation, the Access permission explicitly requires the Browse permission. This combination (Browse + Access) constitutes the standard "read-only" access level, which is a fundamental and correct permission setting for consumers of content within the library.

A. Access + Full Control: This is incorrect because the Full Control permission is the highest level and implicitly includes all lower-level permissions, including Access, making the combination redundant.

B. Browse + Modify: This is incorrect because the Modify permission (to save or delete items) requires the Access permission as a prerequisite, which is missing from this combination.

D. Access + Modify: This is incorrect because the Access permission requires the Browse permission as a prerequisite, which is missing. A user cannot access a folder they cannot see.

1. TIBCO Spotfire® Server and Environment - Installation and Administration Manual

Version 12.0 LTS.

Reference: Chapter 6: Administration Manager

Section: "Folder permissions".

Details: The documentation explicitly outlines the permission hierarchy and dependencies:

"Access folder: Grants permission to open the folder and see its contents. This permission requires the Browse folder permission."

"Modify folder contents: Grants permission to save

rename

and delete items in the folder. This permission requires the Access folder permission."

This confirms that Browse + Access is a valid and required combination for viewing content

and that options B and D are missing necessary prerequisite permissions. It also confirms the redundancy in option A

as Full Control requires Modify

which requires Access.

Information Links are metadata objects that represent predefined database queries. They are stored centrally in the TIBCO Spotfire Library, which is a core component managed by the TIBCO Spotfire Server. This server-side storage architecture is essential for governance, allowing administrators to control data access through permissions. It also facilitates the sharing and reuse of these data access definitions across multiple users and analysis files, ensuring consistency and simplifying data loading for end-users.

A. The Spotfire Library is a central, server-based repository, not a component that exists on a local machine.

C. Information Links are metadata objects within the server's Library database, not discrete files saved on a user's computer.

D. They are complex, shareable data access definitions, not simple configuration settings stored on a local machine.

1. TIBCO Spotfire® Server and Environment Installation and Configuration

Version 14.0.0 LTS

Chapter: "The TIBCO Spotfire environment"

Section: "The TIBCO Spotfire Library". This section states: "The TIBCO Spotfire Library is the central repository in the TIBCO Spotfire environment... The library can also contain other items

such as data sources

data connections

and Information Links."

2. TIBCO Spotfire® Analyst User's Guide

Version 14.0.0 LTS

Chapter: "Loading Data"

Section: "What are Information Links?". This official guide specifies: "Information links are stored in the library

and can be used by anyone with the proper permissions." This confirms their location within the server-managed Library.

An information link is a predefined database query stored in the TIBCO Spotfire library. The entire process of creating an information link begins with establishing a connection to the underlying database. This is accomplished by setting up a data source in the Information Designer tool. Without a configured data source, Spotfire has no access to the database schema, and therefore, it is impossible to define any of the subsequent elements required for an information link, such as columns, joins, or filters. The data source is the foundational prerequisite upon which all other information model elements are built.

A. Create Columns: Creating column elements is a necessary step, but it can only be performed after a data source has been set up to expose the available tables and columns.

B. Create Join: Creating a join is an optional step, only required if the information link needs to retrieve data from two or more related tables.

D. Create Multiple Columns: This is a specific instance of creating columns and is subject to the same prerequisite of having a data source configured first.

E. Create Filter: Creating a filter is an optional step used to apply conditions (a WHERE clause) to the query; it is not a mandatory prerequisite.

1. TIBCO Spotfire® Information Designer User's Guide

Version 12.0

Chapter: "Workflow in Information Designer"

Page 10. The documentation explicitly outlines the creation process: "The first thing you must do is to set up one or more data sources. Once a data source is in place

you can start creating the column

join and filter elements that will be the building blocks of your information links." This confirms that setting up a data source is the initial

required step.

2. TIBCO Spotfire® Analyst User's Guide

Version 12.0

Chapter: "Adding Data Connections"

Section: "What is an Information Link?". This section explains that information links are based on data sources that have been set up in Information Designer. It states

"An information link is a database query

specified in the Information Designer... It is built from building blocks such as columns and filters

which have been created from an underlying data source." This reinforces that the data source is the origin for all other components.

In the TIBCO Spotfire IronPython API, the Document object represents the currently open analysis file. The Pages property of this Document object provides access to the collection of all pages (tabs) contained within that analysis. This property returns a PageCollection object, which can be iterated through to access, modify, or manipulate individual pages programmatically. For example, a script can use Document.Pages to add a new page, navigate to an existing page, or retrieve a specific page by its title or index.

A. Document.Pages refers to the internal pages of the Spotfire analysis file (.dxp), not external web pages where it might be published.

C. The system pagefile is an operating system concept for virtual memory management and is entirely unrelated to the Spotfire application's API or object model.

D. This option is incorrect; Document.Pages is a collection of Page objects within a single document, not a collection of documents.

---

1. TIBCO Spotfire® Analyst API Reference

Spotfire.Dxp.Application.Document Class.

Section/Property: Document.Pages Property

Content: The documentation explicitly states that this property "Gets the collection of pages in this document." It returns an object of type PageCollection. This directly supports the correct answer.

2. TIBCO Spotfire® Analyst API Reference

Spotfire.Dxp.Application.PageCollection Class.

Section: Class Summary

Content: The summary for the PageCollection class describes it as a collection that "Contains the pages of a document." This confirms that Document.Pages is indeed a collection of the pages within the current document.

The Graphical Table is a unique visualization in TIBCO Spotfire specifically designed to embed interactive elements called Action Controls within its cells. These controls can be rendered as buttons, links, or images. When a user clicks on an Action Control, it executes a pre-configured action, such as running an IronPython script, applying bookmarks, or navigating to another page or website. This provides a direct and explicit method for triggering actions from a click within the visualization itself, making it distinct from other visualization types.

A. Table visualization: Does not natively support embedding clickable Action Controls to trigger scripts; its interactivity is primarily limited to marking and sorting data.

B. Cross table: Lacks the functionality to embed Action Controls for triggering actions. It is designed for data aggregation and summarization, not direct user actions.

C. Line chart: Interactivity is based on marking data points, which can indirectly trigger scripts upon a change in marking, but it does not support direct, clickable Action Controls.

1. TIBCO Spotfire® Analyst User's Guide (Version 12.0 LTS): In the section "What is a Graphical Table?"

the documentation states: "In a graphical table

you can include different types of values such as calculated values

sparklines

images

or action controls in the columns." This explicitly confirms that Action Controls are a component of Graphical Tables.

2. TIBCO Spotfire® Analyst User's Guide (Version 12.0 LTS): The section "Adding an Action Control" specifies the locations where these controls can be used: "You can add action controls to text areas and graphical tables." This highlights the specific and limited placement of Action Controls

reinforcing why the Graphical Table is the correct answer among the given visualization types.

3. TIBCO Spotfire® Analyst User's Guide (Version 12.0 LTS): Under "Details on Graphical Table Properties - Columns"

the guide details how to add a new column and change its type. One of the available "Renderer" types for a column is "Link"

which can be configured with an "Action control script". This provides the specific mechanism for implementing the feature.