Free NETSUITE-ADMINISTRATOR Practice Test

For a custom field's value to be included in a Global Search, the "Store Value" preference must be enabled, and the "Global Search" checkbox on the custom field record must be checked. The "Global Search" option is only available for a specific subset of custom field types. According to official NetSuite documentation, both Email Address and Phone Number are field types that support the Global Search functionality. Other field types, such as Date and Time of Day, cannot be indexed for Global Search, even if their values are stored.

B. Date: The Date field type is not supported for inclusion in Global Search indexing, as specified by NetSuite's list of eligible custom field types.
C. Time of Day: The Time of Day field type is also not on the list of custom fields that can be made available for Global Search.

1. NetSuite Help Center, SuiteAnswers. (Answer ID: 10002203). Custom Fields Available for Global Search. This document explicitly lists the custom field types for which the Global Search option is available. The list includes "Email Address" and "Phone Number" but excludes "Date" and "Time of Day".

2. NetSuite Help Center. (Topic: Creating a Custom Field). In the section describing the "Display" subtab for custom fields, the documentation for the "Global Search" checkbox states: "Check this box to include the field in global searches. This option is available only for some types of custom fields." This confirms that eligibility is type-dependent.

To create a dependent dropdown field, the "Sourcing & Filtering" tab on the custom field record is used. The dependency is established by filtering the list of available options based on the value of another field on the same form. The Compare to Field column is used to select the controlling field on the current record. The system then compares the value in this field against a field from the source list (specified in the "Filter Using" column) to dynamically filter the dropdown options.

A. Compare Value To: This option is used to filter a list based on a static, predefined value, not on the dynamic value of another field on the form.
B. Value Is: This is a comparison operator used within filter criteria (e.g., in saved searches or workflows), not the column that selects the controlling field.
D. Field Is: This is a comparison operator, similar to "Value Is," used for comparing a field to another field, but "Compare to Field" is the specific column name for this configuration.

1. NetSuite Help Center: Sourcing Information for a Custom Field.

Section: Sourcing & Filtering Tab

Content: The documentation details the columns on the Sourcing & Filtering tab. It explicitly states: "In the Compare to Field column, select the field on the current record to which you want to compare the Filter Using field." This directly confirms its role in creating dependencies.

2. NetSuite Help Center: Creating a Dependent Dropdown List.

Section: Step-by-step instructions.

Content: This guide walks through the process, illustrating that to make a custom field's list dependent on another, you must set a filter where the "Compare to Field" column points to the independent (controlling) field on the form.

3. SuiteAnswers: Creating Dependent Dropdown Lists (Answer ID: 9921)

Section: Procedure

Content: This official support article provides a practical example. In step 11, it instructs the user to "In the Compare to Field column, select the field on the record that will be the parent dropdown." This confirms its function as the link for the dependency.

In a NetSuite OneWorld account, the "From Address for Emailed Forms" preference determines the sender's email address on transactions. To meet the requirement of using an email address from the appropriate subsidiary, the Subsidiary Return Email Address option must be selected. This setting instructs NetSuite to use the email address defined in the "Return Email Address" field on the subsidiary record associated with the specific transaction being emailed. This ensures that communications are correctly branded and replies are routed to the proper subsidiary.

B. Customer Subsidiary Email Address: This is not a valid preference name within NetSuite's Email Preferences settings. The correct terminology is "Subsidiary Return Email Address."
C. Company Return Email Address: This option uses a single, company-wide email address for all outgoing forms, which does not meet the multi-subsidiary requirement.
D. User Email Address: This option uses the email address of the employee sending the form, not the official email address of the subsidiary.

1. NetSuite Help Center, SuiteAnswers. (2023). Setting Email Preferences. Answer ID: 9921.

On the General subtab of the Email Preferences page, the "From Address for Emailed Forms" field is detailed. The documentation states: "In NetSuite OneWorld accounts, you can select Subsidiary Return Email Address to use the address in the Return Email Address field on the subsidiary record."

2. NetSuite Help Center, SuiteAnswers. (2023). Subsidiaries. Answer ID: 8991.

This document outlines the setup of subsidiary records, which includes the "Return Email Address" field. It states, "Enter the email address you want to appear in the From field of email messages sent from this subsidiary." This confirms the field's purpose in conjunction with the email preference.

NetSuite defines specific criteria for its password policies. The "Strong" password policy mandates a minimum length of 10 characters. In addition to length, this policy requires passwords to contain characters from three of the following four categories: uppercase letters, lowercase letters, numbers, and non-alphanumeric (special) characters. It also enforces rules against using account names or having more than two identical consecutive characters, ensuring a robust security standard for user authentication.

B. 6 characters is the minimum length required for the "Weak" password policy, not the "Strong" policy.
C. 12 characters is not a standard minimum length for any of NetSuite's default password policies (Weak, Medium, or Strong).
D. 8 characters is the minimum length required for the "Medium" password policy, not the "Strong" policy.

1. NetSuite Help Center. (2023). Password Requirements. SuiteAnswers, ID: 9911. Retrieved from the NetSuite application Help Center. (This article explicitly states: "Strong: Minimum of 10 characters.")

