I85PREP
⌘ K
OutSystems Platform Ops Engineer study materials
OutSystems Platform Ops Engineer study resources

OutSystems Platform Ops Engineer practice questions

One question at a time. Build your OutSystems Platform Ops Engineer understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Platform operations and environment management

In OutSystems LifeTime, which environment role is responsible for hosting the version of an application that end users actually access in production?

  1. The Production environment Correct answer.
  2. The Staging environment used only for load tests
  3. The Quality Assurance environment
  4. The Development environment

Explanation

The Production environment is the stage where the application is deployed for real end users, and it is normally protected so that only published, tested versions reach it. Development and QA exist earlier in the pipeline to build and validate the application before it is promoted.

Question 2Platform operations and environment management

Which LifeTime operation promotes a tested application version from one environment to the next in the deployment pipeline?

  1. Publishing the module in the source environment
  2. Running the module's unit tests
  3. Tagging the application in Service Studio
  4. Deploying the application through LifeTime Correct answer.

Explanation

Deployment is the LifeTime action that moves a tagged application version between environments along the pipeline. Publishing only compiles and runs the module in its current environment, and tagging merely marks a version as a candidate.

Question 3Platform operations and environment management

An operator needs to give a new team member access to LifeTime with permission to deploy applications but without the ability to manage users or environments. Which approach fits the platform's role model?

  1. Grant the user the Service Studio developer profile only
  2. Add the user to an IT role scoped to the relevant applications and teams Correct answer.
  3. Assign the user the built-in Administrator role in LifeTime
  4. Share the Administrator credentials with the new team member

Explanation

LifeTime uses IT roles that can be scoped to specific applications and teams, so permissions can be limited to deployment activities without granting full administrative control. The Administrator role is broad and should be reserved for operators who genuinely need environment and user management.

Question 4Platform operations and environment management

What is the primary purpose of tagging an application version in LifeTime before deployment?

  1. It compresses the application for faster transfer
  2. It automatically fixes compilation errors in the version
  3. It deletes older versions from the repository
  4. It marks a specific version as the candidate to deploy to a target environment Correct answer.

Explanation

Tagging identifies a concrete version so operators can select exactly that build for promotion to a target environment. It does not modify the code, compress artifacts, or remove historical versions from the repository.

Question 5Platform operations and environment management

A deployment to Production fails during the compile step because a dependency module was not included. What is the most appropriate operational response?

  1. Downgrade the target environment to an earlier platform version
  2. Add the missing dependency to the application and redeploy a corrected version Correct answer.
  3. Restart the Production front-end servers to clear the error
  4. Retry the same deployment repeatedly until it succeeds

Explanation

A missing dependency is a packaging problem, so the fix is to include the dependency in the application and deploy a corrected version. Retrying or restarting servers cannot supply a module that the deployment package lacks.

Question 6Platform operations and environment management

Which statement best describes how OutSystems separates the development and production runtime so that a faulty deployment can be rolled back?

  1. Each deployment overwrites the previous version with no retained copy
  2. LifeTime can redeploy a previously tagged version to restore the prior state Correct answer.
  3. Rollback requires restoring the entire database from a nightly backup
  4. Rollback is impossible once a version reaches Production

Explanation

Because tagged versions are retained, LifeTime can redeploy an earlier tagged version to return an environment to a known-good state. This avoids relying solely on full database restores and keeps rollback targeted to the application.

Question 7Platform operations and environment management

An operator must confirm which environment a given application version is currently running in before approving the next promotion. Where is this information authoritatively tracked?

  1. In the email thread where the release was requested
  2. In the Production server's operating system event log
  3. In the local Service Studio cache on each developer machine
  4. In LifeTime's application and deployment records Correct answer.

Explanation

LifeTime maintains the authoritative record of which application versions are deployed to which environments, making it the source of truth for promotion decisions. Developer caches, email threads, and OS logs are not reliable deployment registries.

Question 8Platform operations and environment management

