NetSuite Platform Foundations and Navigation
NetSuite is a single-instance, multi-tenant SaaS platform built on a shared data model, and most navigation questions test whether you understand that structure. A record (a transaction, entity, or item) is a database object with a type and an internal ID. Roles control which records and centers a user sees. The Centers menu (the tab strip at the top) is role-driven: a user with the Sales role sees a Sales center; an administrator sees Setup, Customization, and more. Within a center, tabs group related pages, and the global search bar can search records by name or number.
The classic trap is confusing role, subsidiary, and department as if they were the same kind of restriction. Roles govern feature and permission access; subsidiaries partition data and transactions for one-world accounting; departments are reporting dimensions, not security boundaries (unless a role is restricted to them). Another trap: the difference between a record type and a record instance. "Customer" is a record type; "Acme Corp" is an instance with an internal ID. Questions often ask which identifier is stable when names change-the answer is the internal ID.
Know the global search behavior: it searches across record types the role can see, and results are grouped by type. Also know that recent records and reminders are user-level conveniences, not permission controls. A common exam scenario asks a user who cannot see a page despite having the right role-usually the answer is a missing permission or a subsidiary restriction, not a browser problem.
Rule of thumb: when a navigation question is ambiguous, ask "is this controlled by role/permission, by subsidiary, or by user preference?" Most wrong answers swap these categories.