Which of the following is not a benefit of standardization?
- Consistent management
- Better control of system access
- Uniform logging across systems
- Flexible deployment scenarios
Answer: Flexible deployment scenarios
Cloud Computing | Google & AWS | Multiple Choice | Questions and Answers
Answer: Flexible deployment scenarios
Answer: Change management
Answer: Document the solution.
Answer: HBA
Answer: Hotfix
Answer: Resize the virtual machine.
Answer: Baseline
Answer: Capacity planning
Answer: Shared storage
Answer: Rolling updates
Answer: MTBF
Answer: Service level agreement
Answer: Service design
Answer: Standard operating procedure
Answer: Small changes made to code are tested immediately in the development landscape before being passed to other landscapes.
Answer: DevOps ticketing is not a method for deploying application updates. The methods are manual version updating, end-user updating, and using a package manager.
Answer: A code repository organizes code branches to keep code consistent even when multiple teams are working on the same areas in parallel. Developers can publish code changes to the repository, can synchronize their local copy of the code with the repository, or can revert to previously published versions.
Answer: Flexible deployment scenarios is not a benefit of standardization because standardization establishes consistent deployment scenarios and does not allow for each one to be deployed however the user or administrator wishes.
Answer: A maintenance window is an agreed-upon, predefined time period during which service interruptions are least impactful to the customer. This could fall at any time, and depends on the patterns of business activity for that particular customer.
Answer: Chargebacks can be used to establish metrics on mailbox usage per department so that department budgets can be billed for the expense of hosting department e-mail.