pbPassingBI
/
quicksight/exams/quicksight-exam-practice

QuickSight practice exam

Twelve questions across SPICE, datasets, calculations and security.

  1. Consumers see stale figures after you edited the analysis. Why?

    1. SPICE is full
    2. The dashboard was not republished
    3. RLS is blocking
    4. Wrong filter scope

    Answer: The dashboard was not republished — Dashboards are published snapshots; analysis edits require republishing.

  2. Which requires Enterprise edition?

    1. SPICE
    2. Row-level security
    3. Calculated fields
    4. Pivot tables

    Answer: Row-level security — RLS, VPC connectivity and directory integration are Enterprise features.

  3. SPICE refresh fails across several datasets. Check first:

    1. Visual configuration
    2. SPICE capacity in the admin console
    3. Dashboard sharing
    4. Parameter defaults

    Answer: SPICE capacity in the admin console — Exhausted capacity, often from abandoned datasets, is the usual cause.

  4. Which computes revenue per customer regardless of visual grouping?

    1. sum(revenue)
    2. sumOver(sum({revenue}), [{customer_id}], PRE_AGG)
    3. percentOfTotal(sum(revenue))
    4. avg(revenue)

    Answer: sumOver(sum({revenue}), [{customer_id}], PRE_AGG) — Level-aware aggregation pins the calculation to a chosen level of detail.

  5. A blank value in an RLS restriction column grants:

    1. No access
    2. Access to all values of that field
    3. Access to one value
    4. An error

    Answer: Access to all values of that field — Blank is the mechanism for granting full visibility, and a common accidental exposure.

  6. A user absent from the rules dataset sees:

    1. Everything
    2. No data
    3. Only totals
    4. A permission error

    Answer: No data — Default-deny: every entitled user must appear explicitly.

  7. In a multi-tenant anonymous embed, isolation is enforced by:

    1. URL parameters
    2. Session tags matched by the rules dataset
    3. The iframe sandbox
    4. Dashboard permissions

    Answer: Session tags matched by the rules dataset — Anonymous users have no identity, so session tags carry the entitlement into RLS.

  8. Map visuals are unavailable for a city field. Cause?

    1. Direct query mode
    2. No geographic role assigned
    3. SPICE full
    4. Standard edition

    Answer: No geographic role assigned — Geospatial visuals require a geographic role on the field.

  9. Which is true of direct query?

    1. It consumes SPICE capacity
    2. Every visual interaction queries the source
    3. It is always faster
    4. It supports incremental refresh

    Answer: Every visual interaction queries the source — Direct query passes each request to the source, so performance and cost track the source.

  10. Where is complex join logic best maintained?

    1. Dataset custom SQL
    2. A view in the warehouse
    3. An analysis calculated field
    4. A filter

    Answer: A view in the warehouse — Warehouse views are version-controlled, reusable and easier to debug.

  11. In runningSum, the partition argument controls:

    1. Sort order
    2. Where the running total resets
    3. The aggregation
    4. The filter scope

    Answer: Where the running total resets — Partition sets reset boundaries; sort order is a separate argument.

  12. Dashboard consumers need which permission on the underlying dataset?

    1. Owner
    2. None — dashboard access carries the data
    3. Viewer
    4. Author

    Answer: None — dashboard access carries the data — Dashboards carry their dataset access; only authors need dataset permissions.