2. NetSuite Help Center. (2023). Setting Password Policies. SuiteAnswers, ID: 10083. Retrieved from the NetSuite application Help Center. (This document outlines the different policy levels and their respective requirements, confirming the character lengths for Weak, Medium, and Strong policies.)

NetSuite's official best practice is to assign the Administrator role to at least two users. This strategy ensures business continuity and prevents a single point of failure. If one administrator is unavailable, on leave, or departs from the company, a second administrator can still perform essential system management tasks, access critical functions, and manage user access. This approach mitigates the risk of being locked out of administrative functions, which could severely disrupt business operations. It balances security with operational necessity.

B. Only one user should be assigned the Administrator role. This creates a significant business risk and a single point of failure, which is contrary to recommended continuity practices.
C. Assign the Administrator role to the CFO. This violates the principle of least privilege; a user's job title does not automatically justify full system access.
D. Assign all managers the Administrator role. This is a severe security risk, violating the principle of least privilege by granting excessive permissions to multiple users.

1. NetSuite Help Center. (2023). Best Practices for the Administrator Role. SuiteAnswers, ID: 9911. Retrieved from the NetSuite Help Center.

The document explicitly states: "NetSuite recommends that you have at least two users with the Administrator role in your account. This practice ensures that you have a backup administrator if one administrator is unavailable or has left the company."

2. NetSuite Help Center. (2023). NetSuite Security Overview. SuiteAnswers, ID: 8971. Retrieved from the NetSuite Help Center.

This document discusses the principle of least privilege, stating, "Users should be granted only the permissions they need to perform their job duties." This principle directly contradicts options C and D.

The NetSuite Release Preview environment is designed to allow customers to test their existing business processes, customizations, and workflows against an upcoming release. Core data management functionalities, such as CSV Import, are available for this purpose. This enables users to test how new features and changes will affect data handling and migration processes. However, certain features are intentionally disabled in Release Preview to prevent accidental interaction with production data, manage system resources, or because they require special provisioning that is not supported in this temporary environment.

A. Outlook Integration: External integrations are typically limited or disabled in Release Preview to prevent unintended data synchronization with live, production third-party systems.
B. Payroll: Payroll is explicitly unavailable for testing in Release Preview. This is to prevent accidental processing of live payroll runs and because of the feature's complex, region-specific configurations.
D. Scheduled SuiteScript: By default, scheduled scripts do not run automatically in the Release Preview environment to conserve system resources. They must be triggered manually for testing purposes.

1. NetSuite Help Center, SuiteAnswers. (2024). Release Preview Guide. Answer ID: 9452. The section "Unavailable Features and Tasks in Your Release Preview Account" explicitly lists "Payroll" as unavailable. It also notes limitations on features that interact with external systems.

2. NetSuite Help Center, SuiteAnswers. (2024). FAQs: Release Preview. Answer ID: 10090. This document confirms that certain features are not available, stating, "You cannot test SuiteSuccess Payroll in your Release Preview account."

3. NetSuite Help Center, SuiteAnswers. (2024). Testing Scheduled Scripts in Release Preview. Answer ID: 45202. This article clarifies, "By default, scheduled scripts do not run automatically in Release Preview accounts... To test a scheduled script in a Release Preview account, you must manually trigger the script."

4. NetSuite Help Center, SuiteAnswers. (2024). CSV Import Assistant. Answer ID: 7332. This document describes the CSV Import Assistant as a core data import tool, the functionality of which is fundamental to testing data handling in any NetSuite environment, including Release Preview. It is not listed as a restricted feature.

The Release Preview Test Plan is a template provided by NetSuite specifically to guide customers in planning and executing their testing within the Release Preview account. This document helps users structure their testing process by outlining key business workflows, customizations, and integrations that need to be validated before the new release is live in their production account. It provides a framework for defining test cases, assigning testers, and tracking results, ensuring comprehensive coverage of critical business processes.

A. Release User Guide: This is not a standard NetSuite term for a release-specific document. General user guides exist but are not structured as a plan for testing.
B. Sneak Peeks: These are high-level, preliminary overviews of upcoming features. They are for informational purposes and lack the detail required to build a comprehensive test strategy.
C. Release Notes: These are detailed descriptions of all new features, enhancements, and fixes. They are a critical resource for what to test, but not the testing guide itself.

1. NetSuite Help Center, SuiteAnswers. (2023). Release Preview Test Plan Template. Answer ID: 10091. "The Release Preview Test Plan template provides a guide for planning your testing in the Release Preview account."

2. NetSuite Help Center, SuiteAnswers. (2023). Preparing for a NetSuite Release. Answer ID: 9947. This article outlines the release process, mentioning Sneak Peeks for high-level overviews and Release Notes for detailed information, distinguishing them from the Test Plan's purpose.

3. NetSuite Help Center, SuiteAnswers. (2023). NetSuite Release Notes. Answer ID: 9948. This document describes the content of Release Notes, confirming they are a detailed reference of changes, not a testing plan.

