A client wants to perform incremental webgisdr backups daily and full backups weekly. They store all data in the relational ArcGIS Data Store, with no tile or map caches.
Which action is required to enable incremental backups?
To perform incremental backups using the webgisdr tool, point-in-time recovery must be enabled on the relational data store. This creates transaction logs needed for differential backups and aligns with best practices for enterprise-level backup strategies.
From Esri documentation:
''Incremental backups can only be used with a relational data store when point-in-time recovery is enabled. This enables transaction log capture needed for delta backups.''
Option A is unrelated to backup functionality.
Option C is not required unless performance tuning is needed.
ArcGIS Enterprise -- Enabling Point-in-Time Recovery in ArcGIS Data Store for Incremental Backups
=====================
A GIS administrator is responsible for maintaining the stability of a large internal ArcGIS Enterprise deployment. After the Domain CA certificate is replaced with a new one and the new PKCS#12 format PFX file is imported into all Portal for ArcGIS, ArcGIS Server, and ArcGIS Data Store deployments, the following issues are identified:
When connecting directly to the Portal for ArcGIS administration endpoint via port 7443, the new certificate is not recognized and is considered invalid
When connecting directly to the ArcGIS Server administration endpoint via port 6443, the new certificate is not recognized and is considered invalid
When connecting to the ArcGIS Data Store endpoint via port 2443, the new certificate is recognized and considered valid
What is causing this issue?
When replacing SSL certificates in ArcGIS Enterprise components, ArcGIS Server and Portal for ArcGIS require the root and intermediate (issuing) certificates to be explicitly imported into their trust stores. Unlike the ArcGIS Data Store, which can often rely on the system-level trust store, ArcGIS Server and Portal maintain their own certificate 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.''
Option B is incorrect. Domain CA certificates are supported and recommended over self-signed certificates for internal deployments.
Option C refers to an acceptable format but does not address the issue, which is about importing the chain of trust.
Option D is incorrect; PKCS#12 (.pfx) certificates are supported but must be paired with the correct chain files.
ArcGIS Enterprise -- Managing CA certificates in Portal and ArcGIS Server environments
=====================
An ArcGIS administrator executes a script to silently upgrade all components of ArcGIS Enterprise version 10.6.1 to version 10.9.1. The upgrade completes without logging any errors.
When the administrator logs in, the following message appears: "Members in your organization were assigned the Standard (Temporary) or Lite (Temporary) user types. No users can log in to the Portal."
What is causing these issues?
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
An organization wants to use the standard feature analysis tools available in ArcGIS Enterprise to create hosted feature layers for planning and design.
Which data store is required for this work?
The standard feature analysis tools in ArcGIS Enterprise (e.g., buffer, overlay, aggregate points) require hosted feature layers, which depend on the relational data store (a component of ArcGIS Data Store). The relational data store is the default location for hosting feature layers.
From ArcGIS Enterprise documentation:
''To use the standard spatial analysis tools and create hosted feature layers, the ArcGIS Data Store (relational) must be configured and set as the default hosting location.''
Option A (spatiotemporal big data store) is used for real-time and big data feeds, not standard analysis.
Option C supports cached tiles, not feature layers.
ArcGIS Enterprise -- Configuring the Relational Data Store for Hosting Feature Layers
=====================
A GIS administrator publishes a feature service that references user-managed data. The administrator wants users to add new features. Users should not make changes to attributes of existing features or delete features.
Which feature service operations should be set?
To allow users to add new features without the ability to modify or delete existing ones, the feature service should have the 'Create' and 'Query' operations enabled. The 'Create' operation permits users to add new features, while the 'Query' operation allows them to view existing features. By not enabling the 'Update' and 'Delete' operations, users are restricted from making changes to or removing existing features. This configuration is ideal for workflows where data integrity is crucial, and only the addition of new data is permitted.
Enabling 'Update and sync' (Option A) would allow users to modify existing features and synchronize changes, which is not desired in this scenario. 'Extract and create' (Option C) is not a standard combination of operations for controlling editing permissions in feature services.
Reference Source: ArcGIS Server documentation on editor permissions for feature services
Currently there are no comments in this discussion, be the first to comment!
Nada
20 days agoPearline
27 days agoAliza
1 month agoIsreal
1 month agoRoxane
2 months agoGennie
2 months agoRueben
2 months agoReita
2 months agoIvette
3 months agoLashandra
3 months agoLang
3 months agoAshlee
3 months agoCassie
4 months agoSkye
4 months agoWhitney
4 months agoTijuana
4 months agoYvonne
5 months agoErnie
5 months agoSelma
5 months agoScarlet
5 months agoDenise
6 months agoXochitl
6 months agoElouise
6 months agoGlendora
6 months agoShaquana
7 months agoLang
7 months agoClaudia
7 months agoGlory
7 months agoLizbeth
7 months agoMabelle
8 months agoIrma
8 months agoIlene
8 months ago