C1000-169 無料問題集「IBM Cloud Associate SRE V2」

（A）Number of Employees in the Organization

（B）CPU Usage

（C）Load Balancer Configuration

（D）Network Latency

（A）Service Level Indicators (SLIs)

（B）Service Level Agreements (SLAs)

（C）Service Level Objectives (SLOs)

（D）Service Level Targets (SLTs)

（A）Ignoring potential risks and issues to expedite the deployment process

（B）Reviewing operational processes and documentation before deployment

（C）Conducting the ORR after the deployment process is completed

（D）Assigning blame for any issues during deployment

（A）SREs are not involved in application deployments

（B）SREs focus on the reliability and availability of applications during deployment

（C）SREs are responsible for development only and not deployment activities

（D）SREs handle all aspects of application development and deployment

（A）It only supports applications in a specific region of the IBM Cloud

（B）It abstracts away infrastructure management for serverless applications

（C）It requires manual scaling of applications based on traffic demands

（D）It is limited to a specific programming language for applications

（A）Infrastructure ensures high availability through redundancy

（B）Failure domains are isolated parts of the system

（C）Infrastructure ensures high availability by minimizing failure domains

（D）Failure domains are areas where failures are not possible

（A）Releasing software updates quickly and reliably

（B）Allowing developers to bypass testing phases

（C）Automating the entire deployment process

（D）Reducing the number of software releases

（A）By delaying incident response until after business hours

（B）By following a structured and coordinated incident response plan

（C）By assigning incidents to a single individual for resolution

（D）By involving multiple departments without any coordination

（A）By ignoring user-reported issues until they become critical incidents

（B）By checking DNS configurations and CDN caching settings

（C）By directly modifying the network settings in production

（D）By performing system-wide reboots without investigation

（A）Monitoring system logs and analyzing anomalies

（B）Ignoring security alerts and notifications

（C）Waiting for an incident to occur before taking any action

（D）Regularly conducting security audits