https://docs.servicenow.com/bundle/paris-servicenow-platform/page/administer/flow-designer/concept/spokes.
html
A spoke is a scoped application containing Flow Designer content dedicated to a particular application or record type. Flow Designer provides a set of core actions to automate Now Platform processes. You can add application-specific core actions by activating the associated spoke.
Reference: https://community.servicenow.com/community? id=community_blog & sys_id=7b3af354db93ab80afc902d5ca9619bc

To modify the structure of inherited fields, consider the following approaches:
Field Visibility: Use client scripts or UI policies to hide the inherited fields on forms where they are not needed. This approach maintains data integrity while tailoring the user interface to specific requirements.
Form Layout Configuration: Adjust the form layout to remove inherited fields from specific views, ensuring they are not displayed to users in contexts where they are irrelevant.
These methods allow customization of the user experience without altering the underlying table schema or violating the inheritance principles established in the data model.
Explanation:
In ServiceNow, tables can extend other tables, inheriting all fields and functionalities from the parent table. These inherited fields are integral to the structure and behavior of the child table.
A . No, inherited fields cannot be deleted from a child table: This is correct. Inherited fields are part of the child table's schema due to its extension of the parent table. Removing these fields would disrupt the inherent structure and relationships defined by the table hierarchy.
B . Yes, but only if they are text fields: This is incorrect. The data type of the field does not permit the deletion of inherited fields.
C . Yes, select the red X in the left-most column in the table definition: This is incorrect. Inherited fields do not have a delete (red X) option in the table definition, as they are not directly created on the child table.

One of the uses of the ServiceNow REST API Explorer is to create sample code for sending REST requests to ServiceNow. The REST API Explorer is a tool that allows you to discover and test the ServiceNow REST APIs. You can select an API endpoint, set the HTTP method, parameters, headers, and body, and then execute the request. The REST API Explorer will show you the response status, headers, and body, as well as generate sample code for various languages and frameworks, such as cURL, Java, JavaScript, Node.js, Python, Ruby, and more. References: [Use the REST API Explorer - Product Documentation: Tokyo - ServiceNow], [Introduction to Scripted REST APIs - ServiceNow Developers]

Created UI policy on incident form, action set's cmdb_ci field as mandatory and script as not. result, field was not mandatory.
A UI Policy's Actions execute before the UI Policy's Scripts. Actions are predefined operations that can be applied to fields or sections, such as making them mandatory, read-only, visible, or setting a default value. Scripts are custom JavaScript code that can be used to perform more complex logic or validations. Actions are executed first, and then Scripts are executed if the UI Policy conditions are met. Reference: [ServiceNow Docs - UI policy actions], [ServiceNow Docs - UI policy scripts]