NetSuite NETSUITE-ADMINISTRATOR Online Practice Questions and Exam Preparation

NetSuite NETSUITE-ADMINISTRATOR Online Questions & Answers

• Question 11:

  How can an Administrator view deleted Saved Searches?

  A. Access the Audit Trail tab on a specific Saved Search.
  B. Access the Saved Searches List and select Inactive.
  C. Create and run an Analytics Audit Trail search.
  D. Create and run a Saved Searches Saved Search.
  C. Create and run an Analytics Audit Trail search.

  ---

  Explanation/Reference:

  To view deleted Saved Searches, an Administrator can "Create and run an Analytics Audit Trail search" in NetSuite. The Analytics Audit Trail is a powerful tool that tracks changes made to analytics objects, including saved searches. By creating and executing an audit trail search with the appropriate criteria, administrators can identify which saved searches have been deleted, who deleted them, and when the deletion occurred. This functionality is critical for maintaining oversight of changes within the system and can be essential for troubleshooting or compliance purposes. The Audit Trail ensures transparency and accountability in the management of saved searches and other analytics objects.References: NetSuite Help Center, Analytics Audit Trail documentation.

• Question 12:

  What impact does changing the Item name have on Sales Orders from Closed Periods?

  A. Displays the name at time of the original transaction.
  B. The transaction System Notes display the Item name change.
  C. Displays the current Item name.
  D. Displays the current and the original Item name
  A. Displays the name at time of the original transaction.

  ---

  Explanation/Reference:

  Changing the name of an item in NetSuite does not retroactively alter the item's name in transactions from closed periods. The system is designed to maintain the integrity of historical data, including transaction records, by displaying the item name as it was at the time of the original transaction. This feature ensures that financial and sales reports remain consistent and accurate over time, regardless of subsequent changes to item names. It preserves the audit trail and facilitates accurate historical analysis and compliance with accounting principles.References: NetSuite's core principles of data integrity and consistency as outlined in the platform's documentation and training materials, with a specific focus on how changes to master data, such as item names, are handled in relation to historical transactions.

• Question 13:

  Which statement is true about the behavior of bundles in Release Preview?

  A. Bundles can be installed from one Release Preview account to another Release Preview account.
  B. Bundles can be installed from a Release Preview account to a Production account
  C. Bundles can be copied to the repository from Release Preview.
  D. Bundles can be installed from a Release Preview account to a Sandbox or Development account.
  A. Bundles can be installed from one Release Preview account to another Release Preview account.

  ---

  Explanation/Reference:

  In the context of NetSuite's Release Preview environment, bundles, which are collections of customizations that can be easily installed or transferred between NetSuite accounts, can be installed from one Release Preview account to another. This functionality allows users to test how customizations will perform with the new release's features before they are deployed in the production environment. Installing bundles from a Release Preview account directly to a Production account (Option B) is not the standard practice as it bypasses the testing phase. Similarly, copying bundles to the repository from Release Preview (Option C) and installing them from a Release Preview account to a Sandbox or Development account (Option D) are not behaviors specifically associated with the intended use of the Release Preview environment, which is primarily for testing upcoming release features under conditions that closely mimic the production environment. References: NetSuite Help Documentation on Release Preview Environment.

• Question 14:

  A user wants to create a custom field on a Task record that lists all customers with the Taxable checkbox selected. If the field Type = List/Record and List/Record = Customer, what additional settings are required for the custom field?

  A. Sourcing and Filtering > Filter Using = Taxable Is Checked = Yes
  B. Sourcing and Filtering > Source List = Company Sourcing and Filtering > Source From = Taxable
  C. Sourcing and Filtering > Source List = Company Sourcing and Filtering > Source Filter By = Taxable
  D. Validation and Defaulting > Formula = {taxable}
  A. Sourcing and Filtering > Filter Using = Taxable Is Checked = Yes

  ---

  Explanation/Reference:

  To create a custom field on a Task record that lists all customers with the Taxable checkbox selected, the appropriate settings are found under "Sourcing and Filtering > Filter Using = Taxable Is Checked = Yes." This setting effectively filters and displays only those customers for whom the 'Taxable' field is marked as 'Yes' in the custom field's drop- down list or lookup. This method leverages NetSuite's powerful sourcing and filtering capabilities to restrict the list of records based on specific criteria, ensuring that users can easily select from a refined list of taxable customers directly from the Task record.References: NetSuite Help Center, "Creating Custom Fields"

• Question 15:

  An Administrator would like to generate a list of employees with login access to their NetSuite account. What search type will display these users?

  A. Analytics Audit Trail
  B. Employee
  C. System Notes
  D. Login Audit Trail
  B. Employee

  ---

  Explanation/Reference:

  To generate a list of employees with login access to a NetSuite account, the "Employee" search type is the most direct and effective. By performing a search using this type, administrators can filter and display only those employees who have

  been granted access rights to log into the system. This can include criteria such as "Is Active" and specific roles or permissions assigned to employees, allowing for a comprehensive overview of all users with system access. This approach

  simplifies the process of auditing and managing user access by focusing directly on the employee records.References:

  NetSuite SuiteAnswers and Help Center documentation on creating and managing saved searches, with a focus on utilizing the Employee search type to monitor and report on system access.