What does the OutSystems platform's environment health monitoring primarily help an operator detect?

  1. Syntax errors in unpublished modules
  2. Runtime issues such as performance degradation and errors in a deployed environment Correct answer.
  3. Unused variables in a module's logic
  4. Missing translations in the user interface

Explanation

Environment health monitoring surfaces runtime signals such as error rates, slow requests, and resource pressure in a deployed environment. Design-time issues like syntax errors or unused variables are handled inside Service Studio, not by environment monitoring.

Question 9Platform operations and environment management

A Production environment shows rising response times after a new deployment, while QA showed no such issue. Which first step best isolates whether the deployment caused the regression?

  1. Disable health monitoring to reduce overhead
  2. Immediately roll back to the previous tagged version and compare metrics Correct answer.
  3. Rebuild the application from scratch in Development
  4. Increase the number of front-end servers before investigating

Explanation

Rolling back to the last known-good tagged version and comparing metrics isolates whether the new deployment introduced the regression. Adding capacity or disabling monitoring obscures the signal and delays diagnosis.

Question 10Platform operations and environment management

Which practice best supports consistent configuration across Development, QA, and Production environments?

  1. Hard-coding Production connection strings in the module source
  2. Copying the Production database into Development on every release
  3. Using environment-specific configurations managed centrally so each stage receives appropriate values Correct answer.
  4. Manually editing each environment's settings after every deployment

Explanation

Centralized, environment-specific configuration lets each stage receive the correct values without hard-coding secrets or repeating manual edits. This reduces drift and the risk of Production settings leaking into lower environments.

Question 11Platform operations and environment management

An operator wants to prevent developers from deploying directly to Production. Which LifeTime control most directly enforces this?

  1. Restricting deployment permissions so only authorized roles can deploy to Production Correct answer.
  2. Requiring developers to use a different IDE
  3. Removing all developers from the Development environment
  4. Disabling the QA environment

Explanation

Deployment permissions in LifeTime determine who may promote applications to a given environment, so limiting Production deployment to authorized roles enforces the control. Removing Development access or disabling QA does not govern Production deployment rights.

Question 12Platform operations and environment management

Why should an operator avoid deploying an untagged version directly to Production?

  1. Untagged versions run only in Development by design
  2. Without a tag there is no reliable reference point for rollback or audit Correct answer.
  3. Tagging is required to start the application servers
  4. Untagged versions cannot compile in LifeTime

Explanation

A tag creates an identifiable, reproducible reference for the deployed build, which underpins rollback and audit trails. Deploying without a tag leaves no clear marker of exactly what was released.

Question 13Platform operations and environment management

Which item is typically part of a platform operator's routine environment maintenance for a Production stage?

  1. Deleting all logs to reclaim disk space daily
  2. Reviewing deployment history and health alerts for anomalies Correct answer.
  3. Rewriting business logic in Production modules
  4. Changing the application's data model directly in Production

Explanation

Routine operations include reviewing deployment history and health alerts to catch anomalies early. Business logic, data models, and logs should be handled through proper change and retention processes rather than ad hoc edits in Production.

Question 14Platform operations and environment management

A module in QA works correctly, but after deployment to Production it fails to connect to an external service. What is the most likely operational cause?

  1. The developer used the wrong variable naming convention
  2. The module has too many screens
  3. The Production environment's configuration or network access differs from QA Correct answer.
  4. The tag was created in the wrong color

Explanation

Environment-specific differences such as configuration values, credentials, or network egress rules commonly explain why a service call works in QA but fails in Production. These must be verified per environment rather than assumed identical.

Question 15Platform operations and environment management

Which LifeTime capability helps an operator understand which users performed recent deployments and when?

  1. The Service Studio welcome page
  2. The application's end-user login screen
  3. The Production server's DNS configuration
  4. Deployment history and audit records in LifeTime Correct answer.

Explanation

LifeTime records deployment history and audit information, including who deployed what and when, supporting accountability and investigation. End-user screens and local IDE pages do not provide this operational record.

Question 16Platform operations and environment management

