Pair your devices with a code and playback position follows you: pause on this device, hit resume on the other. Position is saved to the site every minute and on pause.
Open this panel on your other device and enter the same code.
16 questions. Four options each, one correct answer, no partial credit. Answers and explanations below.
1. Which of these is a valid CLI invocation?
aws quick list-dashboardsaws quicksight list-dashboardsaws quick-suite list-dashboardsaws quicksuite list-dashboards2. How many AWS documentation trees currently serve Quick Sight user-guide content?
3. Your production data sits in a private VPC. The account is Standard edition. What happens?
4. Which pair of quotas differ between Standard and Enterprise?
CreateIngestion calls per 24h5. You promote someone to Admin. Which seat does that consume?
6. You hold AdministratorAccess in IAM. Can you purchase SPICE capacity?
7. The $250/month infrastructure fee is charged:
8. Your account uses IAM Identity Center. How are Quick roles assigned?
9. Signup fails with what looks like a permissions error, in an AWS Organizations landing zone. First place to look?
10. Encryption at rest for a new account is:
11. You open Quick from the AWS Management Console while the console is set to eu-west-1. Quick
opens in:
eu-west-1, matching the consoleus-east-1 always12. create-ingestion returns HTTP 404 ResourceNotFoundException. Most likely cause?
13. You need the same dashboard in two Regions. The mechanism is:
aws quicksight move-dashboard14. A dataset was built from an uploaded Excel file. What can't you do?
15. An author hides eight fields in every visual. The effect on SPICE capacity is:
16. You grant a Reader access to a dashboard. Can they open the underlying analysis?
1 — B. The rename touched the console and docs only. AWS states existing APIs, SDKs and
integrations continue to work without changes: the CLI is aws quicksight, the endpoint is
quicksight.<region>.amazonaws.com, IAM actions are quicksight:*. A, C and D don't exist.
2 — C. /quicksight/latest/user/, /quick/latest/userguide/ and /quicksuite/latest/userguide/
all render real content (verified 2026-08-09), and they cross-link mid-paragraph. They are not
redirects — which is why a bare doc link isn't a stable citation right now.
3 — C. "Add data from virtual private clouds (VPCs) and on-premises data sources" is listed under Enterprise edition capabilities. It's a capability gate, not a networking problem, so no NAT gateway or capacity purchase changes it.
4 — B. Standard is 25 M rows / 25 GB per dataset and 8 CreateIngestion calls per 24h;
Enterprise is 2 B rows / 2 TB and 32 calls. The quotas in A, C and D are the same for both editions.
5 — B. Admin is not a separate subscription: the docs state the Admin role is the same as the Quick Sight Author subscription, and Admin Pro the same as Quick Enterprise. So it consumes an author seat.
6 — C. The admin split table puts SPICE capacity under the Quick admin role and not under IAM permissions. IAM governs assets, security & permissions, VPC connections, KMS keys and account settings. This catches platform engineers constantly.
7 — B. It's a monthly floor that applies for Pro users or active Topics / Dashboard Q&A, not a per-user or per-dashboard charge. A three-person Pro trial can trigger the full amount.
8 — B. For IAM Identity Center or Active Directory accounts, groups are assigned to Quick roles. Only Quick + IAM user accounts manage roles at the individual user level.
9 — C. The signup docs warn explicitly: if the account is in an AWS Organization and you sign in as an IAM user, check you haven't inherited permissions that deny the required ones. It presents as a Quick bug but isn't one.
10 — B. "Your data is encrypted by default using AWS-managed keys. Admins can adjust settings for custom encryption in the admin portal after signing up." CMK is a post-signup, IAM-side change.
11 — C. The two Region selectors are independent, and Quick "opens in the last AWS Region that you selected in Amazon Quick" — not the console's Region.
12 — B. Region is the first hypothesis on a 404 with this service, well ahead of a deleted
dataset. An exhausted ingestion quota returns 409 LimitExceededException, and a direct-query dataset
returns DATA_SET_NOT_SPICE on the ingestion, not a 404.
13 — C. Assets are Region-scoped and there is no documented move operation. You build and promote via asset export/import through the API (Q7). Sharing doesn't relocate anything.
14 — C. "Connection information isn't saved for text or Microsoft Excel files" — there is no source to reconnect to. It can be in SPICE, carry RLS, and back a dashboard; it just can't be refreshed from source.
15 — B. Logical size is computed at dataset save. AWS states changes in an analysis have no effect on SPICE size — only changes saved in the dataset do.
16 — C. "Share the dashboard so other people can use the dashboard, even if they don't use the analysis that it's based on." Dashboard access and analysis access are separate grants.
| Score | Reading |
|---|---|
| 14–16 | Foundations solid. Go to Q1 (data sources) or straight to Q8. |
| 11–13 | Good. Re-read lessons 2 and 4 — editions and Regions are where the gaps sit. |
| 8–10 | Re-read the module and do the lab against a real account. |
| ≤ 7 | Start at lesson 1. The rest of the track assumes this vocabulary. |
The five that matter most in practice: 3 (VPC is Enterprise-gated), 6 (IAM can't buy SPICE), 11 (independent Region selectors), 12 (404 means Region), 15 (analysis changes don't shrink SPICE).