Scrum PSD Exam - Topic 1 Question 54 Discussion

Actual exam question for Scrum's PSD exam

Question #: 54
Topic #: 1

[All PSD Questions]

When is a system's architecture decided? (choose the best answer)

AIt is designed along with the vision, before the first Sprint.

BIn the beginning of the project, during Sprint 0.

CBefore writing code.

DThroughout development, as understanding emerges.

Show Suggested Answer

Suggested Answer: D

There is no time in between sprints, so there cannot be activities.

by Leatha at Mar 06, 2024, 09:33 PM

Limited Time Offer

25%

Off

Get Premium PSD Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Rima

6 months ago

Architecture needs to align with the vision from the start.

upvoted 0 times

...

Gregoria

6 months ago

Wait, is it really designed before the first Sprint? That seems early!

upvoted 0 times

...

Devon

6 months ago

I disagree, it should evolve throughout development.

upvoted 0 times

...

Delpha

7 months ago

Definitely before writing any code!

upvoted 0 times

...

Talia

7 months ago

I think it's usually decided in Sprint 0.

upvoted 0 times

...

Jeff

7 months ago

I’m leaning towards the idea that it’s designed with the vision, but I wonder if that’s too simplistic.

upvoted 0 times

...

Frank

7 months ago

I feel like it should be before writing any code, but I also recall discussions about it being flexible as the project progresses.

upvoted 0 times

...

Craig

7 months ago

I remember a practice question that mentioned architecture evolving throughout development, which makes sense too.

upvoted 0 times

...

Rikki

8 months ago

I think the architecture is usually decided early on, maybe during Sprint 0, but I'm not completely sure.

upvoted 0 times

...

Simona

8 months ago

I think the best answer is that the architecture evolves throughout the project as the team's understanding grows. That seems most in line with Agile principles.

upvoted 0 times

...

Dana

8 months ago

The architecture is definitely designed upfront, before any coding starts. That's just common sense.

upvoted 0 times

...

Raul

8 months ago

Hmm, I'm not totally sure about this. I'll have to review my notes on Agile development to decide between a few of these options.

upvoted 0 times

...

Dannette

8 months ago

I'm pretty sure the system architecture is decided early on, before the first sprint. That seems like the most logical answer.

upvoted 0 times

...

Gilma

8 months ago

This is a tricky one. I'll need to think through the different options carefully.

upvoted 0 times

...

Jules

8 months ago

The MANAGER column being a foreign key referencing EMPNO makes sense, but I'm not sure about the index being created automatically. I'll need to think that through.

upvoted 0 times

...

Whitley

8 months ago

Hmm, this looks like a tricky one. I'll need to think through the different options carefully.

upvoted 0 times

...

Antonio

8 months ago

I remember practicing with a similar question, and I think DEP is the right choice for corporate-owned devices.

upvoted 0 times

...

Phuong

1 year ago

Option D, because the only thing we architects are good at is changing our minds constantly. Keeps the developers on their toes!

upvoted 0 times

...

Dalene

1 year ago

Architecture? I thought we were just winging it and adding features until the client gets tired of paying us. Where's the fun in planning ahead?

upvoted 0 times

Nakita

11 months ago

C) Before writing code.

upvoted 0 times

...

Hana

11 months ago

B) In the beginning of the project, during Sprint 0.

upvoted 0 times

...

Major

12 months ago

A) It is designed along with the vision, before the first Sprint.

upvoted 0 times

...

Nida

1 year ago

Option D, for sure. The only constant in software is change, am I right? Gotta keep that architecture nimble!

upvoted 0 times

Dick

12 months ago

Definitely, staying agile with the architecture is essential to handle changes.

upvoted 0 times

...

Jacklyn

12 months ago

I agree, being able to adapt as you go is crucial in software development.

upvoted 0 times

...

Ronnie

12 months ago

Absolutely, flexibility is key when it comes to architecture.

upvoted 0 times

...

Germaine

1 year ago

Hmm, I was leaning towards B, but I can see the logic in D. Gotta keep that architecture flexible, you know?

upvoted 0 times

Patrick

1 year ago

Definitely, flexibility in architecture is crucial for success.

upvoted 0 times

...

Cathrine

1 year ago

I agree, it's best to decide as understanding emerges.

upvoted 0 times

...

Fernanda

1 year ago

Yeah, keeping the architecture flexible is important.

upvoted 0 times

...

Walton

1 year ago

I think D makes sense, flexibility is key.

upvoted 0 times

...

Melissa

1 year ago

I agree, D is the correct answer. Architecture is not a one-time event, it's an ongoing process of adaptation and refinement.

upvoted 0 times

Kate

1 year ago

Yes, I agree. It's crucial to adapt the system's architecture as our understanding of the project evolves.

upvoted 0 times

...

Layla

1 year ago

I think D is the best option too. It's important to continuously refine the architecture as we learn more.

upvoted 0 times

...

Mitzie

1 year ago

I believe the architecture evolves throughout development as we gain more understanding of the project requirements.

upvoted 0 times

...

Nickolas

1 year ago

Option D is the best answer. The system's architecture is refined and improved throughout the development process as our understanding of the problem grows.

upvoted 0 times