Explanation
https://blog.udemy.com/database-normal-forms/

The ORDER BY clause in Oracle SQL is used to sort the result set of a query by one or more columns, and it comes with its own set of rules and behaviors:
D . Column aliases can be used In the ORDER BY clause: True, column aliases that are specified in the SELECT clause can be used in the ORDER BY clause to refer to the columns to sort the results by.
E . In a character sort, the values are case-sensitive: Oracle sorts results in case-sensitive order by default when using the ORDER BY clause with character columns, unless otherwise specified by the NLS_SORT parameter.
Reference:
Oracle Database SQL Language Reference 12c, which provides details on sorting query results using ORDER BY.

The queries that will return all the rows from the COLORS table are those that ensure every record from COLORS is selected, regardless of whether there's a matching record in the BRICKS table:
* Option A:
* SELECT * FROM bricks b RIGHT JOIN colors c ON b.color_rgb_hex_value = c.rgb_hex_value;
* A right join will return all the rows from the right table (COLORS), with the matching rows from the left table (BRICKS). If there is no match, NULL will be returned for columns from BRICKS.
* Option B:
* SELECT * FROM colors c LEFT JOIN bricks b USING (rgb_hex_value);
* A left join will return all the rows from the left table (COLORS), with the matching rows from the right table (BRICKS). If there is no match, NULL will be returned for columns from BRICKS. The USING clause indicates a join condition where columns with the same names are compared for equality.
Options C, D, and E will not return all the rows from the COLORS table:
* Option C: The full join will return all rows from both tables, but it is not restricted to only the rows from COLORS.
* Option D: An inner join will return only the matching rows between both tables, not all rows from COLORS.
* Option E: This is a left join, which would typically return all rows from COLORS, but the WHERE clause restricts the result set to only those rows from COLORS that have a matching BRICK_ID in BRICKS which is greater than 0, potentially excluding rows from COLORS.