Explanation:

https://learn.microsoft.com/en-us/azure/active-directory/roles/groups-concept#how-are-role-assignable- groups-protected
"Group nesting isn't supported. A group can't be added as a member of a role-assignable group." For the second question:
https://learn.microsoft.com/en-us/azure/active-directory/fundamentals/how-to-manage-groups#add-or-remove- a-group-from-another-group
"We currently don't support:
Adding Microsoft 365 groups to Security groups or other Microsoft 365 groups.
"
For the third question, although it appears truncated in the screenshot (ending with "for...") there is a reference about Microsoft 365 groups support for roles assignment here:
https://learn.microsoft.com/en-us/azure/active-directory/roles/groups-concept#how-role-assignments-to- groups-work
"To assign a role to a group, you must create a new security or Microsoft 365 group with the isAssignableToRole property set to true. "

Explanation:
Litwareinc.com users can be assigned to package1. = No
After 365 days, fabrikam.com users will be removed from Group1. = Yes
After 395 days, fabrikam.com users will be removed from the contoso.com tenant = No Litwareinc.com users cannot be assigned to package1 because they are not a connected organization in the contoso.com tenant. Only users from connected organizations can request access packages that are configured for external users1 Fabrikam.com users will be removed from Group1 after 365 days because the access package has an expiration policy of 365 days for external users. This means that the access assignments for external users will end after 365 days, unless they are renewed or extended2 Fabrikam.com users will not be removed from the contoso.com tenant after 395 days because the external user lifecycle settings have a deletion policy of 30 days after blocking. This means that external users will be blocked from signing in after 365 days of inactivity, and then deleted after another 30 days. Therefore, the total time before deletion is 395 days of inactivity, not 395 days from the date of assignment3

Change the Service administrator for an Azure subscription
Sign in to Account Center as the Account administrator.
Select a subscription.
On the right side, select Edit subscription details.
Scenario: Designate a new user named Admin1 as the service administrator of the Azure subscription.
References: https://docs.microsoft.com/en-us/azure/billing/billing-add-change-azure-subscription- administrator

Before creating a network interface, you must have an existing virtual network in the same location and subscription you create a network interface in.
If you try to create a NIC on a location that does not have any Vnets you will get the following error: "The currently selected subscription and location lack any existing virtual networks. Create a virtual network first." Reference:
https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-network-interface

https://docs.microsoft.com/en-us/azure/role-based-access-control/rbac-and-directory-admin-roles#:~:
text=The%20User%20Access%20Administrator%20role%20enables%20the%20user%20to%20grant,Azure%
20subscriptions%20and%20management%20groups.