Table Builderis a feature in ServiceNow that allows administrators tomanage table structures, relationships, and configurations.
The"Additional Actions"menu includes options such ascreating database indexes, which improve query performance.
Explanation of Incorrect Options:
Duplicate the selected form view (A)# Form views are configured separately and not via Table Builder.
Add a new module (B)# Modules are added in the Application Navigator,not Table Builder.
Schedule a job (D)# Jobs are created in theSystem Scheduler, not Table Builder.
Reference:
ServiceNow Docs - Table Builder

In ServiceNow,groupsare stored in theGroup [sys_user_group]table. Groups are used to organize users with similar responsibilities, permissions, or functional roles.
Name(name) - The unique name of the group.
Manager(manager) - The user responsible for managing the group.
Roles(roles) - The roles assigned to the group, which are inherited by all group members.
Parent Group(parent) - If applicable, this establishes group hierarchy.
Assigning access roles to multiple users at once.
Routing tasks or approvals (e.g., Incident assignments to an IT Support group).
Managing security and permissions in ServiceNow.
A). Group [user group]- Incorrect. This is not a valid ServiceNow table.
B). Group [sys_user]- Incorrect. This is theUsertable, not the Group table.
D). Group [sys_user_group_profile]- Incorrect. This table does not exist in ServiceNow.
ServiceNow Docs: User Administration - sys_user_group Table
ServiceNow CSA Study Guide - Managing Users and Groups
Key Fields in thesys_user_groupTable:Common Use Cases for Groups:Explanation of Incorrect Options:
References from Certified System Administrator (CSA) Documentation:

In ServiceNow,Business Rulesare server-side scripts that executeat specific timesrelative to database operations. The"When" settingdetermineswhenthe Business Rule runs in relation to a record action (Insert, Update, Delete, Query).
Why is Option A Correct?Before
Executesbeforea record is saved to the database.
Used tovalidate data, modify values, or prevent an action(e.g., stopping an invalid update).
After
Executesaftera record is inserted, updated, or deleted.
Commonly used fortriggering notificationsor creating related records.
Async (Asynchronous)
Runsaftera database operation but executes inthe background.
Ideal forlong-running or performance-heavy tasks(e.g., integrating with external systems).
Display
Executesbefore a form loads, allowing modifications to fieldsbefore they are displayedto the user.
Typically used forpre-filling form fieldsbased on user roles or conditions.
Why Are the Other Options Incorrect?B. Prior to, Synchronous, on Update
"Prior to"is not a valid Business Rule execution timing.
"Synchronous"is a general term but isnot a specific execution timing optionin Business Rules.
"on Update"is a database operation,not an execution timing.
C). Insert, Update, Delete, Query
These aredatabase operationsthat trigger Business Rules,not execution timings.
Execution timing determineswhen(before, after, etc.), while these determinewhat triggers it.
D). Before, Synchronous, Scheduled Job, View
"Synchronous"is not a Business Rule timing option.
"Scheduled Job"refers toScheduled Jobs(not Business Rules).
"View"is a UI-related concept,not a Business Rule execution timing.
ServiceNow Business Rules - How They Work
ServiceNow Best Practices - Business Rule Execution Timing
ServiceNow Developer Documentation - Before, After, Async, and Display Business Rules References to Official Certified System Administrator (CSA) Documentation: