CompTIA PK0-005 Practice Test 70

Question 690

A release pipeline has no automated tests or controlled promotion stages. Which caution is MOST directly relevant to the project manager's decision?

An untested restore instruction is not reliable evidence of rollback readiness
Automation does not remove the need for security and release authorization
A green deployment tool indicator does not prove customer-facing service works
A technically safe patch may still require a planned customer maintenance window

Explanation

Correct Answer

Automation does not remove the need for security and release authorization. The underlying reason is that cI/CD automates integration and delivery steps under governed controls.

Incorrect Answers

This is a caution about rollback readiness, not the immediate risk in ci cd controls. A rollback plan limits the consequences of a failed operational change.

This is a caution about postchange validation, not the immediate risk in ci cd controls. Operational change closure requires evidence of safe service after deployment.

This is a caution about maintenance window, not the immediate risk in ci cd controls. Infrastructure change control coordinates service impact and authorized timing.

Question 691

A project uses an on-premises hardware reboot procedure for a managed SaaS tenant. Which project-management action BEST addresses this situation?

Run documented postchange service validation and record any needed rollback
Test changes in an appropriately representative staging environment first
Adapt change governance to the cloud service responsibility model
Schedule a controlled maintenance window with customer notifications

Explanation

Correct Answer

Cloud change control differs based on provider ownership of infrastructure layers. Here, a project uses an on-premises hardware reboot procedure for a managed saas tenant; the chosen action targets that failure. Verification: verify provider and customer change obligations are documented.

Incorrect Answers

This response addresses postchange validation, but the stated decision concerns cloud change differences. Operational change closure requires evidence of safe service after deployment.

This response addresses staging versus production, but the stated decision concerns cloud change differences. Staging limits exposure while validating changes before live service.

This response addresses maintenance window, but the stated decision concerns cloud change differences. Infrastructure change control coordinates service impact and authorized timing.

Question 692

The team follows this response: Adapt change governance to the cloud service responsibility model. Context: a project uses an on-premises hardware reboot procedure for a managed saas tenant. Which evidence BEST verifies the intended outcome?

Confirm staging results meet criteria before authorized production rollout
Verify a rehearsal proves recovery steps work within tolerance
Verify provider and customer change obligations are documented
Review pipeline runs for reproducible artifacts, tests and approvals

Explanation

Correct Answer

Verify provider and customer change obligations are documented. That evidence tests the response to a project uses an on-premises hardware reboot procedure for a managed saas tenant instead of an unrelated project condition.

Incorrect Answers

This check would validate staging versus production, not the result required by the cloud change differences case. Staging limits exposure while validating changes before live service.

This check would validate rollback readiness, not the result required by the cloud change differences case. A rollback plan limits the consequences of a failed operational change.

This check would validate ci cd controls, not the result required by the cloud change differences case. CI/CD automates integration and delivery steps under governed controls.

Question 693

Cloud deployment planning ignores provider maintenance and customer configuration scope. Which principle MOST directly explains how the project should be managed?

Staging limits exposure while validating changes before live service
Infrastructure change control coordinates service impact and authorized timing
A rollback plan limits the consequences of a failed operational change
Cloud change control differs based on provider ownership of infrastructure layers

Explanation

Correct Answer

Cloud change control differs based on provider ownership of infrastructure layers. The situation involves cloud deployment planning ignores provider maintenance and customer configuration scope, so this is the governing distinction.

Incorrect Answers

That principle concerns staging versus production rather than the problem of cloud change differences. Staging limits exposure while validating changes before live service.

That principle concerns maintenance window rather than the problem of cloud change differences. Infrastructure change control coordinates service impact and authorized timing.

That principle concerns rollback readiness rather than the problem of cloud change differences. A rollback plan limits the consequences of a failed operational change.

Question 694

Cloud deployment planning ignores provider maintenance and customer configuration scope. Which caution is MOST directly relevant to the project manager's decision?

Passing a development demo is not necessarily sufficient production readiness
A green deployment tool indicator does not prove customer-facing service works
A technically safe patch may still require a planned customer maintenance window
A cloud service does not grant the tenant control over provider hardware windows

Explanation

Correct Answer

A cloud service does not grant the tenant control over provider hardware windows. The underlying reason is that cloud change control differs based on provider ownership of infrastructure layers.

Incorrect Answers

This is a caution about staging versus production, not the immediate risk in cloud change differences. Staging limits exposure while validating changes before live service.

This is a caution about postchange validation, not the immediate risk in cloud change differences. Operational change closure requires evidence of safe service after deployment.

This is a caution about maintenance window, not the immediate risk in cloud change differences. Infrastructure change control coordinates service impact and authorized timing.

Question 695

A firewall modification is declared finished without testing application paths. Which project-management action BEST addresses this situation?

Test changes in an appropriately representative staging environment first
Run documented postchange service validation and record any needed rollback
Schedule a controlled maintenance window with customer notifications
Adapt change governance to the cloud service responsibility model

Explanation

Correct Answer

Operational change closure requires evidence of safe service after deployment. Here, a firewall modification is declared finished without testing application paths; the chosen action targets that failure. Verification: confirm monitoring and functional checks satisfy approved change criteria.

Incorrect Answers

