Test
Solution Architecture
Crea una cuenta gratis para terminar este test
Guarda tu progreso y consulta tu resultado final.
¿Ya tienes cuenta? Inicia sesión
Preguntas del test (18)
1When is a plugin framework not very helpful?
- AWhen attempting to maximize manageability
- BWhen attempting to maximize availability
- CWhen attempting to maximize security
- DWhen attempting to maximize testability
2How can you deploy for performance?
- ABy deploying the business and data layers on multiple tiers, and use a load balancer to distribute incoming calls evenly over all tiers.
- BBy deploying all layers onto a single monolithic tier
- CBy having a secondary tier automatically take over when the primary tier fails
- DBy buffering all calls into the business layer and automatically retrying them if the business layer is offline for short periods of time.
3Your architecture adds features to a legacy system. You want to maximize the conceptual integrity of your design. What is _not_ a good strategy?
- ADevelop the features separately, wrap the legacy system with a facade pattern, and call into the facade
- BDevelop the features separately, wrap the legacy system with a SOAP service, and call into the service
- CRebuild the entire legacy system using current best practices for architecture design, and add the required features.
- DAdd the new features directly to the code of the legacy system
4You are designing a service architecture with high reliability. What is a good strategy to achieve this?
- ADeploy your business and data layers onto a primary and secondary tier. Have the service layer automatically call the secondary tier if the primary tier fails.
- BDeploy your business and data layers onto many identical tiers. Have the service layer automatically call the distribute calls overall tiers.
- CDeploy all layers onto a single monolithic tier
- DDeploy each layer on its own distributed tier
5The data layer of your architecture occasionally throws a NullReferenceException. What is the best exception management strategy for the business layer?
- ACatch and discard
- BCatch, wrap, and throw
- CAllow to propagate
- DCatch and Rethrow
6Your architecture uses a load balancer in the service layer to distribute calls over many tiers, each holding the business and data layer. The business layer is stateful, and business state is stored in local memory. Will this work? If not, what's the best way to fix it?
- AYes it will work
- BNo, it won't work. You need to change your business layer to a stateless architecture
- CNo, it won't work. You need to store state in a separate state server
- DNo, it won't work. You need to introduce session affinity to pin client sessions to a single business tier.
7What is a benefit of the MVC architecture pattern?
- AIt scales well for large user interfaces
- BIt is especially well-suited for data binding
- CIt allows for 3rd parties
- DIt promotes discoverability and resilience
8What is a disadvantage of the N-Tier architecture pattern?
- AIt's hard to get the inheritance hierarchy right
- BThe pattern scatters related code over 3 distinct classes or components
- CThe pattern requires coarse-grained interfaces
- DThe pattern has many unanticipated communications
9You want to use 3rd party controls in your architecture. Which architecture pattern would you use?
- AThe object-oriented pattern
- BThe component-based pattern
- CThe layered pattern
- DThe service-oriented architecture
10When would you use the microservice architecture?
- AWhen your architecture requires a large user interface
- BWhen your architecture requires an API
- CWhen your architecture requires a high degree of modularity
- DWhen your architecture requires and API, and the business environment contains many discrete collaborating systems with clearly defined API's
11What is a disadvantage of the object-oriented pattern?
- AIt's way too detailed and tends to micromanage the development teams
- BIt's hard to test and debug
- CIt's difficult to understand
- DIt leads to non-cohesive code
12A hospital is using the message bus pattern to process patient X-ray documents. Users are complaining about poor performance. What could be the reason, and how would you fix it?
- AService infrastructure is too lightweight. Increase processing and memory
- BThe message bus is not well suited for processing documents. Move to a microservices architecture.
- CThe architecture passes entire documents over the network between services. change this by storing the documents in a repository and only putting the document identifier on the message bus
13What are loose interactions in a layered architecture?
- AA layer may only communicate with the layer directly below
- BA layer may only communicate with the layers directly above and below
- CA layer may only communicate with the lower layers in the stack
- DA layer can communicate with any layer in the stack
14What are the implications of using a plugin framework, with each plugin supporting a user interface?
- AThe plugin framework will have to reside entirely in the business layer
- BThe plugin framework will have to reside entirely in the presentation layer
- CThe plugin framework will have to reside entirely in the systemwide layer
- DThe architecture will require some kind of plugin abstraction, to combine presentation and business plugins into an aggregated solution
15You are designing a layered architecture with strict interactions. Which layers can you safely combine onto a single-tier?
- AThe presentation and the data layer
- BThe service and the data layer
- CThe business and the data layer
- DTrick question! you should never combine key layers
16Your architecture has a business layer with several business entities. What's an easy way to load these objects with data?
- ACall a service contract to obtain a message, then transform that message to a business entity
- BCall a presentation layer component to obtain a presentation entity, then transform that object into a business entity
- CUse the .NET database classes to execute a database query, obtain data, and populate the business entity
- DUse an object-relational mapper from the data layer to execute a database query and project the data directly into the business entity
17You decide to add a REST API to your architecture. What's a consequence of this choice?
- AThe API will not be well suited for exposing business entities
- BThe API will have a high overhead
- CThe API will not be discoverable. There is no automatic universal standard for generating client code from rest endpoint
- DThe API will not support XML
18Your architecture has a service layer that uses a data transformation engine to transform customer entities from the business layer into service messages. The customer entity has 140 public fields, and the transformation 'narrows' this to a service message with only 20 public fields. Which API operation cannot be implemented?
- ARetrieving customers
- BUpdating customers
- CDeleting customers
- DCreating customers
Información
- Descripción
- Software Development Computer Science Test sobre Solution Architecture, creado por Dustin White el 28/12/2021.
- Autor
- Dustin White
- Idioma
- English
- Visitas
- 5
- Etiquetas
- Valoración
- Aún sin valoraciones Valora este test