An operator is asked to reduce risk when promoting a large release that touches several applications with shared dependencies. Which approach is most sound?

  1. Deploy all applications simultaneously to save time
  2. Deploy each application independently in arbitrary order without coordination
  3. Skip QA validation to shorten the release window
  4. Plan the deployment order based on dependency relationships and validate in QA first Correct answer.

Explanation

When applications share dependencies, deployment order matters, so planning it around dependency relationships and validating in QA reduces the chance of broken references. Arbitrary or simultaneous deployment can leave consumers running against incompatible versions.

Question 17Platform operations and environment management

What is the role of the OutSystems platform server component in an environment?

  1. It compiles, runs, and serves the deployed applications and manages their lifecycle Correct answer.
  2. It provides the user interface design canvas
  3. It replaces the need for a database
  4. It stores only the source code files for developers

Explanation

The platform server compiles and runs deployed applications and manages their runtime lifecycle within an environment. The design canvas belongs to Service Studio, and the platform server does not replace the database.

Question 18Platform operations and environment management

An operator notices that a Production environment has a much older platform version than QA. Why is this a concern for deployments?

  1. Older platform versions always run faster
  2. Version differences are irrelevant as long as the database is the same
  3. The platform version affects only the color scheme
  4. Applications built on a newer platform version may not deploy or run correctly on an older one Correct answer.

Explanation

Applications compiled against a newer platform version may rely on features or runtime behavior absent in an older environment, causing deployment or runtime failures. Keeping platform versions aligned across the pipeline reduces this risk.

Question 19Platform operations and environment management

Which action best protects sensitive Production data when troubleshooting an issue that requires reproducing behavior?

  1. Email Production records to the support team
  2. Reproduce the issue using anonymized or masked data in a non-Production environment Correct answer.
  3. Disable database encryption to speed up queries
  4. Export the full Production database to a developer laptop

Explanation

Troubleshooting should use anonymized or masked data in a lower environment to avoid exposing sensitive Production records. Exporting full Production data or disabling encryption creates serious data-protection and compliance risks.

Question 20Platform operations and environment management

An operator must schedule routine maintenance that briefly interrupts Production. Which consideration is most important before proceeding?

  1. Performing it during peak traffic to observe real load
  2. Running it without a rollback plan to save time
  3. Avoiding any communication to prevent confusion
  4. Choosing a window with the least business impact and notifying stakeholders in advance Correct answer.

Explanation

Maintenance that interrupts Production should be scheduled for a low-impact window with advance stakeholder notification. Running during peak load or without a rollback plan increases risk and business disruption.

Question 21Platform operations and environment management

A deployment succeeds but the application returns errors only for some users. Which area should the operator investigate first?

  1. The font used in the application's theme
  2. The number of modules in the application
  3. The physical network cable of the server
  4. Role-based permissions and data visibility rules for the affected users Correct answer.

Explanation

Errors limited to specific users commonly stem from role assignments, permission checks, or data visibility rules that differ per user. Investigating these access-related factors is more targeted than checking unrelated infrastructure or styling.

Question 22Platform operations and environment management

Which statement about environment synchronization in a multi-stage OutSystems pipeline is accurate?

  1. Environments progress through a pipeline where validated versions are promoted in sequence Correct answer.
  2. All environments always run the identical version at all times
  3. Development and Production must share the same database
  4. Each environment is fully isolated and shares nothing with others

Explanation

In a pipeline, a version is validated in earlier stages and then promoted in sequence to later stages such as Production. Environments are not required to run identical versions at all times, and they do not share databases.

Question 23Platform operations and environment management

An operator needs to verify that a hotfix reaches Production quickly while still passing through QA. What is the most appropriate approach?

  1. Tag the hotfix version and promote it through QA with expedited validation before Production Correct answer.
  2. Rebuild the entire application from scratch in Production
  3. Deploy the hotfix directly to Production, bypassing QA entirely
  4. Wait for the next scheduled major release

Explanation