After enabling the Multi-Language feature, an administrator must explicitly add the desired languages to the NetSuite account. This is a mandatory setup step performed under Setup > Company > General Preferences on the Languages subtab. Adding a language here makes it available throughout the system for translation, including for bulk updates via the translation string import/export process. Without this configuration, there is no target language to which translations can be applied in bulk.

A. Changing a user's language preference only affects that specific user's interface display; it does not configure the account for bulk translation capabilities.
C. NetSuite's bulk translation process uses a specific file format for export and import; it does not require the creation of a custom CSV import template.
D. Setting a preferred language at the subsidiary level is a OneWorld feature that defaults transaction language; it is not the prerequisite for enabling bulk translation.

1. NetSuite Help Center, SuiteAnswers ID: 9920, "Setting Up Multiple Languages." This document states, "To set up multiple languages, you must first enable the Multi-Language feature at Setup > Company > Enable Features. Then, you must select the languages you want to make available in your NetSuite account at Setup > Company > General Preferences, on the Languages subtab."

2. NetSuite Help Center, SuiteAnswers ID: 10095, "Importing Translated Strings." This guide on the bulk update process notes, "Before you can import translated strings, you must have selected the languages you want to use in your account. For information, see Setting Language Preferences." This confirms that adding languages in General Preferences is a prerequisite.

3. NetSuite Help Center, SuiteAnswers ID: 43988, "Translating Custom Fields, Lists, and Records." In the section "Setting Up Languages for Translation," the first step listed is: "Go to Setup > Company > General Preferences. On the Languages subtab, in the Language list, select the languages you want to make available in your account."

The "Run Unrestricted" option on a saved search is designed to bypass role-based data restrictions (such as subsidiary, department, or class) when the search is executed. This allows a user with a restricted role to see a complete set of results that would otherwise be filtered. However, this capability is limited to viewing the data within the search results grid only. It does not grant the user any additional permissions, such as the ability to edit the records or to drill down to view the underlying record pages if those records fall outside their role's normal restrictions.

A. None: This is incorrect because the specific purpose of the "Run Unrestricted" feature is to provide the user with access to search results they would normally not see.
B. Edit access to resulting records: This is incorrect. The feature does not override the fundamental permissions of the user's role; it only bypasses data restrictions for viewing search results.
C. Edit access to the search results: This is incorrect. Similar to option B, the user's ability to edit is governed by their role's permissions, not by the "Run Unrestricted" search setting.
E. View access to the underlying detail from summary: This is incorrect. A key limitation of this feature is that it does not allow users to drill down and view the underlying record forms for results that are outside their role's restrictions. ---

1. NetSuite Help Center, SuiteAnswers: Running a Search with Unrestricted Access. Answer ID: 9911.

Quote: "When you check the Run Unrestricted box on a saved search page, the search returns all matching records, regardless of the restrictions that apply to the role of the user running the search... Note that this option only enables users to see the search results. It does not enable them to drill down to view the records for which they do not have permission." This directly supports that access is for viewing search results (D) and explicitly refutes the ability to drill down (E).

2. NetSuite Help Center, SuiteAnswers: Defining a Saved Search. Answer ID: 8991.

Section: Saved Search Page Fields.

Quote: Under the description for the "Run Unrestricted" checkbox, it states: "Check this box to have this search return all results, regardless of user role restrictions." This confirms the function is to show results that are normally restricted, making option D the correct outcome. It makes no mention of granting edit or drill-down capabilities, thereby invalidating options B, C, and E.

The "Core Administration Permissions" feature grants access to sensitive account setup pages. NetSuite classifies any role containing this permission as "highly privileged." As a mandatory security protocol to safeguard account integrity, NetSuite requires that any user assigned to a highly privileged role must use two-factor authentication (2FA) to log in. Therefore, a primary consideration for an administrator when assigning this permission is to ensure the role is configured to require 2FA, which is an enforced system behavior.

B. Editing employee records is governed by permissions on the Employee record type, not the broad Core Administration Permissions feature.
C. Assigning this powerful permission solely to edit searches violates the security principle of least privilege; specific search-related permissions should be used instead.
D. Using the standard Administrator role as a general workaround is a significant security risk and contradicts best practices, which favor creating custom roles with minimal necessary permissions.

1. NetSuite Help Center, SuiteAnswers. (2023). Two-Factor Authentication. Answer ID: 49211. This document explicitly lists "Core Administration Permissions" as a permission that makes a role highly privileged, for which 2FA is required. It states, "Users with these roles are required to set up and use 2FA to log in to NetSuite."

2. NetSuite Help Center, SuiteAnswers. (2023). Core Administration Permissions. Answer ID: 99397. This article defines the permission and notes, "Because this permission provides access to sensitive account setup information, you should assign it with caution." It reinforces the link between this permission and the 2FA mandate for highly privileged roles.

3. NetSuite Help Center, SuiteAnswers. (2023). Best Practices for Customizing or Creating Roles. Answer ID: 10092. This document advises administrators to "Follow the principle of least privilege" and to avoid using the Administrator role for daily tasks, directly contradicting the logic in options C and D.