PSA-SYSADMIN Psa Sysadmin Practice Questions

This correctly uses the standard PSA hierarchy. 'Region' is the top-level entity for APAC. 'Practices' are used for the sub-units (Australia, Singapore) under the Region, allowing for separate management and reporting. 'Groups' further segment resources within each Practice. Creating distinct Work Calendars and assigning them at the appropriate level (e.g., Practice) correctly handles the different holiday and work-week requirements.

While enabling Skills and Certifications enhances the functionality of resource searching and planning, it is not a mandatory prerequisite for using the basic features of the Resource and Project Planners. The planners can function without this setting, focusing on availability and role-based planning.

Permission Sets can be used to grant additional permissions but also to control visibility. If a user is assigned a Permission Set that explicitly sets the 'Project Management' Workspace tab to 'Tab Hidden', it will override the 'Default On' or 'Default Off' setting from their profile. This is a common cause of visibility issues for specific users who may have unique permission assignments.

Many Certinia Lightning components, including the Project Header, are driven by Field Sets. This allows administrators to declaratively control which fields are displayed without modifying the component's code. It is common for a package upgrade to overwrite or reset a standard Field Set. The administrator must navigate to the Project object's Field Sets and add the custom field back to the specific Field Set used by the Project Header component.

Certinia PSA includes a standard, schedulable Apex class specifically for this purpose, often named something like 'AppLogBatchPurge'. Administrators can schedule this job to run on a recurring basis (e.g., daily, weekly) and specify the retention period (e.g., 180 days). This is the supported, out-of-the-box method for automating App Log maintenance.

Certinia PSA provides a specific control on the Project object, 'Enable Change Requests', to govern the visibility of change request functionality. If this checkbox is not selected for a particular project, the associated actions will be hidden, even if the user has the correct permissions. This allows for granular control over which projects can have formal change requests.

A successful upgrade requires careful preparation. Reviewing release notes is crucial for understanding the impact. Comprehensive testing in a sandbox validates that existing processes and customizations will work correctly. A rollback plan is a critical safety net in case of unforeseen issues. Deactivating automation in production is risky and not a standard best practice; testing should identify any conflicts beforehand.

As data volume grows, a fixed batch size can lead to longer processing times or hitting governor limits. The most direct, admin-controlled first step is to review the configuration for the scheduled job, which often includes a batch size setting. Reducing the batch size means each transaction processes fewer records, which can prevent timeouts and improve overall job stability, even if the total runtime remains long. It's the most logical and immediate action before considering more complex solutions.

The 'Allow Self-Staffing' option allows resources who meet the request's criteria (e.g., skills, region) to propose themselves for the assignment. However, it does not bypass the standard approval process. A resource manager or project manager must still review and approve the proposed assignment.

PSA Configuration Groups are the central place to manage shared, profile-based configurations. An administrator can define Gantt settings, including color-coding based on field values (like 'High Risk') and critical path visibility, within a Configuration Group. This configuration is then applied to all users assigned to that group, ensuring a consistent and standardized user experience.