An expedited but still sequential promotion lets the hotfix pass through QA validation before reaching Production, preserving quality gates. Bypassing QA or deferring to a major release defeats the purpose of a hotfix.

Question 24Platform operations and environment management

Which LifeTime feature allows an operator to compare what changed between two application versions before promoting?

  1. The database schema editor
  2. The end-user profile page
  3. Version comparison and deployment details in LifeTime Correct answer.
  4. The server's BIOS settings

Explanation

LifeTime provides version comparison and deployment details so operators can review changes before promotion. End-user pages, schema editors, and hardware settings do not offer this release-review capability.

Question 25Platform operations and environment management

An operator observes repeated failed logins to LifeTime from an unusual location. What is the most appropriate first response?

  1. Post the credentials in a shared channel for verification
  2. Investigate the account, review audit logs, and consider locking or resetting credentials Correct answer.
  3. Ignore it because LifeTime logins are not security-relevant
  4. Disable all monitoring to reduce alert noise

Explanation

Repeated unusual login attempts warrant investigation of the affected account, review of audit logs, and protective action such as locking or resetting credentials. Ignoring the signal or sharing credentials would worsen the security exposure.

Question 26Platform operations and environment management

An operator is preparing a new Production environment for its first deployment. Which LifeTime step is required before any application can be deployed to that environment?

  1. The environment must have its own separate LifeTime installation running on the same server.
  2. The environment must be registered in LifeTime and associated with the correct deployment controller and stage. Correct answer.
  3. The environment must be converted into an OutSystems personal environment before registration.
  4. The environment must be removed from the Development stage so it stops receiving automatic publishes.

Explanation

LifeTime only orchestrates environments it knows about, so a new Production stage must first be registered with its deployment controller address and stage assignment. Until that registration is complete, no application version can be tagged or deployed to it. Personal environments are for individual developers and are not the mechanism for adding a managed Production stage.

Question 27Platform operations and environment management

A platform operator needs to review which applications in Production are running versions older than the latest tagged version. Which LifeTime view is most directly suited to this check?

  1. The applications list filtered by environment, showing the deployed version per application. Correct answer.
  2. The environment health dashboard showing server CPU and memory counters.
  3. The audit log of module-level publish operations only.
  4. The user management screen showing which developers have LifeTime accounts.

Explanation

LifeTime's application list is organized per environment and shows the version currently deployed for each application, making version drift visible at a glance. Health dashboards and audit logs describe runtime state and activity history rather than deployed version identity. User management has no bearing on which application versions are running.

Question 28Platform operations and environment management

An operator wants to guarantee that only versions which passed QA can be promoted to Production. Which LifeTime mechanism most directly enforces this?

  1. Granting all developers the Deploy to Target permission across every stage.
  2. Enabling debug mode on the Production environment so developers can inspect failures.
  3. Tagging the version in QA and configuring the deployment plan so only tagged versions reach the Production stage. Correct answer.
  4. Disabling the QA environment so that all deployments bypass it.

Explanation

Tags mark a version as approved for a stage, and LifeTime deployment plans can restrict which tags are allowed to progress to Production. This creates a controlled gate between QA validation and Production promotion. Broad permissions or bypassing QA would weaken, not strengthen, that gate.

Question 29Platform operations and environment management

Which activity belongs to routine operational maintenance of a Production OutSystems environment rather than to application development?

  1. Designing new screen flows for an upcoming feature release.
  2. Reviewing platform server disk usage and log growth, then planning cleanup or archiving. Correct answer.
  3. Refactoring a module's entity model to normalize data.
  4. Writing server actions that call an external REST API.

Explanation

Operators maintain the health of the runtime environment: monitoring disk, logs, database growth, and platform services so the environment stays stable. Designing screens, writing server actions, and refactoring entities are development tasks performed in a development environment. Keeping these responsibilities separate protects Production stability.

Question 30Platform operations and environment management