• Question 16:

  Which preferences prevent creating duplicate records once an online form is submitted? (Choose 2)

  A. On the Select Fields tab, select the Search column field.
  B. On the Setup Workflow tab, select Use Duplicate Detection Criteria.
  C. On the Setup Workflow tab, select Allow Update on Contact Record.
  D. On the Select Fields tab, select Mandatory.
  A. On the Select Fields tab, select the Search column field.
  B. On the Setup Workflow tab, select Use Duplicate Detection Criteria.

  ---

  Explanation/Reference:

  To prevent the creation of duplicate records from online form submissions in NetSuite, two key preferences can be utilized:

  On the Select Fields tab, select the Search column field: By enabling the Search column for specific fields on the Select Fields tab, the system can perform searches based on the data entered in those fields to check for existing records that

  match the criteria. This helps prevent duplicates by comparing incoming form data against existing records.

  On the Setup Workflow tab, select Use Duplicate Detection Criteria: This setting activates duplicate detection rules that you have defined for your system or specific record type. When this preference is set, the system uses these predefined

  criteria to identify and prevent duplication during the form submission process.

  Both of these settings are crucial for maintaining data integrity and preventing the accumulation of redundant records in the database.

  References:

  NetSuite Online Form Configuration Guide.

  Best practices in managing duplicate records in NetSuite.

• Question 17:

  If a bundle author changes a bundle already installed on a target account, who can update the installed bundle? (Choose 2)

  A. Account Administrator
  B. User with SuiteApp Marketplace permission
  C. User with access to Managed Bundles permission
  D. User with SuiteApp Distribution permission
  A. Account Administrator
  C. User with access to Managed Bundles permission

  ---

  Explanation/Reference:

  Updating an installed bundle that has been changed by the bundle author requires specific permissions within a NetSuite account. The Account Administrator inherently has the necessary rights across the account to manage and update any installed bundles. Additionally, any user granted the "Manage Bundles" permission can also update installed bundles. This permission allows users to access the bundle management functionality, where they can check for updates to installed bundles and apply those updates as released by the bundle author. It's important for these users to monitor changes to bundles, as updates may include critical fixes or enhancements necessary for the optimal performance and security of the NetSuite account. References: NetSuite Help Center: Managing and Updating Installed Bundles NetSuite SuiteAnswers: Permissions for Bundle Management

• Question 18:

  Which installed bundle cannot be updated by target account users?

  A. Managed bundle
  B. Customization bundle
  C. Configuration bundle
  D. Non-managed bundle
  A. Managed bundle

  ---

  Explanation/Reference:

  Managed bundles in NetSuite are bundles provided typically by third-party vendors or created in one account and distributed to others, where the original creator retains control over bundle updates and maintenance. Users in the target

  account (where the bundle is installed) cannot update a managed bundle; only the bundle provider can push updates. This ensures consistency, reliability, and integrity of the bundle's functionality across different accounts, preventing

  unauthorized modifications.References:

  NetSuite Help Center and SuiteAnswers articles on bundle management, specifically focusing on the distinctions between managed and unmanaged (custom) bundles.

• Question 19:

  How do you prevent a terminated employee from logging into NetSuite?

  A. Clear the Give Access checkbox.
  B. Delete the Employee record.
  C. Inactivate the Employee record.
  D. Reset the employee's password.
  A. Clear the Give Access checkbox.

  ---

  Explanation/Reference:

  To prevent a terminated employee from logging into NetSuite, the recommended action is to clear the "Give Access" checkbox in the employee's record. This action effectively revokes the employee's access to the system without deleting or inactivating their record, which can be important for maintaining historical data and compliance with record-keeping requirements. Deleting the employee record is not advisable as it removes all historical data associated with that employee, and inactivating the record may not necessarily block login attempts. Resetting the employee's password can temporarily prevent access but doesn't address the underlying need to revoke access permissions systematically. Clearing the "Give Access" checkbox is a direct and reversible way to manage access rights for terminated employees.References: NetSuite's documentation on managing user access and employee records.

• Question 20:

  Which statement is true about Global Permissions?

  A. Role-based permissions override Global Permissions.
  B. Global Permissions let Administrators bypass assigning roles to employees.
  C. Global Permissions override role-based permissions.
  D. Global Permissions apply to the Administrator.
  C. Global Permissions override role-based permissions.

  ---

  Explanation/Reference:

  Global Permissions in NetSuite are designed to augment or extend the access rights provided by role-based permissions, essentially overriding them for specific areas of the system. These permissions are typically used to grant additional, cross- functional access to users without needing to assign them a new or different role. For instance, if a user has a role with restricted financial data access but requires view access to all financial reports, a Global Permission related to financial report viewing can be granted. This approach provides a flexible way to manage exceptions to role-based access controls without compromising the principle of least privilege or necessitating the creation of overly broad roles.References: NetSuite Help Documentation, "Managing Access and Permissions"