Sisense BI ElastiCube Management & Data Connectivity 3

Question 1

Where can Sisense administrators access detailed logs for ElastiCube build operations?

Accepted Answer

Through the ElastiCube Server management console and server-side log files

Answer

In the Sisense dashboard audit trail under Settings

Answer

In the user activity log on the Sisense web portal

Answer

Only via third-party log aggregation tools

Question 2

What does the 'Restore' operation accomplish for an ElastiCube in Sisense?

Accepted Answer

Restores the ElastiCube's data and schema to a previously saved build snapshot

Answer

Resets all dashboard configurations to factory defaults

Answer

Reinstalls the ElastiCube Server software to fix corruption

Answer

Resets all user permissions and access levels to defaults

Question 3

Which Sisense REST API endpoint group is used to manage ElastiCube operations such as triggering builds programmatically?

Accepted Answer

/api/v1/elasticubes

Answer

/api/v1/dashboards

Answer

/api/v1/builds

Answer

/api/v1/datacubes

Question 4

What permission level is required for a Sisense user to publish an ElastiCube to the server?

Accepted Answer

Data Admin

Answer

Viewer

Answer

Designer

Answer

Dashboard Owner

Question 5

What feature in ElastiCube Manager allows users to validate and inspect data within the model before publishing it to production?

Accepted Answer

Query Preview in ElastiCube Manager

Answer

ElastiCube Staging Mode

Answer

Dashboard Sandbox Preview

Answer

Data Quality Checker

Question 6

When an ElastiCube build fails partway through execution, what is Sisense's default behavior?

Accepted Answer

The previous successful build remains active while the failed build is discarded

Answer

The ElastiCube is immediately taken offline until manually repaired

Answer

All data is deleted and must be fully rebuilt from scratch manually

Answer

The partial build is published with a warning flag for incomplete data

Question 7

What is the primary benefit of using ElastiCube's Accumulative (Changes Only) build setting for large production datasets?

Accepted Answer

It reduces build time and server resource consumption by only loading incremental data changes

Answer

It skips all data validation checks, speeding up the build

Answer

It prevents users from accessing the ElastiCube during builds for data consistency

Answer

It enforces data quality rules exclusively on newly added records