An operator must add a new QA environment between Development and the existing Production stage in LifeTime. What is the most appropriate sequence?

  1. Delete the Production environment, recreate it after QA, and redeploy every application manually.
  2. Move Production into the Development stage so both share the same deployment plan.
  3. Register the new environment, assign it to a QA stage positioned before Production, then update deployment plans so promotions flow through it. Correct answer.
  4. Register the environment but leave it outside any stage so deployments skip it automatically.

Explanation

Inserting a stage requires registering the environment, placing it in the correct position in the pipeline, and adjusting deployment plans so promotions pass through the new stage. Deleting Production or merging stages would destroy the separation of concerns the pipeline provides. An unassigned environment cannot participate in the promotion flow.

Question 31Platform operations and environment management

After a deployment, an operator sees that a scheduled job that ran hourly in QA now runs every minute in Production. Which configuration area should be checked first?

  1. The environment-specific values of the timer or scheduled action in the Production environment. Correct answer.
  2. The version of the browser used by end users in Production.
  3. The number of developers with access to the Development environment.
  4. The LifeTime license count assigned to the Production stage.

Explanation

Scheduled actions and timers can carry environment-specific settings, so a schedule defined differently in Production will override the QA cadence. The operator should compare the Production timer configuration with the QA definition. License counts, developer access, and browser versions do not change how often a timer fires.

Question 32Platform operations and environment management

An operator wants to verify what changed in an application between the version running in QA and the version running in Production before approving promotion. Which LifeTime capability is most appropriate?

  1. Comparing the two application versions to review the differences in modules and dependencies. Correct answer.
  2. Reading the server's operating system event log for hardware faults.
  3. Checking the SSL certificate expiry date on the Production load balancer.
  4. Reviewing the list of end users who logged into Production that day.

Explanation

LifeTime provides a version comparison that highlights what differs between two application versions, including module changes and dependencies, so the operator can assess impact before promotion. OS event logs, user login lists, and certificate expiry describe infrastructure or access state, not application change content.

Question 33Platform operations and environment management

A Production environment is running a platform server version several releases behind the QA environment, and a new application version now fails to deploy. What is the most likely operational cause?

  1. The QA environment has too many registered users for the deployment to proceed.
  2. The application version requires platform features that the older Production server does not yet support. Correct answer.
  3. The Production database has been switched to read-only mode by the deployment plan.
  4. The application's tag was applied in QA rather than in Development.

Explanation

Applications compiled against a newer platform may depend on runtime features unavailable on an older server, causing deployment or runtime failure. Operators should align platform versions across stages before promoting such releases. Database read-only mode, user counts, and where a tag was applied do not explain a platform version mismatch.

Question 34Platform operations and environment management

An operator is asked to confirm that a hotfix reaches Production quickly while still being validated in QA. Which approach best fits the LifeTime model?

  1. Deploy directly from the developer's personal environment to Production and skip QA entirely.
  2. Copy the compiled files onto the Production server manually and restart the services.
  3. Publish the fix only to Development and declare the incident resolved.
  4. Deploy the fix to QA, validate it, tag that version for Production, and promote it through the normal plan. Correct answer.

Explanation

LifeTime's model routes changes through the pipeline: validate in QA, tag the validated version, then promote it. This keeps the hotfix fast while preserving the QA gate and traceability. Manual file copies and direct personal-environment deploys bypass the controls that make Production changes auditable.

Question 35Platform operations and environment management

An operator notices that deployments to Production frequently fail because of missing dependencies on other applications. Which operational practice most directly reduces this risk?

  1. Running the Production environment on a larger server instance.
  2. Scheduling deployments during business hours for faster feedback.
  3. Reviewing and including the full dependency set in the deployment plan before promoting. Correct answer.
  4. Increasing the number of LifeTime users who can approve deployments.

Explanation

Deployment failures from missing dependencies usually mean the plan did not include every application the release depends on. Reviewing dependencies and adding them to the plan ensures the whole set is promoted together. More approvers, larger servers, and business-hour timing do not address dependency completeness.

Question 36Platform operations and environment management

