During the upgrade from ArcGIS Enterprise 10.6.1 to 10.9.1, user type licensing is enforced. If the new license file includes more than one compatible user type (e.g., Creator and GIS Professional), existing members without a specified user type may be assigned temporary user types like "Standard (Temporary)" or
"Lite (Temporary)." These temporary assignments prevent users from logging in until valid user types are manually assigned.
This issue is not related to internet access (Option B) or the need to restart services (Option C).
Reference Source:ArcGIS Enterprise documentation on user type licensing during upgrades

For map services that are infrequently updated and contain numerous detailed features with complex symbology, configuring the service to use cached tiles is the most effective way to improve drawing performance. Cached map services pre-render map images at various scales and store them, allowing for faster display to users. This approach is particularly beneficial when the data does not change frequently, as it reduces the server's processing load during user interactions.
Eliminating scale-dependent rendering (Option B) may lead to performance degradation, as it could result in rendering all features at all scales, increasing the amount of data processed and displayed unnecessarily.
Switching to dedicated instances (Option C) can improve performance in some scenarios, but it also increases resource usage on the server. Given that the service is infrequently updated and the primary concern is drawing performance, caching is the more efficient and scalable solution.
Reference Source: ArcGIS Enterprise documentation on optimizing map services for performance.

When replacing SSL certificates in ArcGIS Enterprise components,ArcGIS Server and Portal for ArcGIS require the root and intermediate (issuing) certificates to be explicitly importedinto their trust stores.
Unlike the ArcGIS Data Store, which can often rely on the system-level trust store, ArcGIS Server and Portal maintain their owncertificate trust management.
From the official ArcGIS Enterprise documentation:
"When using certificates issued by an internal or external CA, it is essential to also import the corresponding root and intermediate certificates into the Portal for ArcGIS and ArcGIS Server trust stores to ensure the certificate chain is validated properly."
* OptionBis incorrect. Domain CA certificatesare supported and recommendedover self-signed certificates for internal deployments.
* OptionCrefers to an acceptable format butdoes not address the issue, which is about importing the chain of trust.
* OptionDis incorrect; PKCS#12 (.pfx) certificates are supported but must be paired with the correct chain files.
Reference:ArcGIS Enterprise -Managing CA certificates in Portal and ArcGIS Server environments

A shared update group allows group members to edit each other's items without needing to transfer ownership. This is ideal for collaborative editing and shared responsibility for applications, maps, or dashboards.
From Esri documentation:
"Shared update groups allow multiple members to update items shared with the group, even if they do not own the items."
* Option B doesn't exist as a group type in ArcGIS Enterprise.
* Option C allows viewing, but not editing others' content.
* Option D applies to distributed collaboration, not shared editing.
Reference:ArcGIS Enterprise - Group Settings for Collaborative Management

When users perform standard analysis tasks in the portal Map Viewer, the hosting server executes geoprocessing operations that are computationally intensive. These operations require significant CPU resources. Monitoring CPU utilization helps ensure that the server can handle the increased load without performance degradation.
While disk activity and network utilization are important, they are less directly impacted by standard analysis tasks compared to CPU usage. Therefore, CPU utilization is the primary resource to monitor in this scenario.
Reference Source: ArcGIS Enterprise documentation on system performance monitoring.