Discuss Scaled Agile SAFe-DevOps Exam Topic 2 Question 7

What is the desired frequency of deployment in SAFe?

Choose the correct option from below list

AContinuous

BDaily

COnce per Iteration

DOnce per PI

Suggested Answer: D

The %C&A metric measures the percent of time downstream customers receive work that is usable as-is in the Continuous Delivery Pipeline. The %C&A metric is a measure of the quality of the work output from a process step. It indicates the percentage of time that the downstream customers receive work that is acceptable as is, without any rework or errors. To calculate the %C&A metric, the people responsible for the next step need to inspect the work output from the previous step and determine whether it meets the quality standards and expectations. They also need to provide feedback to the previous step on the defects or issues they find and how they affect the value stream. By measuring the %C&A metric, the enterprise can gain insight into the current state of the delivery process, such as the lead time, cycle time, throughput, quality, and waste. This insight can help the enterprise identify bottlenecks, dependencies, handoffs, delays, and inefficiencies that affect the flow of value. The %C&A metric can also help the enterprise understand how the flow of value can be improved by applying the principles and practices of DevOps, such as culture, automation, lean flow, measurement, and recovery.By improving the %C&A metric, the enterprise can increase customer satisfaction, reduce costs, accelerate time-to-market, and enhance business agility

Get Premium SAFe-DevOps Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

31 comments · newest first

Vanesa 11 months ago

Daily sounds reasonable too, but Continuous is ideal!

Jonelle 11 months ago

I thought it was once per iteration, but I guess not!

Dean 11 months ago

Wait, Continuous? That seems a bit much...

Quiana 11 months ago

Totally agree, Continuous is the way to go!

Ronnie 12 months ago

It's Continuous deployment in SAFe!

Dahlia 12 months ago

I’m leaning towards Once per PI, but I think that’s more about planning than deployment frequency. I need to double-check my notes.

Lavelle 12 months ago

I feel like it could be Daily, but I also recall that Continuous was emphasized in the framework.

Eun 1 year ago

I remember something about deploying once per iteration, but that feels a bit off. I should have reviewed that section more.

Dana 1 year ago

I think the answer might be Continuous, but I'm not entirely sure. We discussed deployment frequency in our last study group.

Dorothea 1 year ago

Ah, I remember now. The correct answer is once per PI, or Program Increment. SAFe is all about aligning teams and coordinating releases at the program level, not just the team level.

Tamekia 1 year ago

Okay, I've got this. The desired frequency of deployment in SAFe is once per Iteration, not continuous or daily. That aligns with the Agile principles of delivering working software frequently.

Karan 1 year ago

I'm a bit unsure about this one. I know SAFe emphasizes frequent delivery, but I can't remember if it's daily or continuous. Let me think this through...

Markus 1 year ago

Hmm, this seems like a straightforward question about SAFe practices. I think the answer is Continuous, since that's the desired frequency of deployment in SAFe.

Merissa 1 year ago

This is a tricky one. I'm tempted to go with the Power Automate option to really streamline the process, but I'm not sure if that's the best approach given the requirement to keep things simple to maintain. I'll need to weigh the pros and cons carefully.

Nikita 1 year ago

Okay, let's think this through step-by-step. I'll start the iptables service, flush the rules, delete any existing chains, and then save the configuration.

Gail 1 year ago

Once per PI? That's like the grand finale of the software symphony. I'm feeling the suspense already!

Delila 1 year ago

↳ replying to Gail

User 3: Once per PI is the big performance at the end of the season.

Catarina 1 year ago

↳ replying to Gail

User 2: Daily deployment is like a daily jam session.

Dorthy 1 year ago

↳ replying to Gail

User 1: Continuous deployment sounds like a never-ending concert.

Lucina 1 year ago

Once per iteration, huh? That's like the tortoise in the software race. Steady and reliable, but not exactly the most exciting option.

Jolanda 1 year ago

↳ replying to Lucina

User 4: Once per PI gives time for planning and coordination, a balanced approach.

Rodrigo 1 year ago

↳ replying to Lucina

User 3: Once per iteration may be slow, but it ensures stability and quality.

Leota 1 year ago

↳ replying to Lucina

User 2: Daily deployment sounds intense, but it keeps things moving quickly.

Paz 1 year ago

↳ replying to Lucina

User 1: Continuous deployment is the way to go, always staying ahead of the game.

Lashawn 1 year ago

Daily deployment? That's like trying to catch a greased pig every morning. I'll pass on that one.

Earlean 2 years ago

I believe the correct answer is A) Continuous as well. It aligns with the principles of Agile and DevOps.

Lino 2 years ago

Continuous deployment? That's like the fast and furious version of software development. I'm gonna go with that one!

Aja 1 year ago

↳ replying to Lino

User 2: Yeah, it's like the fast and furious version of software development.

Jeannetta 1 year ago

↳ replying to Lino

User 1: Continuous deployment? That sounds intense!

Loren 2 years ago

I agree with Estrella. Continuous deployment allows for faster feedback and quicker delivery of value to customers.

Estrella 2 years ago

I think the desired frequency of deployment in SAFe is A) Continuous.

Scaled Agile SAFe-DevOps Exam - Topic 2 Question 7 Discussion