An operator needs to know which user tagged a specific application version for Production and when. Which LifeTime source provides this?

  1. The list of modules currently published in Development.
  2. The Production server's CPU utilization graph.
  3. The application's end-user login history.
  4. The audit trail of tagging and deployment operations recorded in LifeTime. Correct answer.

Explanation

LifeTime records tagging and deployment operations with the acting user and timestamp, which is exactly what an audit question requires. Login history, resource graphs, and Development module lists do not attribute tagging actions to users. This audit trail is central to change accountability.

Question 37Platform operations and environment management

An operator observes that a Production environment's database is growing much faster than expected while application usage is stable. Which investigation is most appropriate first?

  1. Reduce the number of QA environments registered in LifeTime.
  2. Disable the LifeTime audit trail to stop it from consuming storage.
  3. Check log table growth and retention settings, and review whether verbose logging was left enabled after troubleshooting. Correct answer.
  4. Immediately delete all application modules from Production to reclaim space.

Explanation

Unexpected database growth with stable usage often traces to log tables, verbose logging left on, or missing retention policies. Reviewing those settings is a safe, reversible first step. Deleting modules or disabling auditing destroys data and traceability, and QA environment counts do not affect the Production database.

Question 38Platform operations and environment management

A deployment to Production succeeded, but the application now returns errors only for users in a specific department. Which area should the operator investigate first?

  1. The browser cache size on the LifeTime server.
  2. Role and permission assignments for that department's users in the Production environment. Correct answer.
  3. The platform server's operating system patch level.
  4. The number of applications registered in the Development stage.

Explanation

When failures are scoped to a user group, the most likely cause is environment-specific authorization data such as roles and permissions that differ from QA. Checking those assignments in Production isolates the issue quickly. OS patch level, Development application counts, and LifeTime browser cache would affect all users uniformly or not at all.

Question 39Platform operations and environment management

An operator must apply a platform server upgrade to Production. Which consideration most directly protects the ability to recover if the upgrade fails?

  1. Removing the QA environment so only one environment needs attention.
  2. Choosing a weekday morning so more staff are online to observe the change.
  3. Increasing the number of LifeTime administrators just before the upgrade.
  4. Verifying a tested, recent backup of the environment's database and configuration exists before starting. Correct answer.

Explanation

A platform upgrade can alter schema and configuration, so a verified recent backup is the primary recovery control if the change fails. Staffing and administrator counts help response but do not restore a broken environment. Removing QA reduces validation capability and does not improve recoverability.

Question 40Platform operations and environment management

An operator is asked to reduce the blast radius of a release that touches several applications sharing common dependencies. Which approach best fits LifeTime operations?

  1. Deploy only the application with the most visible changes and leave dependencies behind.
  2. Disable the deployment plan so LifeTime deploys applications in arbitrary order.
  3. Split the release into staged promotions, validating shared dependencies in QA before promoting the full set together. Correct answer.
  4. Promote every application simultaneously to Production without intermediate validation.

Explanation

Staged promotion lets the operator confirm shared dependencies behave correctly before the full set moves to Production, limiting the impact of any single failure. Promoting everything at once maximizes exposure, while deploying only part of the set risks inconsistent dependencies. Disabling the plan removes ordering control entirely.

Question 41Deployment and lifecycle management

In OutSystems lifecycle management, which environment is the one where end users actually consume the application and where published versions must be treated as production code?

  1. Development environment
  2. Production environment Correct answer.
  3. Quality environment
  4. Personal sandbox environment

Explanation

The Production environment is the runtime stage where real end users access the application, so every deployment there must follow change control and rollback planning. Development and Quality exist to build and validate before reaching that point.

Question 42Deployment and lifecycle management

A team wants to move a validated application version from Quality to Production. Which OutSystems capability is designed to perform that cross-environment promotion?

  1. Service Studio's 1-Click Publish button
  2. The Module's public elements list
  3. LifeTime deployment plans Correct answer.
  4. The application's screen flow editor

Explanation

