Process Questions
Software development lifecycle (SDLC), code promotion with Update Sets, deployment processes, Now Create, and development environment strategy.
Newest question added: AI-assisted drafts, not yet individually reviewedHow questions are made
About Process
Process management for Platform Owners involves understanding SDLC methodologies, code promotion processes, and environment strategies. Knowing when to use Waterfall vs Agile and how to properly promote code through development, test, and production instances is essential.
Why This Matters for Your Exam
Process accounts for approximately 15.7% of the CPOA exam. Questions test your knowledge of deployment stages in Now Create, proper code promotion using Update Sets, and the benefits and drawbacks of different SDLC approaches.
Key Concepts to Master
Know the Now Create deployment process stages. Understand that Update Sets are the standard method for code promotion. Remember that development should NEVER be done directly in production. Know the flexibility benefits of Agile vs the rigidity of Waterfall.
Exam Tips
Focus on the sequence of deployment stages: development → testing/validation → production. Remember that multiple instances (dev/test/prod) enable safe testing before affecting end users.
Practice Questions
25 questions availableA team uses separate development, test, and production instances. A developer has just marked an update set Complete on the development instance. What is the next step in the documented update set workflow?
👆 Click an option above to select your answer
Show answer and explanation
Correct answer: C. Retrieve and commit it on the test instance, then test it
The documented workflow is: create the update set on development, make changes, and mark it complete. Then log in to the test instance, retrieve the completed update set, commit it there, and test thoroughly before moving it from test to production.
- Why A is wrong: A clone copies a source instance over the target, overwriting it, which would wipe the development work instead of promoting it.
- Why B is wrong: Update sets should follow a common path from dev to test and then from test to production, not skip testing.
- Why D is wrong: Backing out reverses the changes of a committed update set; it is not a promotion step.
A new catalog item was built and tested on the test instance and is being moved to production with an update set. What does the update set carry to production?
👆 Click an option above to select your answer
Show answer and explanation
Correct answer: A. Its definition, variables, and variable choices
Update sets capture configuration details but exclude task or process data. For a catalog item, they record the item definition, variables, and variable choices, but not submitted orders or catalog tasks.
- Why B is wrong: Catalog tasks are task data, which update sets do not record.
- Why C is wrong: Home pages and content pages are not added to update sets by default; they must be unloaded into the update set.
- Why D is wrong: Submitted orders are process data, which update sets exclude.
A company has only two instances: production and one non-production instance. How does the documented update set workflow handle development and testing in this setup?
👆 Click an option above to select your answer
Show answer and explanation
Correct answer: C. Build and test on a staging instance, then retrieve in production
With only two instances, the development and testing instances can be combined into a single staging instance. Customizations are made and tested on the staging instance, and the completed update set is then retrieved and committed on production.
- Why A is wrong: The docs warn against using both update sets and the Application Repository for scoped app development.
- Why B is wrong: Update sets are meant for building on a non-production instance and promoting the changes, not for developing on production.
- Why D is wrong: A clone copies everything from the source and overwrites the target, so cloning over production would replace production data, not promote changes.