Deployment

What two phases make up SAP Cloud ALM for Implementation, and why does CI/CD belong to the second one?

Within the implementation area, what is the final step after testing, and which orchestration tools support it?

In an SAP Activate project, what triggers the start of the deploy phase, and what example roadmap task marks it?

How does a rollout differ from a roll-in in an SAP Cloud ALM project?

To which SAP Activate phase is the deployment of functions assigned, and how does an agile approach change when import actually happens?

Besides importing changes into production, what other deploy-phase activities does SAP Activate expect you to plan for?

Before change control can work, what three preparatory measures must the release manager complete, including how systems are assigned?

How many deployment plans can a project be linked to for change control, and what does that link give the project access to?

Which app and tabs do you use to set up system groups and deployment plans, and what else can you configure there?

What are the steps to create a system group in the Projects and Setup app, and what naming convention is recommended?

What does a deployment plan group together, and how is it maintained relative to system groups?

What are the steps to create a deployment plan and define its releases?

Why would you lock a future release in a deployment plan, and what does locking prevent?

Who deactivates and activates releases over time, and can release planning still change afterward?

How do you attach system groups to a release inside a deployment plan?

What becomes possible when several system groups are added to one deployment plan?

When does it actually make sense to assign the same deployment plan to more than one project?

How is a feature's status changed, and what does its status control on the system line?

What does the initial feature status mean, and what happens in it?

What is the difference between the Not planned and Will be implemented feature statuses?

What has happened to a feature's transports when it reaches the In the test status?

What does the Ready for production status signify about a feature?

What characterizes the Deployed status, and why is it significant for change control?

If you delete a feature that already had transports created on the development system, what problem must you handle and what can you not undo?

Is feature creation restricted by authorizations, and must every feature reference a requirement or user story?

In a small SAP Cloud ALM project you consider skipping requirements and user stories entirely. What are you trading away, and what can you still not skip?

New requirements land in the prepare phase, but the requirements backlog for features only shows realize-phase ones. What does moving a requirement from prepare to realize actually signify?

You have one requirement but want to split its work across two sprints. Can you attach both features to that single requirement, and can a feature belong to two requirements at once?

Once you choose Create then Feature, what is actually mandatory, and why do teams prefix titles with FEA or COR?

Why is it advantageous to carry a text fragment like the business process name Pick Warehouse Orders from the requirement into the feature title?

A feature's technical description isn't free text but a set of named modules. What are they and what belongs in each?

You want to attach your functional test cases directly to a feature as linked objects. Why does SAP Cloud ALM make you write them into the Test case text module instead?

What are release notes in the deployment context, and why does it pay off to jot them down as bullet points inside each feature as you go?

After a feature is specified, how does SAP Cloud ALM actually control change, and why does the exact transport tooling differ from project to project?

When you open the create-transport popup for a feature, why is the Title already filled in, and which four fields must you supply?

The functional test on a transport of copy fails. What is the correct recovery loop, and how do you inspect what was imported?

After a functional test finally passes, what does the Release action do to the modifiable transports, and what changes about them afterward?

How do you get released transports into the test system, and how can you tell the import succeeded from the transport list?

Development and import to test are done. Which button hands the feature to test management, and what status results?

Before you hand a newly live solution over to the IT support operations team, which conditions should be satisfied?

How is SAP Cloud ALM split at the top level, and which two subareas does the book focus on?

On what basis are individual systems assigned inside a system group, and what does a single system group typically represent?

A release management team wants a reusable list of confirmed requirements to turn into features. How do they build that requirements backlog in SAP Cloud ALM, and which filters isolate the ready ones?

Why bother saving your filtered requirements search instead of just re-running the filters each time you need to create features?

When you open a requirement's detail view before creating a feature, what does the header show versus the lower tab area?

Beyond title and description, which ownership and grouping fields do you maintain on a feature's Additional Information tab?

Who creates the transports for a feature: the release management team up front, or the developers during implementation?

Testing is complete and go-live criteria are met. Which action promotes the feature, and to what status?

How is the transport imported into production once a feature is approved, and why does its Target Tenant column go blank afterward?

An individual developer is about to push a feature's transport into production on their own. Why is that the wrong person to do it?

The transport is live in production but the feature still isn't Deployed. What final action closes it out, and what changes on the feature afterward?

What governs when a release actually gets imported into production, and what should happen before that date arrives?

Instead of importing each feature's transport one by one, how do you mass-deploy a whole release to production in SAP Cloud ALM?

You've selected features for mass deployment but the Deploy to Production button is greyed out. What must be true of every selected feature before it activates?

Once deployment or go-live is done, which project phase begins and what characterizes it?

Why must configurations and developments reach production through transports in a defined order, and what infrastructure records them on-premise versus in the cloud?

What is a deployment plan in SAP Cloud ALM, and what happens inside it?

In SAP Cloud ALM, what is a feature and what role does it play in the deploy phase?

At what point and by whom is a feature typically created, even though it belongs to the deploy phase?

Once developers have recorded their work, how does the feature move those changes toward test and production?

What key information does a feature hold together?

A freshly saved transport shows Creation Pending, not Modifiable. What is happening behind the scenes, and when can developers finally write to it?

After the transport exists and changes are documented, how do you move the feature to Implemented, and can you undo it if you jumped the gun?

Why would you assign the relevant user stories to a feature even after implementation has already started?

What problem does a transport of copy solve, and how does it actually shrink the number of transports that end up in a release?

You try to create a transport of copy straight from the feature but it won't go. What prerequisite is easy to miss?

Walk through creating a transport of copy from a feature, and say what SAP Cloud ALM does the moment you confirm it.

Where in the feature do you check a transport of copy's ID and whether it actually deployed to the target?

What are the steps to link a deployment plan to a project?