LifeTime is the console that manages environments and orchestrates deployments between them through deployment plans. 1-Click Publish only pushes code from Service Studio to the environment the developer is connected to.

Question 43Deployment and lifecycle management

What is the primary purpose of tagging an application version in LifeTime before promoting it?

  1. It grants end users permission to access the application
  2. It automatically fixes compilation errors found during validation
  3. It creates a named, immutable reference to that version for traceability and rollback Correct answer.
  4. It compiles the application faster in the target environment

Explanation

A tag records a specific application version under a meaningful name so you can identify what was released and redeploy that same version if a rollback is needed. Tags do not change compilation behavior or user permissions.

Question 44Deployment and lifecycle management

Which statement best describes a deployment plan in OutSystems LifeTime?

  1. A report of end-user sessions active during a release
  2. A schedule of database backups taken by the platform
  3. A record of the modules and versions to be deployed from a source environment to a target environment Correct answer.
  4. A list of modules selected for validation before publishing to the same environment

Explanation

A deployment plan captures which applications and module versions will move from the source environment to the target, and tracks the progress of that promotion. It is the unit of cross-environment release work in LifeTime.

Question 45Deployment and lifecycle management

A developer needs to publish a fix directly to the Development environment after editing a module. Which action accomplishes this?

  1. Tag the application in LifeTime
  2. Run the module's impact analysis report
  3. Use 1-Click Publish in Service Studio Correct answer.
  4. Create a deployment plan in LifeTime

Explanation

1-Click Publish compiles and deploys the current module to the environment the developer is connected to, which is typically Development. LifeTime deployment plans are for moving between environments.

Question 46Deployment and lifecycle management

What does the OutSystems platform do when a module's dependencies are not satisfied during a deployment?

  1. It silently skips the missing dependency and publishes anyway
  2. It converts the module to a reactive web app
  3. It blocks the deployment and reports the unresolved dependency Correct answer.
  4. It automatically downgrades the target environment

Explanation

Deployments require all referenced dependencies to be present and compatible in the target environment. When one is missing or mismatched, the platform halts the deployment and surfaces the dependency problem for resolution.

Question 47Deployment and lifecycle management

Which artifact should be reviewed to understand which other modules will be affected before changing a shared module used across applications?

  1. The dependency and impact analysis information for that module Correct answer.
  2. The module's TrueChange tab only
  3. The environment's server log files
  4. The application's user story backlog

Explanation

Impact analysis shows which modules and applications reference the module being changed, so the team can plan regression testing and coordinated deployments. TrueChange reports validation issues in the module itself, not downstream consumers.

Question 48Deployment and lifecycle management

What is the role of the Quality environment in a standard OutSystems three-stage pipeline?

  1. It is where developers first create modules
  2. It is where end users consume the final release
  3. It is where the platform stores source code backups
  4. It is where validated builds are tested before promotion to Production Correct answer.

Explanation

Quality sits between Development and Production and is used to test a build that already passed development validation before it reaches end users. This separation reduces the risk of releasing untested changes to Production.

Question 49Deployment and lifecycle management

A deployment to Production fails during the compile stage. What is the most appropriate first step for the operations engineer?

  1. Delete the Production environment and recreate it
  2. Retry the deployment repeatedly until it succeeds
  3. Manually copy files from Quality to the Production server
  4. Inspect the deployment log to identify the compilation error and fix the source module Correct answer.

Explanation

Deployment logs identify the module and the specific compilation failure, which points to the fix needed in the source environment. Blind retries or manual file copies do not resolve a genuine compile error and can leave the environment inconsistent.

Question 50Deployment and lifecycle management

An application in Production must be reverted to the version released last week. Which LifeTime action supports this?

  1. Redeploy the previously tagged version to Production Correct answer.
  2. Edit the Production module directly in Service Studio
  3. Restore the Development environment from a snapshot
  4. Delete the deployment plan history

Explanation

Because tags preserve references to earlier versions, redeploying the tagged version restores the known-good release. Editing Production directly bypasses the pipeline and creates drift from source control.