Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Scrum PSD Exam - Topic 1 Question 54 Discussion

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

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

Suggested Answer: D

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


Get Premium PSD Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
42 comments · newest first
RI
Rima 10 months ago
Architecture needs to align with the vision from the start.
GR
Gregoria 11 months ago
Wait, is it really designed before the first Sprint? That seems early!
DE
Devon 11 months ago
I disagree, it should evolve throughout development.
DE
Delpha 11 months ago
Definitely before writing any code!
TA
Talia 11 months ago
I think it's usually decided in Sprint 0.
JE
Jeff 12 months ago
I’m leaning towards the idea that it’s designed with the vision, but I wonder if that’s too simplistic.
FR
Frank 12 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.
CR
Craig 12 months ago
I remember a practice question that mentioned architecture evolving throughout development, which makes sense too.
RI
Rikki 1 year ago
I think the architecture is usually decided early on, maybe during Sprint 0, but I'm not completely sure.
SI
Simona 1 year 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.
DA
Dana 1 year ago
The architecture is definitely designed upfront, before any coding starts. That's just common sense.
RA
Raul 1 year 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.
DA
Dannette 1 year ago
I'm pretty sure the system architecture is decided early on, before the first sprint. That seems like the most logical answer.
GI
Gilma 1 year ago
This is a tricky one. I'll need to think through the different options carefully.
JU
Jules 1 year 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.
WH
Whitley 1 year ago
Hmm, this looks like a tricky one. I'll need to think through the different options carefully.
AN
Antonio 1 year ago
I remember practicing with a similar question, and I think DEP is the right choice for corporate-owned devices.
PH
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!
DA
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?
NA
Nakita 1 year ago
↳ replying to Dalene
C) Before writing code.
HA
Hana 1 year ago
↳ replying to Dalene
B) In the beginning of the project, during Sprint 0.
MA
Major 1 year ago
↳ replying to Dalene
A) It is designed along with the vision, before the first Sprint.
NI
Nida 1 year ago
Option D, for sure. The only constant in software is change, am I right? Gotta keep that architecture nimble!
DI
Dick 1 year ago
↳ replying to Nida
Definitely, staying agile with the architecture is essential to handle changes.
JA
Jacklyn 1 year ago
↳ replying to Nida
I agree, being able to adapt as you go is crucial in software development.
RO
Ronnie 1 year ago
↳ replying to Nida
Absolutely, flexibility is key when it comes to architecture.
GE
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?
PA
Patrick 1 year ago
↳ replying to Germaine
Definitely, flexibility in architecture is crucial for success.
CA
Cathrine 1 year ago
↳ replying to Germaine
I agree, it's best to decide as understanding emerges.
FE
Fernanda 1 year ago
↳ replying to Germaine
Yeah, keeping the architecture flexible is important.
WA
Walton 1 year ago
↳ replying to Germaine
I think D makes sense, flexibility is key.
ME
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.
KA
Kate 1 year ago
↳ replying to Melissa
Yes, I agree. It's crucial to adapt the system's architecture as our understanding of the project evolves.
LA
Layla 1 year ago
↳ replying to Melissa
I think D is the best option too. It's important to continuously refine the architecture as we learn more.
MI
Mitzie 2 years ago
I believe the architecture evolves throughout development as we gain more understanding of the project requirements.
NI
Nickolas 2 years 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.
SH
Shala 1 year ago
↳ replying to Nickolas
Yes, the architecture should be flexible and able to change as needed during the development process.
TI
Tina 1 year ago
↳ replying to Nickolas
I think it's crucial to adapt the architecture based on new insights during development.
KE
Kelvin 1 year ago
↳ replying to Nickolas
It's important to continuously refine and improve the architecture as we gain more understanding.
IZ
Izetta 1 year ago
↳ replying to Nickolas
I agree, the system's architecture should evolve as we learn more about the problem.
DE
Denny 2 years ago
I agree with Lindsey, it's important to have a plan in place before diving into coding.
LI
Lindsey 2 years ago
I think the system's architecture is decided before writing code.
0/2000 characters

Save Cancel