ArcGIS Online Administration Associate common mistakes
ArcGIS Online Administration Associate · Understand the traps and how to avoid them.
Treating ArcGIS Online roles as a simple ladder, so the candidate assumes an Administrator can do everything a Publisher can and answers permission questions by picking the highest-sounding role.
The default roles (Viewer, User, Publisher, Administrator) are not strictly cumulative in every respect, and candidates who memorise a ranking rather than the actual privileges assigned to each role misjudge questions about who can share content, create groups, or manage members.
What to do instead
Study the privilege categories attached to each default role (content, sharing, groups, organisation, and so on) and practise mapping a described task to the minimum role that grants it. For any scenario question, ask which specific privilege is required before choosing a role.
Confusing the organisation's default sharing level with the sharing level of a specific item, and answering that setting the organisation default to 'private' makes existing public items private.
The organisation sharing setting governs the default for newly created items, not a retroactive change to items already shared. Candidates read 'default' as 'enforced' and pick the answer that sounds most secure.
What to do instead
Learn the distinction between default sharing level, the ability to allow sharing outside the organisation, and per-item sharing. Remember that restricting public sharing affects future sharing actions and may require administrators to review existing public items separately.
Assuming deleting a user account removes their content, or that content must be manually reassigned before deletion, without checking the actual behaviour of the delete operation and the available content-transfer options.
Member management questions often hinge on what happens to items, groups, and group ownership when an account is removed. Candidates generalise from other platforms where deletion cascades, or from a half-remembered warning dialog.
What to do instead
Review the documented member-removal workflow, including how to reassign content and group ownership before deleting an account, and what happens to items owned by a deleted member. Practise the sequence: transfer content, transfer or delete groups, then remove the member.
Mixing up group types and membership models, for example assuming any group can be made view-only or that an organisation group automatically includes all members.
Group behaviour depends on several independent settings (who can join, who can contribute, whether membership is by invitation or request, and whether the group is visible to the organisation or public). Candidates collapse these into one 'group type' concept.
What to do instead
Build a table of group settings and what each controls: join policy, contribution access, visibility, and whether the group is used for sharing updates. Test each setting in a trial organisation so the effect on sharing and membership is concrete.
Answering licensing questions by counting named users only, ignoring the difference between user types and add-on capabilities such as spatial analysis, geocoding, or premium content.
ArcGIS Online licensing distinguishes user types from add-on licences and credit-consuming capabilities. Candidates who have only seen a single-seat setup assume every member has the same capabilities.
What to do instead
Learn how user types map to capability bundles and how add-on licences are assigned to individual members. For scenario questions, identify the capability required first, then the licence that provides it, then the member assignment step.
Treating credits as a general storage quota and guessing which operations consume them, such as assuming publishing a hosted feature layer is free or that viewing a map consumes credits.
Credit consumption is tied to specific premium operations and storage, not to everyday viewing. Candidates extrapolate from consumer cloud pricing or from a single experience with a large upload.
What to do instead
Memorise the main credit-consuming categories: hosted feature storage, spatial analysis tools, geocoding and routing, and premium content. Distinguish these from free operations such as map viewing and standard sharing. Review the credit usage reports available to administrators.
Configuring security settings in isolation, for example enabling multi-factor authentication or enterprise logins without accounting for how it interacts with existing member accounts and the organisation's identity provider.
Security configuration questions combine several controls (MFA enforcement, SAML or OpenID Connect enterprise logins, allowed origins, and IP restrictions). Candidates focus on the single control named in the question and ignore the prerequisites and side effects.
What to do instead
Study each security control together with its prerequisites and its effect on members. Know the difference between organisation-specific logins and enterprise logins, what happens to built-in accounts when enterprise logins are enabled, and how to test configuration with a small pilot group before enforcing it.
Describing status monitoring and health checks as a reactive task, so the candidate cannot say what administrators should configure to detect service issues or how to review system status.
Candidates prepare for content and membership questions and skim the operational monitoring material, leaving them unable to distinguish organisation-level status information from item-level errors.
What to do instead
Review the administrative tools for monitoring the organisation: status dashboards, organisation status pages, and the logs and reports available to administrators. Practise reading a described symptom and deciding whether it is an item configuration issue, a member permission issue, or a service-wide status event.
Confusing the organisation's URL and custom domain configuration with item URLs, and answering that changing the organisation short name or custom domain automatically updates all shared links.
The organisation short name appears in item URLs and in the organisation URL, and custom domains add another layer. Candidates assume renaming is cosmetic and do not consider link breakage or the constraints on changing these identifiers.
What to do instead
Learn which identifiers can be changed and what depends on them, including the organisation short name, the custom domain, and the URLs of items and groups. For each, note the impact on existing links and the recommended order of operations when a rebrand is required.
Answering backup, restore, and content-governance questions by assuming ArcGIS Online provides full automatic versioning of hosted layers and item recovery, rather than knowing what administrators must configure or export themselves.
Candidates transfer expectations from desktop GIS or from database systems where versioning is automatic. The exam tests practical governance: what is protected by default, what requires configuration, and what must be exported.
What to do instead
Study the available options for protecting content: item deletion protection, overwrite controls, scheduled exports, and the role of groups and ownership in recovery. Be able to state, for a given scenario, whether recovery is possible and what an administrator should have set up in advance.