https://docs.servicenow.com/bundle/tokyo-servicenow-platform/page/administer/notification/task/t_CreateANotification.html
https://developer.servicenow.com/dev.do#!/learn/learning-plans/quebec/new_to_servicenow/app_store_learnv2_automatingapps_quebec_when_to_send The Weight field in an Email Notification determines which notification is sent when multiple notifications are triggered for the same record and recipients. Only the notification with the highest weight is sent. A weight value of zero means the notification is always sent when the notification's When to send criteria is met. A weight value of -1 means that no email should be sent3. References: Email Notification Weight

In ServiceNow, Application Access settings at the table level allow developers to control which operations from other application scopes can be performed on their application's tables. The specific database operations that can be controlled are:
Can read: Allows other application scopes to read records from the table.
Can create: Allows other application scopes to create new records in the table.
Can update: Allows other application scopes to modify existing records in the table.
Can delete: Allows other application scopes to delete records from the table.
Options A (Update) and B (Create) are correct because "Can update" and "Can create" are among the operations that can be controlled through Application Access settings.
Options C (Execute) and D (Query) are incorrect. While "Execute" pertains to the ability to run scripts or script includes, it is not a database operation controlled by Application Access but rather by script access settings. "Query" corresponds to reading data, which is governed by the "Can read" setting.
For more detailed information, refer to the official ServiceNow documentation on Application Access settings:
SERVICENOW.COM

In ServiceNow, the Event Registry is a table that contains a record for every event recognized by the system.
It allows ServiceNow to respond when these events are generated. By registering events, the system can automate activities such as triggering notifications or executing script actions when specific events occur.
Therefore, the correct answer is A.
The other options are not accurate descriptions of the Event Registry:
* B. The Event Log which lists all Events that have been generated: This describes the Event Log, not the Event Registry.
* C. A Workflow which is launched every time an Event is generated; used to debug Events: This is not how the Event Registry functions.
* D. The method used in server-side scripts to generate Events and pass parameters: This describes the gs.
eventQueue() method, not the Event Registry.
For more detailed information, refer to the official ServiceNow documentation on the Event Registry.