https://docs.servicenow.com/bundle/rome-platform-administration/page/administer/reference-pages/task/schedule-report.html Generate and distribute scheduled reports via email.
A report is a graphical representation of data from one or more tables in ServiceNow. The following are true for reports in ServiceNow:
Can be a graphical representation of data. This is true because reports can use various chart types, such as pie, bar, line, or gauge, to visualize data in a meaningful way.
Can be run on demand by authorized users. This is true because reports can be accessed from the Reports menu or the Report Navigator and run by users who have the appropriate roles and permissions to view the data.
Can be scheduled to be run and distributed by email. This is true because reports can be configured to run at a specific time and frequency and send the results to one or more email recipients.
The following are not true for reports in ServiceNow:
Any user can see any report shared with them. This is false because users can only see reports that are shared with them if they also have access to the data source of the report. For example, a user who does not have the itil role cannot see a report based on the incident table, even if the report is shared with them.
All users can generate reports on any table. This is false because users can only generate reports on tables that they have access to and that are enabled for reporting. For example, a user who does not have the admin role cannot generate reports on the sys_user table, which is the table for user records. References: Reports, Report Security

Access Controls are rules that define who can access what data and how they can access it. When configuring an Access Control, you can specify the table, operation, and role for the rule. You can also add a condition or a script to further refine the rule. If you do not add a condition or a script, the rule will apply to all records and fields on the table.
The statements A, B, and C are true for Access Controls that have no condition or script. For example:
table.* will grant access to every field in a record. This means that the user can view and edit all the fields on the record, regardless of their role or any other criteria.
table.None will grant access to every record on the table. This means that the user can view and edit all the records on the table, regardless of their role or any other criteria.
table.field will grant access to a specific field in a record. This means that the user can view and edit only that field on the record, regardless of their role or any other criteria.
The statement D is not true for Access Controls that have no condition or script. table.id will not grant access to a specific record on the table. This is because the id is not a field name, but a unique identifier for the record. To grant access to a specific record on the table, you need to add a condition or a script that matches the id of the record.
References:
[Access Control rules]
[Create an Access Control rule]

A benefit of creating an Application Properties page for each application you develop is that Application Properties allow a developer or admin to make changes to an application's behavior without modifying application artifacts. Application Properties are system properties that store configuration information for a specific application. They can be used to control various aspects of the application, such as feature flags, default values, thresholds, or URLs. By creating an Application Properties page, you can group and display all the properties related to your application in one place and make them easy to access and update. This way, you can avoid hard-coding static data in your application code and make your application more flexible and maintainable. Reference: Working with System Properties, Organizing your ServiceNow System Properties

https://docs.servicenow.com/bundle/rome-application-development/page/build/applications/concept/c_ApplicationScope.html The correct statement regarding Application Scope is that applications downloaded from 3rd party ServiceNow application developers cannot have naming conflicts. Application Scope is a feature that identifies and isolates applications and their related artifacts from other applications. Each scoped application has a unique namespace identifier that consists of a prefix and a scope name. This prevents cross-application name collisions and ensures that only authorized scripts can access or modify data in a scoped application. References: [Product Documentation | ServiceNow], [How To Create a Scoped App in ServiceNow - YouTube]

"Restricted caller access [sys_restricted_caller_access] records track cross-scope applications or scripts that request access to an application, application resource, or event in the Now Platform." <<== this is the third sentence down in the following link: https://docs.servicenow.com/bundle/tokyo-application-development/page/build/applications/concept/restricted-caller-access-privilege.html