This response addresses staging versus production, but the stated decision concerns postchange validation. Staging limits exposure while validating changes before live service.

This response addresses maintenance window, but the stated decision concerns postchange validation. Infrastructure change control coordinates service impact and authorized timing.

This response addresses cloud change differences, but the stated decision concerns postchange validation. Cloud change control differs based on provider ownership of infrastructure layers.

Question 696

The team follows this response: Run documented postchange service validation and record any needed rollback. Context: a firewall modification is declared finished without testing application paths. Which evidence BEST verifies the intended outcome?

Confirm staging results meet criteria before authorized production rollout
Review pipeline runs for reproducible artifacts, tests and approvals
Verify provider and customer change obligations are documented
Confirm monitoring and functional checks satisfy approved change criteria

Explanation

Correct Answer

Confirm monitoring and functional checks satisfy approved change criteria. That evidence tests the response to a firewall modification is declared finished without testing application paths instead of an unrelated project condition.

Incorrect Answers

This check would validate staging versus production, not the result required by the postchange validation case. Staging limits exposure while validating changes before live service.

This check would validate ci cd controls, not the result required by the postchange validation case. CI/CD automates integration and delivery steps under governed controls.

This check would validate cloud change differences, not the result required by the postchange validation case. Cloud change control differs based on provider ownership of infrastructure layers.

Question 697

A production release receives approval but no end-to-end service checks. Which principle MOST directly explains how the project should be managed?

CI/CD automates integration and delivery steps under governed controls
A rollback plan limits the consequences of a failed operational change
Operational change closure requires evidence of safe service after deployment
Infrastructure change control coordinates service impact and authorized timing

Explanation

Correct Answer

Operational change closure requires evidence of safe service after deployment. The situation involves a production release receives approval but no end-to-end service checks, so this is the governing distinction.

Incorrect Answers

That principle concerns ci cd controls rather than the problem of postchange validation. CI/CD automates integration and delivery steps under governed controls.

That principle concerns rollback readiness rather than the problem of postchange validation. A rollback plan limits the consequences of a failed operational change.

That principle concerns maintenance window rather than the problem of postchange validation. Infrastructure change control coordinates service impact and authorized timing.

Question 698

A production release receives approval but no end-to-end service checks. Which caution is MOST directly relevant to the project manager's decision?

A green deployment tool indicator does not prove customer-facing service works
Passing a development demo is not necessarily sufficient production readiness
Automation does not remove the need for security and release authorization
A cloud service does not grant the tenant control over provider hardware windows

Explanation

Correct Answer

A green deployment tool indicator does not prove customer-facing service works. The underlying reason is that operational change closure requires evidence of safe service after deployment.

Incorrect Answers

This is a caution about staging versus production, not the immediate risk in postchange validation. Staging limits exposure while validating changes before live service.

This is a caution about ci cd controls, not the immediate risk in postchange validation. CI/CD automates integration and delivery steps under governed controls.

This is a caution about cloud change differences, not the immediate risk in postchange validation. Cloud change control differs based on provider ownership of infrastructure layers.

Question 699

A cloud provider supplies virtual machines while the customer configures operating-system patches and application software. Which cloud service model is described?

Infrastructure as a Service (IaaS)
Fully managed business process outsourcing
Platform as a Service (PaaS)
Software as a Service (SaaS)

Explanation

Correct Answer

IaaS provides computing infrastructure while the customer retains guest operating-system and application responsibility.

Incorrect Answers

Business process outsourcing describes an operational service arrangement, not this virtual infrastructure model.

PaaS typically abstracts much of the runtime platform and guest OS management from the customer.

SaaS delivers a complete provider-operated application rather than customer-managed virtual machines.

Question 700

A production deployment has a verified rollback taking 25 minutes. The approved outage budget is 20 minutes and validation needs 5 minutes. What is the best prechange decision?

Skip validation to fit the window
Proceed because rollback time is only an estimate
Assume operations can complete rollback instantly
Do not proceed without revising the plan or securing an adequate window

Explanation

Correct Answer

The combined worst-case validation and rollback is at least 5 + 25 = 30 minutes, exceeding the 20-minute approved window; revise and reapprove.

Incorrect Answers

Skipping planned validation removes evidence the production change is safe.

Treating a 25-minute verified rollback as negligible understates outage exposure.

An assumption of instantaneous rollback contradicts the verified duration.

Pass Your CompTIA PK0-005 Exam Easy!

Question 690

Explanation

Correct Answer

Incorrect Answers

Question 691

Explanation

Correct Answer

Incorrect Answers

Question 692

Explanation

Correct Answer

Incorrect Answers

Question 693

Explanation

Correct Answer

Incorrect Answers

Question 694

Explanation

Correct Answer

Incorrect Answers

Question 695

Explanation

Correct Answer

Incorrect Answers

Question 696

Explanation

Correct Answer

Incorrect Answers

Question 697

Explanation

Correct Answer

Incorrect Answers

Question 698

Explanation

Correct Answer

Incorrect Answers

Question 699

Explanation

Correct Answer

Incorrect Answers

Question 700

Explanation

Correct Answer

Incorrect Answers

CompTIA Project+ (PK0-005) Practice Tests