JAMF100 Policies and Scripts 2 — Questions and Answers
Question 1: Which Jamf Pro policy trigger fires when a user logs into a managed Mac?
- Startup
- Recurring Check-In
- Login (Correct answer)
- Network State Change
Correct answer: Login
The Login trigger fires a policy when a user logs into a managed Mac, allowing user-specific configurations or scripts to execute at login time.
Question 2: What is the purpose of 'Parameter Labels' when configuring a script in Jamf Pro?
- To name the script for reporting purposes
- To provide descriptive labels for parameter fields shown in the policy configuration UI (Correct answer)
- To encrypt script parameters before transmission
- To define the script's execution order within a policy
Correct answer: To provide descriptive labels for parameter fields shown in the policy configuration UI
Parameter Labels provide human-readable descriptions for parameters 4–11, making it clear to admins what values to enter when adding the script to a policy.
Question 3: When would you use the 'Ongoing' execution frequency for a Jamf Pro policy?
- When a policy should run only once ever across the fleet
- When a policy should run every time its trigger fires with no repetition limit (Correct answer)
- When a policy should run once per calendar week
- When a policy should run at a specific time of day
Correct answer: When a policy should run every time its trigger fires with no repetition limit
'Ongoing' causes the policy to run every single time its trigger fires, with no cap on repetitions, making it suitable for tasks that must always execute on check-in or login.
Question 4: What is the 'Custom Event' trigger used for in Jamf Pro policies?
- Triggering policies based on calendar events
- Allowing policies to be triggered by a custom string via the jamf binary on the client (Correct answer)
- Triggering policies when a specific app launches
- Running policies based on Siri Shortcuts
Correct answer: Allowing policies to be triggered by a custom string via the jamf binary on the client
Custom Event triggers allow policies to be called by running 'jamf policy -event <customEventName>' on a managed Mac, enabling script-to-policy chaining and on-demand invocation.
Question 5: In Jamf Pro, what does the 'Files and Processes' payload in a policy allow an administrator to do?
- Install files from a distribution point package
- Search for files, run Unix commands, and kill specific running processes (Correct answer)
- Manage file system permissions only
- Create new local user accounts
Correct answer: Search for files, run Unix commands, and kill specific running processes
The Files and Processes payload allows administrators to search for files, execute Unix commands, open applications, and terminate specific processes on managed computers.
Question 6: Which Jamf Pro policy payload is used to display a message or notification to end users during policy execution?
- Scripts payload
- Files and Processes payload
- User Interaction payload (Correct answer)
- Software Update payload
Correct answer: User Interaction payload
The User Interaction payload allows policies to display messages to users, issue restart or shutdown warnings, and solicit input from users during policy execution.
Question 7: What is the purpose of the 'Maintenance' payload in a Jamf Pro policy?
- To schedule hardware maintenance windows in the Jamf Pro calendar
- To perform macOS maintenance tasks like flushing DNS cache and rebuilding the Spotlight index (Correct answer)
- To update Jamf Pro server components remotely
- To manage Time Machine backup schedules
Correct answer: To perform macOS maintenance tasks like flushing DNS cache and rebuilding the Spotlight index
The Maintenance payload performs common macOS upkeep tasks such as verifying the startup disk, flushing DNS cache, repairing disk permissions, and rebuilding the Spotlight index.
Which Jamf Pro policy trigger fires when a user logs into a managed Mac?