The architect for a large enterprise is tasked with reviewing a proposed design created by a service partner.
Which design elements are expected to be detailed within the physical design section of the documentation?
The architect for a large enterprise is tasked with reviewing a proposed design created by a service partner.
Which design elements are expected to be detailed within the physical design section of the documentation?
The physical design section of the documentation is expected to show a design diagram illustrating the configuration and specific attributes, such as IP addresses. This section typically includes detailed schematics and configuration details of how a system needs to be built, focusing on specific hardware, network configuration, and other technical specifics. Requirements, constraints, and risks are more likely to be found in the conceptual design phase, not in the physical design section.
A. A design diagram illustrating the configuration and specific attributes, such as IP addresses
"The physical design is based on the logical design. The physical design includes specific hardware from specific vendors. This design also lists specific configurations for each of the components that are deployed" - A
Correct answer will be A
Answer A. https://www.jeffreykusters.nl/2018/06/25/breaking-down-the-conceptual-design-rcars-and-amprs-vcdx-style/
Physical design This is the portion of the design that appeals most to technical engineers. It is the “builders/engineers perspective”. It includes detailed schematics and configuration details of HOW a system needs to be built. It includes many details that are often completely
A - physical design includes IP adresses, FQDNs and so on
definetly A
A, as option b is the conceptual
Physical design This is the portion of the design that appeals most to technical engineers. It is the “builders/engineers perspective”. It includes detailed schematics and configuration details of HOW a system needs to be built. It includes many details that are often completely irrelevant to the owner of the system.
I believe is B - A list of requirements, constraints, and risks A service partner sends a design to an architect for a large enterprise to review. In this phase of a project, it makes more sense to me send "a list of requirements, constraints, and risks" What do you think?
As it states "within the physical design section of the documentation" im going with A. I wouldn't expect to see a list of requirements, constraints and risks in the physical design section.
Agree. I did not read well that part of the question. Thanks! A