The Twitter component is a standard Lightning component that can be added to mobile view Lightning pages using the Lightning App Builder. It displays a contact's Twitter profile and recent tweets

LEFT(Account.Zip_Code_c, 5) is the correct formula to display only the first five digits of Zip Code from the parent Account. LEFT function returns the specified number of characters from the left side of a text string. Account.Zip_Code_c is the custom text field that stores the Zip Code on Account object. 5 is the number of characters to return from the left side of the Zip Code. The other options are not valid formulas or functions.

For an app builder who needs to ensure all fields from the page layout are visible on a Lightning Record Page after using the Lightning Object Creator, the correct component to use is:
Record Detail (C). The Record Detail component automatically displays all fields that are included on the assigned page layout for the object. It is designed to reflect the layout configuration and is the simplest way to ensure all fields are presented as configured in the layout editor.
Highlights Panel (A) is used primarily to display key fields at the top of the record page, providing a summary view rather than full field visibility. Recommendations (B) is used for displaying prompts or suggestions and does not display record fields. Path (D) is useful for displaying stages in a process (like sales stages or service processes) and does not show field data directly.
Reference for setting up Lightning Record Pages and using components effectively:
Lightning Record Pages: https://help.salesforce.com/articleView?id=sf.lightning_page_components.htm&type=5

For reporting snapshots, the source report must be capable of grouping data, which is necessary for summarizing information at specific intervals. The acceptable formats for a source report in reporting snapshots are:
Summary format (B). This format groups rows of data by one or more criteria and can perform calculations such as sum, average, etc., on another column at each group level.
Matrix format (D). Similar to the summary format but arranges data in a grid format, allowing summarization by both rows and columns.
Tabular (A) and joined (C) formats are not suitable for reporting snapshots. Tabular reports do not include grouped or summarized data, and joined reports involve combining multiple report types, which are not compatible with how reporting snapshots need to structure data.
Reference for more information on reporting snapshots and report formats:
Reporting Snapshots: https://help.salesforce.com/articleView?id=reports_snapshots.htm&type=5 Report Formats: https://help.salesforce.com/articleView?id=reports_understanding_formats.htm&type=5

Criteria-based sharing rules are the best tool to use for automatically sharing records based on specific criteria, such as the opportunity type being "Service Agreement." This rule can share opportunities with all users in a particular role, such as the Service Manager role, when the criteria are met, thereby adhering to the private sharing model while still providing necessary access.
A: Owner-based sharing rules focus on the record owner's role or group, not the record type.
C: Apex sharing is used for more complex scenarios not easily handled by declarative sharing settings.